[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1133
  • Last Modified:

Rename Standard Primary DNS Server

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
pleyden1974
Asked:
pleyden1974
  • 6
  • 4
1 Solution
 
Chris DentPowerShell DeveloperCommented:

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
 
pleyden1974Author Commented:
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
 
Chris DentPowerShell DeveloperCommented:

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
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
pleyden1974Author Commented:
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
 
Chris DentPowerShell DeveloperCommented:

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
 
pleyden1974Author Commented:
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
 
Chris DentPowerShell DeveloperCommented:

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
 
chicagoanCommented:
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
 
Chris DentPowerShell DeveloperCommented:

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
 
pleyden1974Author Commented:
Thanks Chris, upgrade happened and went perfectly.
0
 
Chris DentPowerShell DeveloperCommented:

Brilliant :)

Chris
0

Featured Post

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

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