error 5774

  • Thread starter Thread starter Bedz1
  • Start date Start date
B

Bedz1

Anyone know why I am getting error 5774 in system log
saying DNS does not exist. I checked eventid.net but does
not have exact error DNS does not exist?? Any help would
be appreciated-thx
 
What is the exact verbatim of the description of the event you're receiving?
The main article for troubleshooting these errors is this one:

259277 - Troubleshooting Netlogon Event 5774, 5775, and 5781
(http://support.microsoft.com/?id=259277).

--
J.C. Hornbeck, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
 
In
Bedz1 said:
Anyone know why I am getting error 5774 in system log
saying DNS does not exist. I checked eventid.net but does
not have exact error DNS does not exist?? Any help would
be appreciated-thx
Click to expand...


Normally )99.9% of the time) it's caused by your machines NOT using the
internal DNS server in their IP properties, and *possibly* listing your
ISP's. AD *requires* DNS, since it stores all it'd data in there. AD always
'asks" DNS, where is this or where is that in my domain. If the ISP is
listed, then all sorts of problems *will* occur. Guaranteed to occur.

Recommendations:
1. Use only your internal DNS. This applies to all machines, DCs and
clients.

2. Set updates on the zone properties to at least "Yes".

3. Insure that your AD domain name is NOT a single label name ("domain.com"
instead of just "domain") or numerous other problems will arise due to this.

4. Then at a cmd prompt on the DC:
ipconfig /registerdns
net stop netlogon
net start netlogon

5. To achieve efficient internet name resolution, configure a forwarder on
your DNS. If the option is grayed out, delete the Root zone. This articl
shows how to configure a forwarder and delete the root zone:
http://support.microsoft.com/?id=300202


If the above steps are true or you've followed them, and you're still having
problems, then we'll need to see an ipconfig /all from your DC. Also if you
can also please tell us what your AD DNS Domain name should be (exact
spelling). This will help in diagnosis. It may come down to other issues.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top