Computing.Net > Forums > Windows Server 2003 > DNS errors after changeover

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

DNS errors after changeover

Reply to Message Icon

Name: rayhorn13
Date: January 15, 2006 at 18:49:37 Pacific
OS: MS Server 2003
CPU/Ram: 2 x 2.8 GHz w/ 1 GB RAM
Comment:

I am fairly green when it comes to DNS issues. We have a single Server 2003 as our DC.
We just changed internet providers, email & web hosting all at once. That went smooth enough after I found that I needed to change the Host (A) records to point to the new IPs. Now everything seems to be running fine, but I rebooted (after a recent MS security update) for the first time since the changeover & in the logs I found a large number of
--------------------
DNS errors:
6 for event ID 4004 (DNS server unable to complete directory service enumeration of zone ..)
2 for event ID 4015 (DNS server has encountered a critical error from the Active Directory)
1 for event ID 6702 (DNS server has updated its own Host (A) records. An attempt made through dynamic update... An error occured during this update)
System (NETLOGON) errors:
20 for event ID 5774 (The dynamic registration of the DNS record (20 different messages follow - examples shown below) failed on the following DNS server...
--------------------
Examples of the "20 varying responses" are:
'_kerberos._tcp.mydomain.com. 600 IN SRV 0 100 88 MYSERVER.mydomain.com.'
'_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com. 600 IN SRV 0 100 389 MYSERVER.mydomain.com.'
'_ldap._tcp.DomainDnsZones.mydomain.com. 600 IN SRV 0 100 389 MYSERVER.mydomain.com.'
'<<many numbers>>._msdcs.mydomain.com. 600 IN CNAME MYSERVER.mydomain.com.'
and 16 more DNS records that failed!
--------------------

Obviously, there is much more information to be gained from the logs that I have left out but can supply.

--------------------

Even with all of these error messages, everything seems to be running fine for now. The emphasis is on "seems to be" and "for now."

Can anyone tell me how serious this is? What can I do to fix it? Is it a simple or complex problem & fix?

MANY THANKS IN ADVANCE!!



Sponsored Link
Ads by Google

Response Number 1
Name: wanderer
Date: January 17, 2006 at 08:15:37 Pacific
Reply:

"That went smooth enough after I found that I needed to change the Host (A) records to point to the new IPs."

That was incorrect. You put the isps entries in the FORWARDERS tab not at host/ptr records.

MS works by wksts point to the ms dns server and the ms dns server forwards unresolved requests to the isps dns servers.

Golly gee wilerkers everyone. Learn to Internet Search


0
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: DNS errors after changeover

DNS Fails to resolve www.computing.net/answers/windows-2003/dns-fails-to-resolve-/3534.html

DNS Errors Irritating www.computing.net/answers/windows-2003/dns-errors-irritating/7059.html

Slow loging and dns errors www.computing.net/answers/windows-2003/slow-loging-and-dns-errors/5134.html