Internal DNS server change

[David Swales]

Hi everyone,

We are about to migrate NT to Win2k & AD.
My internal clients (all Win2k) point at the NT PDC & BDC
for DNS and WINS, a seperate RAS box giving domain-wide
DHCP.
The existing PDC/BDC boxes are unsuitable for upgrade, so
two new boxes are SP6a ready for the migration, one
already now being PDC.
Not being very NT conversant, what is my best option for
giving the new boxes the old boxes' IPs, and DNS/WINS
services, then doing the Win2k upgrade, such that I do not
have to change the properties on my clients' NICs?

Many thanks in advance.

David

 

[Herb Martin]

Hi everyone,

We are about to migrate NT to Win2k & AD.
My internal clients (all Win2k) point at the NT PDC & BDC
for DNS and WINS, a seperate RAS box giving domain-wide
DHCP.
The existing PDC/BDC boxes are unsuitable for upgrade, so
two new boxes are SP6a ready for the migration, one
already now being PDC.

One quick solution is to temporarily leave these old dcs running just
as DNS/WINS and make them secondaries for DNS from the new
DNS server(s) and WINS partners.

Not being very NT conversant, what is my best option for
giving the new boxes the old boxes' IPs, and DNS/WINS
services, then doing the Win2k upgrade, such that I do not
have to change the properties on my clients' NICs?

Just take them offline and give the new boxes the addresses. Restart
the Netlogon service on each DC where you mess with the IP settings
or the NIC client DNS server.

One advantage of using DHCP that people often overlook when they
don't need "dynamic addressing" itself: You can dynamically change
such settings for hundreds or thousands of clients.