Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm considering changing the IP on a 2008 Domain Controller, anything that I should be aware of to look out for?

Will be doing this on a Saturday night to, leases renew every 24 hours so by Monday morning all the machines will have valid DHCP leases with correct DNS servers. Have a list of all machines on static IP so I know to update them while I'm at it.

share|improve this question
up vote 2 down vote accepted

You can safely change the IP address on a domain controller, just be sure to reboot it to ensure proper updating of DNS records and that all services running on the machine correctly acknowledge the change.

If the server is also running the DNS service you should be careful to update client settings, but looking at your question it looks like you've already taken this into account :-)

share|improve this answer

Active Directory finds it resources via DNS resource records. So changing the IP shouldn't cause problems. After changing the IP address; go into CMD mode and typeipconfig /registerdns Just remember to change its subnet in 'Sites and Services' to reflect the new IP address.

share|improve this answer
ipconfig /registerdns will not suffice, it will only register A and PTR records for the server; the actual SRV resource records are populated upon restarting Active Directory services. – Massimo May 24 '10 at 11:57

I have only done this with 2003, but:

  • If this is a new subnet, don't forget sites and services like Jake Mentioned.
  • Also, I ran into a catch-22 with the DNS IP. If it is configured to listen on a specific IP, make sure you change that in the DNS settings before changing the IP of the machine. If you don't, when you reboot DNS will fail, and you won't be able to change the settings on DNS either. There might be away around this, but this is what happened to me with the standard DNS console in 2003. I just gave the machine a secondary IP of the old IP so I could get into the DNS settings to add the new one, then removed the secondary IP when I was done.
share|improve this answer

Providing the DC isn't hosting any of the FSMO roles and isn't your sole DC, you might be better off demoting, changing the IP address and re-promoting it to ensure you don't end up with the old IP address anywhere.

Should on take 10-20 mins to do:

  • DCPromo - demote

  • Change IP address

  • DCPromo - promote

This way you can be sure the old IP address isn't anywhere in AD or DNS.

share|improve this answer
That's totally unnecessary and a lot more invasive than simply changing the IP address. – Massimo May 24 '10 at 10:48
@Massimo - I disagree I don't think you can be too cautious with Domain Controllers. Running De-promo/Promo really isn't a big deal - I always prefer a totally "clean" DC. – Jon Rhoades May 24 '10 at 12:51
"I don't think you can be too cautious with Domain Controllers"... right. That's exactly why I'd avoid promoting them back and forth unless absolutely needed. – Massimo May 24 '10 at 14:03

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.