In
MIcrosoft said:
Hi, recentley had to reinstall Win2kAS on a new hard drive, and I am
getting event id 5782 every 2 hours, and nothing I have tried seems
to solve the issue. Here is how things are setup:
1 Win2kAS as PDC, with Exchange 2000, SQL 2000. DNS Service is not
installed. I have followed all knowledge base articles about
disabling Dynamic DNS registrations. I am using an IP adress given
by ISP and am using my domain name registrars DNS servers. I have one
of those DNS servers listed in the DNS tab of TCP/IP and the other
two DNS servers are my ISP's. None of these DNS servers support
Dynamic registration, so I have disabled this. But if it is supposed
to be disabled why am I still getting this message, and why does the
error say there are no local DNS servers? I never had this problem
with my first installation.
Any thoughts of how I can fix this?
Thank You
Paul
Not sure how you got the first one running properly, since you used your
ISP's and registrar's DNS servers for this installation. Basically you
CANNOT use a foreign DNS server with an AD installation. AD requires it;s
own internal private DNS so the Netlogon service can register it's SRV
records that are required for domain communication. Without these records,
all sorts of problems are guaranteed to occur. This article is a good start
to understand AD's fundamental requirements:
http://support.microsoft.com/?id=291382
Also, read this post from a couple of weeks ago that I posted for someone
with similar errors that are due to the same reason:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---- Original Message -----
From: Ace Fekay [MVP]
Newsgroups: microsoft.public.win2000.dns
Sent: Friday, April 02, 2004 5:33 PM
Subject: Re: error 5774
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
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