I’ll show you the quickest way to move an existing public advertising DNS deployment on Windows Server 2012R2, generation 1 virtual machines (1 primary DNS server and 1 or more secondary DNS Servers) to Windows 2016 RTM generation 2 VMs. On top of this we will preserve the sever names and the IP addresses. This makes the migration easier and it doesn’t burden anyone with updating IP addresses or FQDN of services pointing to the existing public advertising DNS service. Basically the result is the best possible for everyone involved.
Step by Step
We start by preparing a sysprepped VHDX of Windows 2016 with all the updates installed and any tools that are sysprep compatible and that you want or need on your VMs. This will allow us to make the move fast. As we want our new DNS VMs to be generation 2 VMS, make sure you use a generation 2 VM to create the syprepped OS VHDX.
The process we describe below is the same for each of the involved DNS servers. You start with the secondary VMs and end with the primary VM. This is just a form risk reduction, it’s smart to start with the secondary as it’s less critical than the primary where you make the changes.
Log on to the old, source VM and do the following
- Create a Folder to store the migration data and Info, i.e. C:\DNSMigrateServer01
- Open an elevated command prompt
- Run Ipconfig /all > C:\DNSMigrateServer01\Server01TCPIPinfo.txt this gives you the IP info you need for future reference.
- Run reg export HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DNS\Parameters C:\DNSMigrateServer01\Dns-Service.REG
- Run reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server” C:\DNSMigrateServer01\Dns-Software.REG
- In some cases, rarely for most deployments, you’ll need to also copy all files under each custom database directory on the old DNS server by manually reading from the registry at the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters\DatabaseDirectory If you have these also copy the directory to C:\DNSMigrateServer01. Normally when you have custom DNS database locations this is not by accident and should be well documented.
- Run xcopy %windir%\system32\dns C:\DNSMigrateServer01 /s This copies the content of your DNS folder (normally C:\Windows\System32\dns) to your migration folder. Note that you don’t need to copy the samples sub folder. Even the backup folder is not really needed. Just create a new backup when needed on the news DNS servers.
- Copy the C:\DNSMigrateServer01 from your old DNS Server to your desktop or some file share for safe keeping. You’ll need to copy this into the new DNS Server later. Note it contains your IP information, your registry exports and your DNS files.
You now have everything you need form the old DNS Server. So now we’ll decommission it, but before we do so we’ll make sure we have the options to recover it if needed.
- Make sure you have a backup or have made on recently (you do trust your ability to restore, right?)
- Shut down the VM and for good measure and fast recovery you might want to export the VM for quick import.
- Remove the VM from Failover Clustering if it’s clustered.
- Now remove the VM from Hyper-V Manager. Note this doesn’t delete the virtual disk files.
- Remove the old VHDX (you have an export and a backup) and replace it with your sysprepped W2K16RTM VHDX that has all the updates already. Rename that VHDX to something sensible like server01disk01.vhdx.
- Create a new generation 2 VM with the same name as the old one, select the required memory settings, choose to use an existing VHDX and point it to your sysprepped VHDX.
- Start the VM
- Go through the mini wizard and log in to it.
- Configure the NIC with the same setting as your old DNS Server
- Rename the VM to the old DNS VM name and join the domain.
- Restart the VM
- Login to the new DNS VM
- Install DNS
- Copy the C:\DNSMigrateServer01 you saved from your old DNS Server into the new one
- Open an elevated command prompt and run
- Stop the DNS Server service by running net stop “DNS Server”
- Double click the Dns-Service.REG and merge them into the registry
- Double click the Dns-Software.REG files and merge them into the registry.
- Copy all the files under C:\DNSMigrateServer01 to %windir%\System32\DNS
- Start the DNS Server service by running net start “DNS Server”
Congratulations, you now have a new generation 2 VM running DNS on Windows Server 2016 with the same name and IP configuration as the old one. You now want to validate it’s working. To do so on the primary DNS server update the serial number in the start of authority (SOA) tab of the zone properties. I normally use YearMonthDayXX.
This will allow you to check whether the zone transfers to your migrated DNS server work. Normally all is just fine. In case things went horribly wrong you can import the VMs you exported or restore the backups. If your VMs are domain members and as you have reused the VM name, you’ll need to reestablish its domain member ship but that’s easily done.
Now repeat the above process for all the reaming secondary DNS Server and finally for the primary DNS server. Until you’ve done them all.
You do this process for every DNS Server and finally for your primary DNS server. That’s it. You’re in business and you have achieved 2 goals. You’re DNS VMs have been move to generation 2 and are running on a clean install of Windows Server 2016. All this without having to reconfigure DNS zone and transfers and while maintaining your DNS server names and IP addresses. Life is good.
Thank you for this Article. Is there a easy way to change the IP Address of the DNS Server also? In the Reg File it is REG_MULT_SZ and not so easy to change
If I understand you correctly, I’d say not really. It’s relatively easy to swap the IP if the zone transfers are allowed to any server but otherwise these all need to be taken care off either in the GUI/CLI or PoSh. Also changing DNS IP addresses need to be communicated with and external partner that might be providing secondary DNS Services for your domain(s) and with your ISP where you registered the domain.
Pingback: Migrate a Windows Server 2012 R2 AD FS farm to a Windows Server 2016 AD FS farm - Working Hard In IT
thanks for the migration tutorial. Can i use the same procedure to migrate from dns server 2003 (!x86) to server 2016 (x64). Wins doesn’t support to copy mdb from x86 to x64 to migrate. Does DNS support this migration path (Run xcopy %windir%\system32\dns C:\DNSMigrateServer01 /s) ?
Thanks for your replay
I have not done it but it think it should work, I would try it out in the lab to validate the procedure anyway so give it a try to verify it works.
Careful – this tutorial only works if NO DNSSEC is used, because ZSKs und KSKs wouldn’t be the same and therefore all future DNS-requests would result in a SERVFAIL.
What do you do for migrating non-AD integrated with DNSSEC?
Disable, migrate, re-enable. I would try that.