Standalone dns migration from windows server 2012R2 to server 2022

Question

Hi,
In my organization we are planning to migrate standalone DNS server from windows server 2012R2 to server 2022.
We are planning migrate to different domain with new computer name of targated server. While transferring the zones or through backup and restore method it took the old server name and domain. Could you please assist how can I migrate our standalone DNS?

Or is there any method to remove old FQDN name from target DNS server?

Answer 1

This one could help.
https://www.informaticar.net/how-to-export-dns-zone-from-one-windows-server-and-import-to-another-non-ad-dns/

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Hi,

Depending on your specific needs the basic process is:

1. Export HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server key to .reg file using regedit on source server
2. Copy .dns files from source server to a temporary working folder
3. Modify .reg file to remove certain reg keys that shouldn't be imported on target, and add any additional reg keys/values that are required
4. Modify .dns files you copied above so that they have new FQDN for NS record as well as any other necessary changes. In your case it may be feasible to use TextPad or similar program to perform multiple file search & replace
5. Stop DNS Server service on target server using services.msc or net stop
6. Export HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server key (and its subkeys and values) on target server to .reg file for backup purposes
   Make copy of C:\Windows\System32\Dns folder on target server for backup purposes
7. Copy .dns files to target server's C:\Windows\System32\Dns folder
8. Import .reg file to target server by double-clicking on it while logged on to target server
9. Start DNS Server service on target using services.msc or net start
10. Check target server for warnings/errors related to DNS, perform nslookups against the server for various different domains to make sure they are returning correct results. Rollback your changes if there are any issues.

The above is for non-AD integrated domains only.

I recommend you create a test Server 2022 VM with DNS server running in it and use that to practice with and verify your process works.

IMPORTANT: Make certain that you are comfortable (practice!) with rolling back the changes to the target if you find something is wrong. For example, your rollback procedure might be to stop DNS Server, rename DNS Server reg key, import backup .reg file, rename Dns folder, copy backup Dns folder, Start DNS Server service. Test rolling back in your test VM and check that there are no problems with your rollback process. Also take a full backup and snapshot of the target VM just in case.

I've used above technique in the past for 1,200+ domains on older version of Windows Server. In my case I wrote custom program to create all of the .reg entries, .dns files with A, SOA, NS, MX, CNAME records. Since I wrote out all of the steps it appears like a lot of work, but in reality it is not that difficult.

-TP