asked on The steps and risk in swapping IP address of running 2x domain controller in same AD Site ?
Hi People,
I got 2x domain controller that is currently running:
OldDC2003 (Domain Controller / Global Catalog & DNS): 10.1.3.2
NewDC2012R2 (Domain Controller / Global Catalog, DNS, FSMO role holder): 10.1.3.200
they're both running fine and replicated with each other within the same AD site HQ.
I'd like to swap the IP address into:
OldDC2003 (Domain Controller / Global Catalog & DNS): 10.1.3.200
NewDC2012R2 (Domain Controller / Global Catalog, DNS, FSMO role holder): 10.1.3.2
Because there are lots of firewall and network switch to be changed. So what are the steps that I need to do and the risk involved ?
I got 2x domain controller that is currently running:
OldDC2003 (Domain Controller / Global Catalog & DNS): 10.1.3.2
NewDC2012R2 (Domain Controller / Global Catalog, DNS, FSMO role holder): 10.1.3.200
they're both running fine and replicated with each other within the same AD site HQ.
I'd like to swap the IP address into:
OldDC2003 (Domain Controller / Global Catalog & DNS): 10.1.3.200
NewDC2012R2 (Domain Controller / Global Catalog, DNS, FSMO role holder): 10.1.3.2
Because there are lots of firewall and network switch to be changed. So what are the steps that I need to do and the risk involved ?
Active DirectoryWindows Server 2003Windows Server 2012
Last Comment
Albert Widjaja
ASKER
I also have 13 other site offices with AD domain controller and DNS as well, so I'd like to know how it affects the replication if it is possible.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I was under the impression that I can just swap the IP address on the NIC configuration and then manually update the DNS records accordingly.
Would that cause an issue with Active Directory ?
Would that cause an issue with Active Directory ?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
@Zacharia Kurian: do you mean creating the another server to act as the 3rd IP address or staging IP while the both IP address is currently registered and used by running server ?
ASKER
The Technet article: https://technet.microsoft.com/en-us/library/cc758579%28WS.10%29.aspx somehow only suggest the IP to be changed into another free unused IP address, not the IP address that is in used by another Domain Controller.
So here's what I've been thinking based on your suggestion:
Changing OldDC2003 IP address:
Somehow, I wonder what could be happening in Steps #2 when the IP address of the OldDC2003 is now the same as NewDC2012R2 from the AD and DNS replication perspective ?
Since both of the IP address are used and registered by the running server, do I need to wait few hours or days before proceeding to the steps below:
Changing NewDC2012R2 IP address:
So here's what I've been thinking based on your suggestion:
Changing OldDC2003 IP address:
1. Turn off / shutdown the NewDC2012R2 server & unplug the network.
2. Change IP address (to match the NewDC2012R2 IP).
3. Open Command prompt and then run ipconfig /registerdns command.
4. Restart the NETLOGON service on the current OldDC2003 server.
5. Open Command prompt and then run dcdiag /fix command.
6. Check the AD/DNS replication and for any other error.
Somehow, I wonder what could be happening in Steps #2 when the IP address of the OldDC2003 is now the same as NewDC2012R2 from the AD and DNS replication perspective ?
Since both of the IP address are used and registered by the running server, do I need to wait few hours or days before proceeding to the steps below:
Changing NewDC2012R2 IP address:
1. Turn on the NewDC2012R2 server without the network connection.
2. Change IP address (to match the OldDC2003 IP).
3. Connect the network cable to the NewDC2012R2 server NIC.
4. Open Command prompt and then run ipconfig /registerdns command.
5. Restart the NETLOGON service on the current OldDC2003 server.
6. Open Command prompt and then run dcdiag /fix command.
7. Check the AD/DNS replication and for any other error.