Reuse old domain controller IP address

Posted on

A server stack is the collection of software that forms the operational infrastructure on a given machine. In a computing context, a stack is an ordered pile. A server stack is one type of solution stack — an ordered selection of software that makes it possible to complete a particular task. Like in this post about Reuse old domain controller IP address was one problem in server stack that need for a solution. Below are some tips in manage your windows server when you find problem about windows, active-directory, windows-server-2008-r2, windows-server-2012, domain-controller.

We currently have 2 Windows Server 2008 R2 domain controllers, and I want to replace one of them with a Server 2012 R2 DC. I also want to reuse the IP address after I demote the old DC.

What is the best way to do this and will reusing the old IP cause any problems?

  • Build the new server
  • Give it a temporary IP address
  • Join it to the domain
  • Promote it to DC (you could need some adprep if this hasn’t already been done)
  • Add required additional services (DNS, etc.)
  • Move FSMO roles if required
  • Change the IP address of the old DC to a temporary one
  • Reboot the old DC two times
  • Wait some time for replication (an hour should be more than enough)
  • Give the IP address of the old DC to the new DC
  • Reboot the new DC two times
  • Wait some time for replication (an hour should be more than enough)
  • Demote the old DC
  • Leave the old DC in service if there are more data or services on it, otherwise just shut it down.

“Best” is highly subjective, but you can re-use the same IP address after you demote the domain controller. You just need to make sure that the references to the old domain controller are gone from Active Directory before promoting a new domain controller at that IP address, and keep in mind that client computers may need to reboot (or at least refresh their network connection) if they have any cached/inactive sessions with the old domain controller.

And, no, it doesn’t cause any problems. I’ve done it myself many, many times myself when I don’t want to go through the hassle of updating manually-configured DNS server records on a whole bunch of computers.

Leave a Reply

Your email address will not be published. Required fields are marked *