Ask a question

Michael Gibbs

DNS Script reports no DNS configured on new server

I have reached the stage where you recommend running the scripts to set the IP address of the opposite DC to be the DNS server.

From the new server ,\SetDNSonWSE2019.ps1 sets the IP of the DNS server to the old server and the alternative to 127.0.0.1 - correct

From the old server I run  .\SetDNSonWSE2012.ps1 and input the IP address of the new server
It first returns the following message
"There are no Domain Name Servers (DNS) configured on this computer."
and then sets the preferred DNS server to itself with 127.0.0.1 as the alternative.

The line to install the roles ran ok and the AD shares for NETLOGON and SYSVOL are present on both servers. There is also a DNS server running on the new server.

Should I just manually set the DNS server to the new server from the old?


asked03/01/2021 12:26
53 views
Add Comment
Mariette Knap

Not sure why it does that but can you set preferred DNS server IP address to the new server on the old server alternative to 127.0.0.1. Pls, post an ipconfig /all from both servers to see if all is OK?

Michael Gibbs

I also note that there are two forwarders on the old server that are set to the DNS server address of the ISP. On the new server one forwarder has been set which points back to the old server. All other entries appear to be as expected with the Forward Lookup Zone for the AD Domain populated as expected.

Mariette Knap

I also note that there are two forwarders on the old server that are set to the DNS server address of the ISP. On the new server one forwarder has been set which points back to the old server. All other entries appear to be as expected with the Forward Lookup Zone for the AD Domain populated as expected.

That is as expected.


replied 03/01/2021 13:03
Michael Gibbs

ipconfig outputs attached, thanks

Attached Files

replied 03/01/2021 13:23
Last Activity 03/01/2021 13:23

No answers found

Add an Answer