How to change Windows Domain controller 2012r2 IP address

%3CLINGO-SUB%20id%3D%22lingo-sub-1742098%22%20slang%3D%22en-US%22%3EHow%20to%20change%20Windows%20Domain%20controller%202012r2%20IP%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1742098%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20send%20us%20the%20step%20by%20step%20procedure%20to%20change%20IP%20address%20of%20the%20windows%20server%202012R2%20STD%20Domain%20controller.%20Also%20having%20the%20DHCP%20%26amp%3B%20DNS%20on%20the%20same%20server.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20this%20AD%20Server%20provides%20single%20sign%20on%20facility.%3C%2FP%3E%3CP%3ESo%20how%20we%20can%20seamlessly%20do%20the%20ip%20address%20changing%20without%20any%20impact.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%3C%2FP%3E%3CP%3EMitesh%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1742098%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EGeneral%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1744544%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20change%20Windows%20Domain%20controller%202012r2%20IP%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1744544%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F818774%22%20target%3D%22_blank%22%3E%40miteshnettelnetwork%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eas%20a%20best%20practice%20you%20should%20add%20a%20second%20domain%20controller%20which%20will%20be%20placed%20in%20the%20new%20subnet%20(and%20ideally%20not%20on%20the%20same%20virtualization%20host%20as%20the%20existing%20domain%20controller).%20Using%20only%20one%20DC%20is%20a%20critical%20single%20point%20of%20failure%20as%20nothing%20will%20work%20anymore%20if%20this%20DC%20fails.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20afraid%20you%20will%20not%20be%20able%20to%20simply%20switch%20the%20IP%20address%20on%20the%20existing%20DC%20without%20any%20impacts%20as%20all%20systems%20use%20this%20DC%20for%20authentication%20and%20have%20its%20IP%20stored%20in%20the%20DNS%20cache.%20So%20if%20you%20switch%20the%20IP%20address%20the%20systems%20will%20still%20try%20to%20connect%20to%20the%20old%20IP%20and%20therefore%20will%20run%20into%20authentication%20and%20DNS%20resolution%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20steps%20required%20for%20modifying%20all%20systems%20would%20have%20to%20be%20executed%20almost%20simultaneously%3A%3CBR%20%2F%3E1.%20Remove%20old%20IP%20address%20from%20DNS%20zone%20and%20register%20new%20ip%20address%20(ipconfig%20%2Fregisterdns)%20on%20DC%3C%2FP%3E%3CP%3E2.%20Modify%20DHCP%20settings%20to%20deploy%20new%20IP%20address%20(DNS%20server)%20to%20clients%3C%2FP%3E%3CP%3E3.%20Modify%20systems%20with%20static%20IP%20addressing%20to%20use%20new%20DNS%20IP%20address%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20add%20another%20domain%20controller%20and%20configure%20it%20to%20function%20in%20the%20same%20way%20as%20DC%201%20you%20are%20able%20to%20switch%20more%20smoothly%20and%20you%20are%20able%20to%20fail%20back%20in%20case%20of%20errors.%20So%20this%20would%20be%20the%20recommended%20way.%3C%2FP%3E%3CP%3E3.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello 

Can anyone send us the step by step procedure to change IP address of the windows server 2012R2 STD Domain controller. Also having the DHCP & DNS on the same server. 

 

Also this AD Server provides single sign on facility.

So how we can seamlessly do the ip address changing without any impact.

 

From

Mitesh

1 Reply

Hello @miteshnettelnetwork ,

 

as a best practice you should add a second domain controller which will be placed in the new subnet (and ideally not on the same virtualization host as the existing domain controller). Using only one DC is a critical single point of failure as nothing will work anymore if this DC fails.

 

I am afraid you will not be able to simply switch the IP address on the existing DC without any impacts as all systems use this DC for authentication and have its IP stored in the DNS cache. So if you switch the IP address the systems will still try to connect to the old IP and therefore will run into authentication and DNS resolution issues.

 

The steps required for modifying all systems would have to be executed almost simultaneously:
1. Remove old IP address from DNS zone and register new ip address (ipconfig /registerdns) on DC

2. Modify DHCP settings to deploy new IP address (DNS server) to clients (clients would have to reboot or reconnect to the network to get the updated config)

3. Modify systems with static IP addressing to use new DNS IP address

 

If you add another domain controller and configure it to function in the same way as DC 1 you are able to switch more smoothly and you are able to fail back in case of errors. So this would be the recommended way.

3.