[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 422
  • Last Modified:

DNS on a member server

Dear Experts,
I upgrade AD from 2003 to 2008 R2. Everything went OK but since lots devices and servers are still pointing to 2003 server as DNS server, can I install DNS on 2003 server back? because when I demote windows 2003 server, it removed DNS, too with AD. I would like to put DNS back so meantime there is no downtime untill they change DNS server on the devices and servers.
Thanks in advance
5 Solutions
Yes , you can install secondary DNS server on Windows 2003 server back. Afrter all devices are pointed to 2008 R2 you can remove it.
Adam BrownSr Solutions ArchitectCommented:
You *can* add DNS back to the 2003 server, but it won't contain all of the information from your AD zone by default. There are some configuration settings you need to set in order for the DNS zone to be replicated to a DNS Server that isn't a Domain Controller. You have to set up the DNS server on the 2008 server to accept zone transfer requests from the 2003 server and a couple other things.
I usually either make the IP address of the old server the IP address of the new server, or I add the old IP address to the new server so that the new server can answer all DNS queries sent to the original server. It eliminates the need to change the DNS settings on clients.
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Install DNS service on member server & configure zone transfer on new dc to windows 2003 server, but on member server the zones will not be AD-Integrated zone.

Hi there,
to change the DNS settings on the other servers (and computers with static IPs), you could use netsh scripts like this:

netsh interface ip set dns name="Local Area Connection 2" source=static addr=
netsh interface ip set dns "Local Area Connection 2" static primary
netsh interface ip add dns "Local Area Connection 2" addr= index=2
netsh interface ip add dns "Local Area Connection 2" addr= index=3

This sets primary DNS on NIC 2, "Local Area Connection 2" to, second to and 3rd to
You could ajust it to your needs and i. e. run it as logonscript on the servers, by computer policy (loopback switched on). The other PCs should have DHCP settings and get the new DNS that way.
This works of course only if you have very similar servers (let's say all use mainly the first NIC and the name of this NIC is default ""Local Area Connection").
Yes you can by Adding DNS to you pr old server, then creating the secondary dns zone pointing to the new server.

But before all that you must change the dns zone properties on the new server. And go to 'zone transfer' tab and change the option to allow zone transfer to specific server and put the ip address of your old dns server to allow replication.

Suggestion: the better is to change back you old server as Domain Controller and Add DNS to be done automatically and also have a redundant server to serve the network incase of new server failure

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now