Hi,
Try using the options below
1. From a newsgroup post:
"If you have 2 DC/DNS servers, to avoid this error, make sure you have the following under IP properties:
DC1:
First DNS address points to DC2.
Second DNS address points to itself.
DC2:
First DNS address points to DC1.
Second DNS address points to itself".
2. From a newsgroup post:
"This can be caused if you have a single DC or two DCs and they point to themselves as the first entry in the DNS list in IP properties and the zone is AD Integrated. Reason could be that the DC has many services running on it (SQL, Exchange, etc.) or is a slower machine, and when the Netlogon service tries to register into the zone at boot time, AD is not quite initialized yet and so you get the error. You can either ignore it or change the zone to a Primary, or if you have multiple DCs, change the first entry to the partner and the second to itself".
3. The error may occure if the "RootDNSServers"-entry was deleted and the DNS-job not restarted.
Main Topics
Browse All Topics





by: Pentrix2Posted on 2004-06-04 at 04:59:10ID: 11231626
Oh, forgot.
Source: DNS
Event ID: 4004