Changing subnet of a domain controller

I have an AD site that has 3 subnets assigned to it.  These are for 3 different buildings connected by fast WAN.  We are moving the servers from one subnet to another including the domain controller (and DNS server) for that site.  It runs Windows Server 2008 R2.  I have changed the NIC on the server to point to another server in another site for DNS primarily now so my thinking is that we change the a and ns records on the other server, change the ip address of the dc and shut it down before moving it.  Once up in the new location change DHCP scopes to point at the new address for DNS.  (DHCP forwarding/relaying is enabled through switches) IT's DNS properties already listen on all interfaces and it only handles AD integrated DNS.  Has anyone done something like this and are there caveats to this I am missing?

Thanks in advance.
habs1994Asked:
Who is Participating?
 
Thomas WheelerConnect With a Mentor Commented:
makes sense but anytime I have done this I make a new site and attach the subnet then move the server and it automatically changes and updates for you so you have no worries.
0
 
Thomas WheelerCommented:
you will also want to change the site in AD sites and services
https://technet.microsoft.com/en-us/library/cc739015(v=ws.10).aspx
0
 
habs1994Author Commented:
The site that the server is in will not change.  Only the subnet within the same site that it resides in.
0
 
habs1994Author Commented:
Thanks for the info.  I will create a new site and attach all the old subnets, including the one that the domain controller will reside in after changing the IP of the DC and shutting it down.  I will bring it up in the new locale that physically resides in the subnet with the new address.
0
 
habs1994Author Commented:
Thomas, now that I have looked into this deeper...how do I create a new site without using an existing IP Inter-Site Transport?  Do I re-use the existing connection to create the site and then delete the old?  It seems that just changing the IP of the domain controller to the new subnet and then physically moving it would involve less steps.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.