Windows OS Hub
  • Windows
    • Windows 11
    • Windows 10
    • Windows Server 2025
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
  • Microsoft
    • Active Directory (AD DS)
    • Group Policies (GPOs)
    • Exchange Server
    • Azure and Microsoft 365
    • Microsoft Office
  • Virtualization
    • VMware
    • Hyper-V
    • Proxmox
  • PowerShell
  • Linux
  • Home
  • About

Windows OS Hub

  • Windows
    • Windows 11
    • Windows 10
    • Windows Server 2025
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
  • Microsoft
    • Active Directory (AD DS)
    • Group Policies (GPOs)
    • Exchange Server
    • Azure and Microsoft 365
    • Microsoft Office
  • Virtualization
    • VMware
    • Hyper-V
    • Proxmox
  • PowerShell
  • Linux

 Windows OS Hub / Active Directory / Best Practices: Changing the IP Address on a Domain Controller

June 23, 2025

Best Practices: Changing the IP Address on a Domain Controller

Changing the IP address of a domain controller in Active Directory is a non-standard operation that could disrupt domain services and affect client connectivity. However, if properly planned and executed, changing a domain controller’s IP address should not negatively impact the Active Directory infrastructure.

In this case, the domain controller (mun-dc02) has a static IP address 192.168.13.14. Due to a change in the network’s IP addressing scheme, this IP address needs to be changed to 192.168.113.14.

Before changing the IP address in the network adapter settings on a domain controller (DC), perform a series of pre-checks:

  • It is assumed that you have deployed several additional domain controllers in your network
  • Make sure that none of the domain Operation Master roles are running on mun-dc02 (If there are any, transfer the FSMO roles to a different DC): netdom query fsmo
    netdom query fsmo
  • If your DC has a DHCP server running, it is recommended to reconfigure it in advance so that it immediately starts assigning the new DC IP address to clients as an alternate DNS server. If applicable, you also need to plan to reconfigure the DHCPRelay options on the routers immediately after changing the IP address.
  • Before changing the IP address, check the status of the domain controller and replication health:
    dcdiag.exe /s:mun-dc02 /q
    repadmin /replsum
    repadmin /showrepl

    Ensure that all tests return no errors, or fix any errors found.
    Learn how to check the health of an AD domain controller.
  • Verify that the preferred DNS server set in the network connection settings is the address of another DC on the same AD site. Also, verify that the alternate DNS server is set to loopback (127.0.0.1), as recommended by Microsoft. Set Preferred/Alternate DNS servers on a domain controller
  • If you change both the IP address and the subnet, make sure that the new IP subnet is added to the AD sites and assigned to the correct site. Check the subnets and AD site assignments
  • Identify all devices that use the IP address of the old domain controller as a DNS server. You can enable logging of all DNS queries and get a list of devices that use DNS on this DC. Issues frequently occur with network devices, such as printers, scanners, and infrastructure equipment, when their TCP/IP settings are configured manually. Locate and identify these devices in your network and verify that at least two DNS servers’ IPs are set in their settings.
  • If firewalls restrict access between network segments in your environment, create firewall rules for the new IP address in advance (on Windows devices, Microsoft Defender Firewall rules can be added via GPO).

Once you have completed the preparatory steps, you can proceed with changing the domain controller IP address:

    1. Schedule the time for the IP address change during a service window with the least possible downtime for users.
    2. Connect to DC. Preferably, connect to the host console (if it is a virtual machine) or the physical server management interface (iLO, iDRAC, KVM-over-IP, etc.) instead of RDP.
    3. Open the Network Connections control panel (ncpa.cpl), then open the properties of the network adapter, and change the IP address and subnet (if necessary). Save the changes. change the IP address on a domain controller
    4. Then, purge the local DNS cache and re-register the server in DNS:
      ipconfig /flushdns
      ipconfig /registerdns
    5. Update the DNS records for the domain controller. This will also update the SRV records in the _msdcs, _sites, _tcp, and _udp zones. Restart the Netlogon service:
      nltest /server:mun-dc02 /dsregdns
      net stop dns & net start dns
      net stop netlogon & net start netlogon

      ipconfig /registerdns - update DNS
    6. Run the dcdiag /fix command to update the computer account SPN attributes
    7. Then run the DC health check again:dcdiag.exe /s:mun-dc02 /q
    8. Open the DNS Manager console to confirm the DNS records for the domain controller have been updated. Verify that the new IP entries in the forward and reverse DNS zones have been created correctly. Adjust them if necessary. Any remaining records for the old IP address must be deleted manually. Check the new IP address of a DC in the Windows DNS
    9. If used, remove the old DC IP address from the DHCP zone settings. Set the new IP address in the DNS settings for devices with static IP configurations. You can use PowerShell to change the DNS settings on remote computers.
0 comment
0
Facebook Twitter Google + Pinterest
Active DirectoryQuestions and Answers
previous post
How to Detect Which User Installed or Removed a Program on Windows

Related Reading

Refresh AD Groups Membership without Reboot/Logoff

March 15, 2024

How to Find the Source of Account Lockouts...

March 12, 2024

Configuring Windows Firewall Rules Using Group Policy

March 15, 2024

Allow Non-admin Users RDP Access to Windows Server

March 16, 2024

How to Disable NTLM Authentication in Windows Domain

March 16, 2024

Copy Files and Folders to User Computers via...

March 15, 2024

Configure Windows LAPS (Local Administrator Passwords Solution) in...

March 15, 2024

Extend an Expired User Password in Active Directory

December 23, 2024

Leave a Comment Cancel Reply

join us telegram channel https://t.me/woshub
Join WindowsHub Telegram channel to get the latest updates!

Recent Posts

  • Encrypt Any Client-Server App Traffic on Windows with Stunnel

    June 12, 2025
  • Failed to Open the Group Policy Object on a Computer

    June 2, 2025
  • Remote Desktop Printing with RD Easy Print Redirection

    June 2, 2025
  • Disable the Lock Screen Widgets in Windows 11

    May 26, 2025
  • Configuring Windows Protected Print Mode (WPP)

    May 19, 2025
  • Map a Network Drive over SSH (SSHFS) in Windows

    May 13, 2025
  • Configure NTP Time Source for Active Directory Domain

    May 6, 2025
  • Cannot Install Network Adapter Drivers on Windows Server

    April 29, 2025
  • Change BIOS from Legacy to UEFI without Reinstalling Windows

    April 21, 2025
  • How to Prefer IPv4 over IPv6 in Windows Networks

    April 9, 2025

Follow us

  • Facebook
  • Twitter
  • Telegram
Popular Posts
  • Check Windows 11 Hardware Readiness with PowerShell Script
  • Extend an Expired User Password in Active Directory
  • AD Domain Join: Computer Account Re-use Blocked
  • Configure DNS Scavenging to Clean Up Stale DNS Records in AD
  • Collecting Windows and Active Directory Event Logs with Graylog
  • Exclude a Specific User or Computer from Group Policy
  • Error: The Specified Domain Doesn’t Exist or Couldn’t Be Contacted
Footer Logo

@2014 - 2024 - Windows OS Hub. All about operating systems for sysadmins


Back To Top