Solved

Rename Standard Primary DNS Server

Posted on 2007-03-20
11
1,116 Views
Last Modified: 2013-12-28
Hi Team,
I currently have a standalone NT4 Primary DNS server. I want to upgrade it to a Windows 2003 DNS Server and keep it standard primary and not have it AD integrated (We do have a 2003 Native Domain). Along with this I want to keep the new server name and IP the same as the old NT4 DNS server. Doing zone transfers and making the new zones on the new server primary ones is ok, but is it straightforward enough to simply decomission the nt4 server and rename the new dns server?
Thanks in advance everyone
0
Comment
Question by:pleyden1974
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 4
11 Comments
 
LVL 71

Expert Comment

by:Chris Dent
ID: 18756124

Sure, I don't see why not. Just check on your zones after you've renamed it - depending on exactly what it's doing you may have to update NS and SOA records.

Chris
0
 

Author Comment

by:pleyden1974
ID: 18756179
Thanks Chris,
OK, so would these steps make sense:
1. NT4DNS1 Server has primary standard zones and W2K3DNS1 Server is a standard secondary zone
2. Add new zones on W2K3DNS1 and transfer from Master (NT4DNS1)
3. Once all zones transfered, shut down NT4DNS1
4. Quickly change all secondary zones to primary zones on W2K3DNS1
5. Simply rename W2K3DNS1 to old name NT4DNS1 and change IP to old one.??
6. What tests should I run to ensure all is well?
Thanks
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 18756227

There's not much I'd change. I'd just switch around a couple so you have your new Primary Zones up before shutting down the current Primary.

1. Is fine
2. Is fine
3. Reset all Secondary Zones to Primary on the 2003 Server
4. Shut Down NT Server
5. Rename 2003 Server
6. Reset IP

Afterwards you're pretty likely to have to fix the NS and SOA records at the very least.

You could always copy across the zone files (%SystemRoot%\System32\DNS) and put those in place following the 2003 server rename - that way the NS and SOA records would match the name and IP of the NT Server.

You have all the zones configured as Primary now, so restarting the DNS service should force a reload from those zone files (as long as the names match up).

However, you would still have to clean up the NS records to remove the secondary from the list (as it will presumably now be hopelessly inaccurate).

Chris
0
Are You Headed to Black Hat USA 2017?

Getting ready for Black Hat next week? Kick things off with the WatchGuard Badge Challenge and test your puzzle and cipher skills. Do you have what it takes to earn our limited edition Firebox Badge? Get started today - https://crimsonthorn.net

 

Author Comment

by:pleyden1974
ID: 18756423
Thanks Chris,
1. so when I do the transfer from master and change the stnd sec to primary stnd on the new server will the NS and SOA values change automatically for each zone to reflect the new Primary Standard server? - hence once I do I server/IP rename (after shutting down old NT DNS) the NS/SOA records will need to be manually changed back?

2. Copying sounds interesting. what steps would you recommend there Chris?
Thanks alot
0
 
LVL 71

Accepted Solution

by:
Chris Dent earned 250 total points
ID: 18756490

1. I believe it will update the NS and SOA records at that point, yes.

2. They're just files, with a .dns extension. The format should be compatible between versions of the DNS Servers. The steps are quite short:

 - Find the .dns files in %systemroot%\system32\dns\ on the NT Server.
 - Copy these to temporary location on 2003 server
 - Run through the steps above to Decomission the NT server
 - Check the file names against those in %systemroot%\system32\dns\ on the 2003 Server.
 - Stop the DNS Service
 - Copy of the old .dns files over the versions on the 2003 Server
 - Start the DNS Service and check all zones

You may also want to take a backup of the 2003 versions of the files, that way if it doesn't work you can simply stop the DNS service, restore the 2003 versions and start it up again.

Quite a few steps, but really not much involved in any of them and it may save you a while updating NS / SOA records.

Chris
0
 

Author Comment

by:pleyden1974
ID: 18757097
Thanks again chris,
based on moving dns records to get around updating the NS and SOA records on the 2 dozen zones we have, would this article apply for NT4 to Win2003? http://support.microsoft.com/kb/280061/
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 18757316

It's not so much the initial copy so much as renaming the server and giving it a new IP afterwards. The article doesn't really apply in that context as you already have the zones configured.

However, if you were to moving it to a new server which didn't have any zones configured the article is much more useful.

Chris
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 18757837
If it is not part of a domain, and you're using it strictly for DNS I don't see a problem with slipping it in at the same name/ip.
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 18757854

Indeed.. it will acheive the same as copying the original zone files across was intended to (leaves the old NS and SOA records intact saving the need to update).

Chris
0
 

Author Comment

by:pleyden1974
ID: 18822769
Thanks Chris, upgrade happened and went perfectly.
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 18823767

Brilliant :)

Chris
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article summaries thoughts and ideas from two years of sustained use. It provides good reasoning to make the jump to Windows 10.
This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question