Update Primary DNS Server IP on a 2008 R2 Domain Controller - Is Reboot Needed?
Posted on 2015-02-04
We have 2 physical sites (East Coast and West Coast).
East Coast is HQ
West Coast is Branch
The two offices are on different IP subnets.
The West Coast branch office has a single Windows Server 2008 R2 DC. It's DNS settings are as follow:
DNS1 IP Address of a DC in the East Coast HQ Office
DNS2 Its Own IP Address
The issue we have is the East Coast HQ DNS1 server is a Virtual Server (Hyper-V). We'd prefer to have the west coast office point to a "physical" DC on the east coast instead of a VM.
We just went in and simply changed the primary DNS IP on the west cost DC to use a different physical DC on the East Coast.
KEY QUESTION - Do we now need to reboot the west coast DC or will all the active directory replication services, etc. detect this change accordingly?
I remember reading somewhere that when you make a change to TCP/IP DNS settings on a DC, you should reboot the DC for the change to take full effect. Of course, that article may have simply been referring to a TCP/IP settings change on a 2003 server since that OS did not do immediate TCP/IP settings changes the way 2008 R2 does.
If we wait it out and do not reboot, how long before the change will take full effect in the system? A full replication cycle?
Please help clear this up for us and provide a link to a relevant article explaining if possible. We can't seem to find a good article describing whether a reboot is needed or not.