Migrating into a new IP range
- Our headoffice current IP range starting to run out. I need to migrate the entire headoffice to a new subnet range in the near future. but I can't find any white paper or step to provide instruction on proper migration.
Environment:
1. All server are windows 2003 R2
2. Our headoffice currently house the following critical services - Active Directory (All master role are spread between 2 domain controller, DNS, DHCP (local subnet only), Exchange 2007, IIS and Wins.
3. We have 8 different statellite offices with their own subnet range connected via VPN - each statellite offices has their windows 2003 server which is acting as DHCP,DNS and Active directory.
Can someone give me some direction or possibly a link to a site.
thank you
Answers
Hi Nelson,
Here is the general guide on this issue:
For Domain Controller/DNS Servers
---------------------------------------------------------
- First change the IP address of the two DC/DNS servers one by one.
- If the DCs in this domain have DNS server running (which was the case in this
instance) make sure the DC's are pointing to each other for primary DNS.
- First take one DC, change it's IP address, subnet mask if needed, and default
gateway to the new range. DNS address should remain the same for now which would be
the IP of the other DC.
- Stop and start netlogon service and then on the command prompt, run IPconfig
/register DNS. Reboot Server (reboot is optional but recommended)
- Take the second DC and change the IP address, subnet mask if needed & default
gateway. Also, change the DNS IP to the new IP of the other server.
- Stop and start netlogon service and then on the command prompt, run IPconfig
/register DNS. Reboot Server (reboot is optional but recommended)
- Now on the first DC, change the DNS IP to point to the new IP of the second DC.
DNS
-------
- Verify that DNS on that domain's DNS servers reflects the new IPs of the DCs.
Check the A, SRV and NS records.
- If there are any DNS servers in other domains forwarding to the DNS server in
this domain. The forwarding addresses on those DNS servers will need updating to
the new addresses of the DNS servers in this domain.
- If any DNS servers have secondary zones for this domain's DNS zone, the
properties of those secondary zones will need updating to reflect the new IP
addresses.
- Similarly, if there are any DNS delegations in any DNS servers that point to this
domain's DNS servers, those will need updating with the new addresses as well.
Exchange
----------------
Exchange should not have any problems with the IP change. However, if there are any
MX records pointing to the exchange server's IP, they would need updating. Reboot
the exchange server after the IP change.
DHCP
----------
DHCP scope for this subnet will need to be recreated with the new IP range. The
DHCP reservations should be noted down so they can be recreated in the new scope.
Old DHCP scope should be backed up by backing up the DHCP.mdb file located in the
%SystemRoot%\System32\Dhcp folder
Also, the following registery key should be backed up:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DhcpServer\Configuration
Clients
----------
All clients should reboot after these IP changes are made.- Proposed As Answer byMeinolf WeberMVPWednesday, November 25, 2009 11:07 PM
- Marked As Answer byMiles ZhangMSFT, ModeratorTuesday, December 01, 2009 1:22 AM
All Replies
Hi,
Thanks for the post.
Please understand that there are several ways to increase the number of IP addresses on the subnet in DHCP server.
Increasing the number of IP addresses on a subnet in DHCP Server
http://support.microsoft.com/kb/255999
In this case, we can only use either of the two options: resubnetting or superscoping. For resubneting, you will also need to change server IP configuration manually and put a lot of efforts on the server re-configuration.
For superscope, you do not need to change IP configuration of existing computers; however, this puts an additional burden on the router or gateway configured with multiple logical subnets running on a single physical port. The additional burden may result in reduced network performance.
Thanks,
MilesThank you for the quick reply.. Unfortunately.. superscoping is not viable for our network. Can you provide some guidance on how to go about changing an entire subnet IP range into a different range?
Thank you in Advance..
NelsonHi Nelson,
Here is the general guide on this issue:
For Domain Controller/DNS Servers
---------------------------------------------------------
- First change the IP address of the two DC/DNS servers one by one.
- If the DCs in this domain have DNS server running (which was the case in this
instance) make sure the DC's are pointing to each other for primary DNS.
- First take one DC, change it's IP address, subnet mask if needed, and default
gateway to the new range. DNS address should remain the same for now which would be
the IP of the other DC.
- Stop and start netlogon service and then on the command prompt, run IPconfig
/register DNS. Reboot Server (reboot is optional but recommended)
- Take the second DC and change the IP address, subnet mask if needed & default
gateway. Also, change the DNS IP to the new IP of the other server.
- Stop and start netlogon service and then on the command prompt, run IPconfig
/register DNS. Reboot Server (reboot is optional but recommended)
- Now on the first DC, change the DNS IP to point to the new IP of the second DC.
DNS
-------
- Verify that DNS on that domain's DNS servers reflects the new IPs of the DCs.
Check the A, SRV and NS records.
- If there are any DNS servers in other domains forwarding to the DNS server in
this domain. The forwarding addresses on those DNS servers will need updating to
the new addresses of the DNS servers in this domain.
- If any DNS servers have secondary zones for this domain's DNS zone, the
properties of those secondary zones will need updating to reflect the new IP
addresses.
- Similarly, if there are any DNS delegations in any DNS servers that point to this
domain's DNS servers, those will need updating with the new addresses as well.
Exchange
----------------
Exchange should not have any problems with the IP change. However, if there are any
MX records pointing to the exchange server's IP, they would need updating. Reboot
the exchange server after the IP change.
DHCP
----------
DHCP scope for this subnet will need to be recreated with the new IP range. The
DHCP reservations should be noted down so they can be recreated in the new scope.
Old DHCP scope should be backed up by backing up the DHCP.mdb file located in the
%SystemRoot%\System32\Dhcp folder
Also, the following registery key should be backed up:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DhcpServer\Configuration
Clients
----------
All clients should reboot after these IP changes are made.- Proposed As Answer byMeinolf WeberMVPWednesday, November 25, 2009 11:07 PM
- Marked As Answer byMiles ZhangMSFT, ModeratorTuesday, December 01, 2009 1:22 AM
Hi,
I just want to check if the information provided was helpful. If there is any update on this issue, please feel free to let me know.
We are looking forward to your reply.
- Exactly what I was looking for , thank you guys!
