Several months back the building that housed two of my remote domain controllers was destroyed. Since bringing the servers back up was physically impossible, I went through Microsoft's procedure for removing them with ntdsutil. At the same time, I looked at both my dns servers and found numerous references to the "dead" controllers and removed them by hand as well.
Yesterday, I found out my remaining dc's are no longer replicating the scripts folder and have been trying to repair. Today I installed a test domain and after it came up and I verified replication, starting looking at the different zones. The zones on my test domain look different than my production dns server zones. Their is still a left over reference to one of the domain controllers that was destroyedin gc\_tcp area of the dns server .
At this point in time, I believe the AD dns zone is corrupt, but I have no idea how to rebuild?
Any suggestions would be greatly appreciated.
David Harris
Addendum... I noticed today my second dc never receives the message saying
"The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed. "