Unable to register DNS records correctly in 2003 AD domain
Posted on 2007-11-20
I know this has been asked many times before, but the recommendations/solutions I've read so far have not helped.
Quick network rundown: Windows 2003 domain. Single domain controller hosting DNS, WINS, RRAS and DHCP. DHCP has the clients using the domain controller as the only DNS and WINS servers.
Problem: I am currently unable to ping our domain by its DNS name (domain.local). When the domain was first setup, I was able to from all workstations. At this point, even pinging the DNS name from the domain controller fails. Using a HOSTS file entry has been about the only way I can get around the problem.
Things I have tried:
Usual "ipconfig /flushdns" "/registerdns" has no effect on any systems.
Server is using itself as the only DNS server. Restarting netlogon service has no effect.
Only issues NetDiag.exe show relate to not having an interface with the Workstation Service and Messenger Service defined in WINS (which shouldn't affect DNS)
DCDiag.exe comes back clean, everything passes.
If I look in the DNS zone for my internal domain, I see the SRV records like I normally should. I've compared these records to domain DNS zones that do work properly and cannot find any real differences.
Under the advice of some post on here, I removed my domain.local DNS zone, uninstalled DNS, reinstalled DNS and then restarted the NetLogon service. After doing this, I had to manually recreate the domain.local DNS zone before it would auto-populate the SRV records and the sub-folder structure you normally see for an AD DNS zone. Such as the _msdcs, _sites, etc folders. Before I manually re-created the DNS zone, I saw a NETLOGON warning Event ID 5781 in my System log. This event ID lists some recommendations, but most pertain to "make sure your DNS server is turned on" or "you're using the wrong IP address for your DNS server", all of which do not help me.
Only major change that I can remember since it was working has been moving our email server. Our email server used to be hosted on this same physical box but was moved in the last few weeks. This problem however started happening months before I moved the email system to a dedicated machine.