Score:0

How to IMPORT complete DNS text Record to Windows Server 2016?

ph flag

I have reinstalled a Windows 2016 server. I am trying to re-establish my DNS records which I backed up prior to the NEW install. When my DNS records import it ONLY shows the SOA record and has NO details included (eg NS1 or NS2), especially considering it knows the domain from its name you supply during the process. All of the DNS exports had ALL the DNS data but NONE has been READ back into the new server.

I used the DNSCMD method to load, after the Wizard failed to read the records properly. Neither method works. The DNS is accessed using the elevated admin permissions. The processes work fine without error, but NO DNS records.

The exact same issue is in both Forward and Reverse Lookup zones. Why is it so difficult to IMPORT a text file that has ALL the information???

It looks like none of this has changed since windows server was invented and it still cannot simply do the most basic and critical things you would expect from a web server in 2021.

Thankyou for your time, if you provide an answer to this issue.

djdomi avatar
za flag
is that a primary or secondary dns?
joeqwerty avatar
cv flag
`1.` Tell us exactly how you exported your DNS zones, show us the exact command(s). `2.` Show us a sample of the DNS zones you exported. `3.` Stop blaming Microsoft because YOU can't get it to work.
Score:0
ph flag

It was all primary DNS. It is a basic web server serving a handful of basic asp.net apps. On each DNS I used export list which exports simplistic tab delimited *.dns file. This was done individually for each Forward and Reverse DNS. There is no point for me to show the records as they are the same 'format' as any exported dns file.

Even though DNSCMD is being retired and replaced by powershell for this task, it was used to load the dns zone data back in. The dns file was placed in the new dns system folder and the file was read using DNSCMD commands but did only resulted in an SOA record with nothing in it. This despite the fact that the dns text files were unchanged and in their proper folder. The recordadd switch is cumbersome at best and its use is more akin to a command line 101 typing exercise. It is faster to start from scratch using the gui. The reality is there are only 'n' types of dns records which need to be dealt with in a dns file such as SOA, A, CNAME, MX, TXT etc. They have finite fields and settings.

The simplest and most commonsense solution should be achievable by simply backing up the text files from the old 'dns' folder and then placing them back into into the 'dns' folder of the newly reinstalled server. Its *.dns files and subfolders would be wholly intact and unchanged. A refresh command that does something could read the text files and that should be all that is required. Server DNS recovery would be complete in seconds, not hours.

On the microsoft 'Windows Server' to do list a DNS 'import' gui option would be very useful as the current DNSCMD methods are decades old. If there is an 'export' there should be an 'import'. Alternatively a single powershell import command to read any one or all DNS backups back to their respective positions. The convoluted methods required currently should not be required for such a simplistic task.

A useful software update may include a new command to export DNS records to the Azure DNS repository account. Then the DNS role feature may not even need to be installed on a basic windows web server.

I was on my way to closing this question before anyone replied. Please don't waste your time adding answers as the issue has been resolved. DNS records were transferred to Azure, and a single A record was added locally for the internal IP address as the server is on premise. I will undertake tests to identify if I can remove the DNS role altogether and rely wholly on Azure.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.