Please refer to question: DNS Zone Corrupt - AD corrupt
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_21372735.htmlThe solution is not complete. If AD DNS is corrupt and not working then how does the newly built DC see the domain and tranfer FSMO roles.
I have the same exact problem now and am fumbling through a fix. I came up with a partial solution similiar to the one provided before paying to see it on
Experts-Exchange. So if I put a new DC online it can not see the domain just like any other ad system. How would you recover from this? I am wondering if there is a way
to delete the corrupt zone, re-create it and then import the .dns file back to get it working, although when you try to delete it it errors with "the zone cannot be deleted.
the active directory service is not available." I have tried a seperate DNS server but it is still not seeing the domain for some reason. I may not be configuring the dns
right though. I made a domain.local zone and a host record for the dc server name however I do see another on the dc _msdcs.domain.local that I do not have on the new
dns server. I am not sure what entries are made with initial DC set up that I may be missing. I can ping the system but I can not do a nslookup??
I ran a dcdiag and everything appears to show "passed" and with a netdiag the only thing that fails is the dns test.
So to summarize, I have an error " Zone not loaded by DNS server" on the DC that is the dns server as well. (only server that is serving all roles for small office) that
started this whole issue. Obviously nothing can see the domain now so I am trying to set up/fix dns to see the AD domain again. Once the domain can be seen I can
hopefully get a new dc up and take over DNS and FSMO roles.
Any experts out there that could give insight would be greatly appreciated.
THX..
