DNS Problems After Domain Controller Reformat
Posted on 2004-09-06
I have 2 domain controllers. The one that I had initially set up the domain on I had to format. I transfered all of the FSMO roles over to the other DC, ran dcpromo, and then joined a workgroup to completely disassociate the server from the domain before the reformat. Everything with the reformat went beautifully, and there are absolutely no problems. I transfered all of the FSMO roles back and everything. The DNS is acting a little strange though. It appears like when I set up DNS on the server after the reformat it set up a completely new database (or whatever you call it) rather than using what was already existing on the other server.
I would like to completely erase the DNS info on both servers and from the active directory so that I can start fresh. I think there might even be more than one dns file in the active directory (one for each domain controller for some reason perhaps?). I would just like to wipe out all of that info so I can set up the DNS from scratch. My first question is how to do this. Do I just delete the zones one by one from the DNS servers? I tried that once, but when I went to add them again it seemed to be the exact same as before. My second question is after I delete all the DNS information, what would be the best way to set it all back up again? I want both servers to be able to function without the other, but I want the server that I formated to be the main DNS server and to send dynamic updates to the other. Would I set up a primary zone on that server, and then a secondary zone on the other? Or would they both be primaries? When I set these kinds of things up from scratch I always know what I'm doing, but since I had to reformat this server and rejoin it to the domain, I'm a little thrown off. Thanks for your help.