Change Acrive Directory IP Address

Question

Can we change ip of domain controller? I have DC running under window server 2016 and will upgrade to windows server 2022 with plan to make a new fresh install on new PC with Windows 2022.

After the DC 2022 with new ip and hostname is ready then i will promote this as domain controller and will turn off the old DC 2016 then DC 2022 will use the ip used by DC 2016.

Answer 1

Hello Handian,

Yes, you can change the IP of a domain controller, but it must be done carefully to avoid replication or DNS issues. The supported approach is to build your new Windows Server 2022 domain controller with its own hostname and IP, join it to the domain, promote it as a DC, and allow replication to complete. Once the old 2016 DC is demoted and removed, you can safely reassign its former IP to the new 2022 DC. This works because Active Directory identifies domain controllers by their GUID and hostname, not IP, but DNS records and clients often rely on the IP, so reusing it after the old DC is retired is fine. Just ensure you update DNS and verify replication health (dcdiag, repadmin /replsummary) before the cutover.

Harry.

Answer 2

Yes, you can change the IP address of a Domain Controller. This is fully supported, provided the change is performed correctly and DNS is updated accordingly.

In your scenario you are building a new Windows Server 2022 machine, promoting it as a new Domain Controller, retiring the old Windows Server 2016 DC, and then assigning the old IP address to the new server. This approach is valid, but it must follow a controlled sequence.

First, build the new Windows Server 2022 machine with a temporary static IP address. Configure its Preferred DNS server to point to an existing healthy Domain Controller. Join it to the domain as a member server.

Next, install the Active Directory Domain Services role and promote the server as an additional Domain Controller in the existing domain. Allow replication to complete fully.

Verify replication health using:

repadmin /replsummary repadmin /showrepl

Confirm SYSVOL and NETLOGON shares are available and ensure DNS is properly replicating.

After that, transfer FSMO roles if the old DC holds any.

Verify FSMO ownership using:

netdom query fsmo

If required, move roles using Move ADDirectoryServerOperationMasterRole in PowerShell.

Once the new Windows Server 2022 Domain Controller is fully operational and replication is healthy, demote the old Windows Server 2016 Domain Controller using Server Manager or Uninstall ADDSDomainController. Do not simply shut it down permanently without demotion unless it has failed and requires metadata cleanup.

After successful demotion and confirmation that no services depend on the old server, power it off.

Now you can safely change the IP address of the new Windows Server 2022 Domain Controller to the previous IP address used by the 2016 server.

After changing the IP address:

• Update its DNS Preferred and Alternate DNS settings appropriately
• Restart the Netlogon service
• Run ipconfig /registerdns
• Verify DNS A and SRV records in the _msdcs and domain zones
• Clear any stale DNS records related to the old DC

Use dcdiag /v to validate overall health.

Important considerations:

1. Never have two Domain Controllers online simultaneously using the same IP address.
2. Ensure no hard coded references exist to the old DC IP in applications, firewalls, or scripts.
3. If DHCP is involved anywhere, confirm reservations are not conflicting.
4. Confirm AD Sites and Services subnet configuration matches the intended IP subnet.

From an architectural perspective, reusing the old IP address is not technically required if DNS is functioning correctly. Active Directory relies on DNS name resolution, not fixed IP addresses. However, if legacy systems depend on the old IP, your approach is acceptable once the old DC is properly removed.

The critical success factors are clean demotion, healthy replication, and DNS integrity. If those are verified, the transition to the new IP will be seamless.

---

If this resolution has been helpful, I kindly request that you take a moment to click on

and select “Yes” to indicate that the response was helpful. Should you have any further questions or require additional assistance, please do not hesitate to let me know.

Answer 3

Yes, you can change the IP address of a domain controller (DC). When you set up a new DC running Windows Server 2022, you can assign it a new IP address and hostname. After the new DC is configured and promoted, you can then turn off the old DC running Windows Server 2016. If you want the new DC to use the same IP address as the old DC, you can reassign that IP address to the new DC after the old one is turned off. Just ensure that the new DC is properly configured and that there are no IP conflicts on the network.

Make sure to follow best practices for promoting a new DC and demoting the old one to ensure a smooth transition without disrupting your Active Directory services.

---

References:

• Upgrade domain controllers to a newer version of Windows Server
• Core network deployment