Re: changing the entire network address space for the company- do's and donts!
- From: "ptwilliams" <ptw2001@xxxxxxxxxxx>
- Date: Sun, 24 Apr 2005 12:39:09 +0100
> create the new DHCP scope for the new network address space 172.61.16.x
> create the new DNS zones for the new network address space
> change the IP addresses of the DC's and static systems
> reboot.
I assume you mean Reverse lookup zones for this:
> create the new DNS zones for the new network address space
Anyway, your steps seem fine. However, it is recommended that you simply
configure the new IP addresses on the existing NICs as well as the old
addresses for the transition. You should also exclude the old scope so that
the DHCP server will issue NACs and the clients will be forced to get new
addresses.
You also need to check that the new IPs are registered in DNS and remove the
old ones (once transition is complete). You will also need to reconfigure
your sites and subnets in AD:
-- http://www.msresource.net/content/view/22/47/
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net
.
- Follow-Ups:
- Re: changing the entire network address space for the company- do's and donts!
- From: "Rebecca Chen [MSFT]"
- Re: changing the entire network address space for the company- do's and donts!
- References:
- Prev by Date: Re: best method to restrict application execution on terminal servers
- Next by Date: Re: Question about backup of the W2k server for forest prep
- Previous by thread: changing the entire network address space for the company- do's and donts!
- Next by thread: Re: changing the entire network address space for the company- do's and donts!
- Index(es):
Relevant Pages
|
