The Windows Server group is your premier resource for objective technical discussion and peer-to-peer support on the Microsoft Windows Server family of products including Windows Server 2003, IIS Server, ISA Server, and SMS Server.

Reinstall DNS on DC

This is one thing I haven't done before. I have a domain environment (Windows Server 2003) with only one DC that also serves as the DNS and DHCP Server. I would like to reinstall the DNS Service on the server. Kindly help with the steps and precautions to take.

Funny, I found a resolution already. The thing is, we had been having
niggling issues with our network recently and it seems to be building to a
head. I decided to re-install DNS when I had a Win8Pro laptop having
problems joining the domain (and after joining logging on to the
domain) all error quotes suggested a communication issue with the DNS
server. Also the folders beneath my domain in DNSMGR like _tcp, _msdcs
etc... have all disappeared. I had run dcdiag and some other tools to no
avail.

However, while googling, I came across a fix that asked me to install the
WinServ2003 support tool kit, after which I run dcdiag /fix, then netdiag
/fix, flush and register dns, and then restart netlogon (all in that
particular order) after which everything was fine again.

Glad to hear you got it resolved, but for the sake of future visitors to this thread, let me try to answer your original question.

First, the easiest way to rebuild any DNS server is to turn on DNS on another server and let them replicate. After that, remove, reboot, then re-add the DNS server role and let them replicate again.

There is one gotcha in your original question, and that is that your server was also a DC. I have never tried, but I do know that the DNS role is automatically added when you perform a dcpromo. That would make me suspect that you might not be able to remove the DNS role unless you demote the server back to a member first.

If you are having problems with DNS resolution issues though, it might be worth it to just document your static entries and then start from scratch, rebuilding the zones, reading the static entries, and letting the dynamic entries add themselves.

Thanks for sharing your fix though, the worst thing in the world are guys who ask the question, participate in the thread for a month and then just come back to say "I fixed it" and don't tell anyone else what worked. :D

Let's start off with your need to set up a second DC. You are playing Russian Roulette to have a single DC. What are you going to do when (not if) your DC crashes? You will lose your entire domain and face a huge task rebuilding it.

OK, having said that, why do you need to re-install DNS? Depending on the reason, you may not resolve your problem. Kind of like replacing a fuse (remember them?) when you blow one without figuring out why the fuse blew.

I have resolved the issue already. Kindly read through the thread. Reasons
and resolution are up above. Thanks
About the single DC.....well, i see your point. How do I go about doing
this? Can i use already set up servers and add a role on them or is it
better to have another server set up for this?

It's actually pretty easy. You set up the server and make it a DC in the domain. Assuming it has integrated DNS, that is created automatically. It's recommended that you add DHCP and split the scopes.

There's a lot of documentation on the web, including Microsoft Knowledge Base. The exact procedure will depend on the server OS version you are running on your current DC and what OS you want on the new DC.

Thanks Andrew! I don't believe I have ever tried to remove DNS from a DC, and as I said, the role gets automatically added during dcpromo, so I wasn't really sure if it would allow you to or not.

As for a redundant DC, I second that motion. If you have more than one server, you should have more than one DC. As for what server to promote, I usually target file/print servers first. I would recommend that you avoid it on SQL, Exchange, and Terminal servers unless you have no other choice. Yes, ideally you would have a dedicated DC, but in the real world a lot of businesses can't afford to spend a few thousand dollars just to have redundancy for their DC.