replacing DNS server

I have a Server 2003 Domain Controller which is also our DNS server.

This server has been giving us problems for a couple months now. We are planning on retiring the server.

We have created a Virtual server that is going to replace this domain controller/dns server.

I am not too familiar with configuring a DNS server.

What are the main things I have to do to configure the new dns server ?

The new server will have a new IP address and Name
We have another DNS server in our disaster recovery site.

A point in the right direction and a couple words of wisdom would be a great help

Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

Darius GhassemConnect With a Mentor Commented:
If your DNS Zones are AD integrated then you won't have to do much. When you dcpromo the new server to join it to your current domain as a DC then you select the DNS to be integrated with AD which will make DNS replicate all settings over to the new server. In AD integrated zones you don't have to worry about the primary and secondary zones and zone transfers.
ComputerTechieConnect With a Mentor Commented:
Here a great how to if you are going to use windows 2003 dns server
mrmarkfuryConnect With a Mentor Commented:
I'll just provide some general concepts so you have an idea of what you will do. It's nice that your old server is still up, that will make things easier.

First, you will want to add the new server to your current DNS infrastructure, the link CT posted is very good. Basically, you will be:

Installing DNS on the new server
Configuring your forward and reverse lookup zones, downloading the current info from your existing server
Allow zone transfers from your old server to your new one

After the new server has been successfully added, remember before removing the old one, your clients must have the ip address of your new DNS server! If the clients are configured statically, you will need to change their DNS entries to point to the new server, if you use DHCP, you will need to update the DNS's that are handed out by DHCP.

Also, make sure your new server has allowed and is allowed to transfer to all your other DNS servers.

Good luck, if you need some specific advice or clarification, we're here to help.
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

EkuskowskiAuthor Commented:
Looks like DNS is working on the new server. I changed my IP address and DNS server to point to the new DNS server and I am able to get to the internet, ping other servers and printers. What tests should i run to verify DNS is configured correctly? I did not configure anything on the new server, seems to have pulled all the info through AD, just as dariusq had mentioned.

but when I go to DNS management and select the new DNS server, the right side pane gives me a screen that says Configure a DNS Server. I have attached a screenshot called DC1.bmp that shows what I am talking about.

I then selected Action configure a DNS server and I got the next screen, which I'm not sure of how to answer the question so I just cancelled. That screen shot is called DC1-Configure-DNS-Wizard.bmp

When I select our primary DNS server called file05 the screen right side pane has information including Root hints and forwarders. I have attached a screen shout of this as well. called File05.bmp

So I think I have three questions.
1. Is my DNS working properly now, and if I switch all my clients to point to the new DNS will I have a problem ?
2. If it is configured correctly , how do I get dns managment screen to not display "configure DNS Server" in the right hand pane ?
3. If I have to run the configuration wizard how do i answer the first question ?
4. How do I verify DNS is properly configured ?

Thank you for all your help
Darius GhassemCommented:
You need to create a Forward Lookup zone. Walk through the steps make sure you select AD integrated which will place the current zone in AD into the DNS console.

Look at Step three.

After you have the DNS zone setup you can run "dcdiag /test:dns" to confirm all settings are correct.
EkuskowskiAuthor Commented:
Will I need to do a reverse lookup as well?
Darius GhassemCommented:
Yes, but Forward lookup is more important then reverse right now.
EkuskowskiAuthor Commented:
OK, looks like DNS is working, we are going to manually switch a couple of people to point to the new DNS server and see if they have problems.

Is there anything else I should test to make sure DNS is working before closing out this Question ?
Darius GhassemCommented:
Run a dcdiag /test:dns
Also, when you switch the client, do a couple nslookups to verify it's working for them.

First, go to nslookup(Open command prompt, and type "nslookup")
Enter their local computer name, hit enter. Should resolve to IP

Then try to resolve a server (file server or whatever), and a website (

If you have more than one domain in your AD forest, enter a machine name on another domain, including the FQDN (ie COMP1.DOMAIN.COM)
EkuskowskiAuthor Commented:
Everything looks to be working, I thank all of you for your help. still haven't made the switch in production but our tests all seem to be working properly
EkuskowskiAuthor Commented:
We still haven't made the switch in production but in our tests all seem to be working properly. We will probably make the official switch after a couple weeks with a test group
All Courses

From novice to tech pro — start learning today.