Change DNS servers
I currently have two servers with Widows Server 2012 with the DNS service and I need to replace it with two new ones with the same service with Windows Server 2016. What is the correct way to do it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
HI David,
As commented above install a new one let it replicate and shutdown the server and add an additional IP(old server's IP) in the new severs's NIC to avoid any name resolution issue. Once all the clients started working as expected remove the additional IP from the new server and start the old server and decommission the server.
Note: Remove DNS registration when you add additional IP.
https://www.simplyhosting.cloud/knowledgebase/operating-systems/configuring-an-additional-ip-address-on-windows-server
If you want you can add IP back after decommissioning to be safe but not when the old server is up/running.
As commented above install a new one let it replicate and shutdown the server and add an additional IP(old server's IP) in the new severs's NIC to avoid any name resolution issue. Once all the clients started working as expected remove the additional IP from the new server and start the old server and decommission the server.
Note: Remove DNS registration when you add additional IP.
https://www.simplyhosting.cloud/knowledgebase/operating-systems/configuring-an-additional-ip-address-on-windows-server
If you want you can add IP back after decommissioning to be safe but not when the old server is up/running.
Please clarify what do these do.
As Alex pointed cumulatively in both posts.
Presumably, DNS, DC, dhcp are part of that/those.
1) setup the new system
2) use the utilities on the 2016 to run adprep /domain /forest to get the 2012 ad to have a 2016 dc
3) add to the domain as a member or another DC presuming your sysvol is already using dfs replication and not ntfrs.
4) add DHCP rule without activation/authorization
5) you can use netsh DHCP server dump to get the current cobfiguration on the 2012 system which a portion can be populate the DHCP on the new server
Test before ...
Is this a virtualized or physical env?
As Alex pointed cumulatively in both posts.
Presumably, DNS, DC, dhcp are part of that/those.
1) setup the new system
2) use the utilities on the 2016 to run adprep /domain /forest to get the 2012 ad to have a 2016 dc
3) add to the domain as a member or another DC presuming your sysvol is already using dfs replication and not ntfrs.
4) add DHCP rule without activation/authorization
5) you can use netsh DHCP server dump to get the current cobfiguration on the 2012 system which a portion can be populate the DHCP on the new server
Test before ...
Is this a virtualized or physical env?
Actually
The DHCP server dump is utter sh.... Rubbish.
If you're migrating DHCP as well, you'll find that it won't be dishing out IP addresses correctly, when you run the export, import it on 2016 and then immediately export the scopes again, delete the scopes from DHCP and then re-import them with the 2016 export.
Regards
Alex
The DHCP server dump is utter sh.... Rubbish.
If you're migrating DHCP as well, you'll find that it won't be dishing out IP addresses correctly, when you run the export, import it on 2016 and then immediately export the scopes again, delete the scopes from DHCP and then re-import them with the 2016 export.
Regards
Alex
Seeing the config, you can speed up
The dump includes the reservation if any. It is a text file requiring a change of server name when applying the netsh commands to populate the new.
Using additional exclusion rule to make allocatable IPs on the new DHCP that will not clash with the existing.
The dump includes the reservation if any. It is a text file requiring a change of server name when applying the netsh commands to populate the new.
Using additional exclusion rule to make allocatable IPs on the new DHCP that will not clash with the existing.
I tried both in my past and I never ran into issues (with GUI and netsh)
I've done it between 2003 and 2012 and 2008r2 to 2016, had the same problem each time, you can jetpack the database but doing another export from the destination OS works as well.
Or at the very least get the DNS servers via powershell for all your servers.
Regards
Alex