Retiring old DNS Server - migrating to new one

Spammeh

Spammeh

Spammeh

Associate
Joined
2 Aug 2005
Posts
589
In the process of retiring our old 2003 Primary Domain Controller over to our new 2008 R2 server. It currently runs as the primary DNS server for all our clients on this site.

We've set up the new DC, and its set up as a DNS server. I've manually pointed my DNS on my machine at it - and there are no issues. The only problem we have is how to mass point all the machines on the domain to the new DNS server as opposed to the old one.

They all get their IP using DHCP from another DC, whose set up to point at the new DNS server, so i'd like to know how to force all the client machine to pick up the new DNS server as its primary so we can retire the old one

Cheers

Sam
 
Personally I would just leave them both on and let DHCP renew the leases, after a week or so you can just turn off the old server.

You can force the machines to renew with an ipconfig /renew if you must, I see no point in this though.
 
I would just leave it on a few days until all the DHCP clients have renewed their leases. (note renewal happens at 1/2 the total lease time).
If you're desperate to get that server down for some reason you could pop an ipconfig /renew in the logon script for a day or so. However this could cause issues depending on your environment and what else your logon script does.
 
I've set myself to DHCP (as I've usually got a static IP)for a short while, released and renewed and its still setting my primary DNS as the old server. any ideas?
 
You must log in or register to reply here.
Back
Top Bottom