change subnet

  • Thread starter Thread starter eddiec
  • Start date Start date
E

eddiec

hi everyone,

our company has been bought therefore we have to change our AD W2K subnet
address in order to fit in with the new companies addressing scheme. This is
the plan

1) Ensure that only one DNS and DHCP server remain on the network.

2) Shut down all other servers

3) Delete the DNS zone

4) Change the IP address for this server on the NIC

5) Change the DHCP range

6) Recreate the forward and reverse lookup zones with appropriate A records

7) Power on the other servers

8) Change their IP addresses

9) Change the IP address of the firewall and change NAT entries as
appropriate

Is this liable to succeed or will I trash my network?

TIA

EddieC
 
eddiec said:
hi everyone,

our company has been bought therefore we have to change our AD W2K
subnet address in order to fit in with the new companies addressing
scheme. This is the plan
Click to expand...

Unless the company that bought yours is using the exact same subnet, it is
unlikely you need to change your IP addresses. Unless, the two companies are
going to be totally merged into one location.
1) Ensure that only one DNS and DHCP server remain on the network.
Click to expand...

If both companies are using AD it is unlikely this is possible, due to zone
security problems for AD integrated zones. But both DNS servers must be able
to resolve the other's domain. You can do this through the use of Secondary
zones on Win2k or conditional forwarders on Win2k3.
2) Shut down all other servers

3) Delete the DNS zone

4) Change the IP address for this server on the NIC
Click to expand...

You should never just change the IP address on a DC, add the new address,
then after the DC has registered the new address and the clients DNS server
list has been updated and communication to the new address is verified,
remove the old address.
5) Change the DHCP range
Click to expand...

This is out of order, DHCP should be changed before the old address is
removed.
6) Recreate the forward and reverse lookup zones with appropriate A
records
Click to expand...

Forward zones will be updated by DDNS, will need to create a reverse zone.
7) Power on the other servers

8) Change their IP addresses

9) Change the IP address of the firewall and change NAT entries as
appropriate

Is this liable to succeed or will I trash my network?
Click to expand...

If not done in the right order, it is likely to trash domain communication.

The simple way to achieve this, and this depends on what you are really
trying to achieve, is to set up a VPN link between the two networks, Then
create secondary zones for the other domain on each DNS, and create a trust
between to two domains. Then, if you plan on merging into one domain use
ADMT to move accounts from one domain to the other.
 
Back
Top