Nt4 to w2k upgrade

  • Thread starter Thread starter P. Koster
  • Start date Start date
P

P. Koster

Hi,

Soon i will start the upgrade the pdc and bdc's in our network form nt4 to
w2k.
At the moment we are not using our own dns-servers, since we are upgrading
exchange 5.5 to 2k later on, we will need AD and AD needs DNS as i
understand.

We are now using dns-servers from our 'ISP' (not really an isp but more a
network provider) for name-resolution on the internet.

The domainname we are using is a 'characteristic' nt-domain, the fqdn of the
company is in use at our hosting party (not the ISP).

Schema is as following

1. Our network with the domain: ourcompany
2. Dns-servers at the ISP: dns1.isp.local & dns2.isp.local
3. Webserver at hosting-party www.ourcompany.nl

My problem is that we are bound to the 'ISP' because of political matters.
With this in mind, how and when should i setup DNS. Right now with nt4 still
running or during migration?

Best regards Peter
 
My problem is that we are bound to the 'ISP' because of political matters.
With this in mind, how and when should i setup DNS. Right now with nt4 still
running or during migration?
Click to expand...


Install DNS on your PDC when you upgrade it to Win 2k. Point it to itself in
the properties of TCP/IP.
See:
Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675



Point all AD clients to this DNS server ONLY.



Configure your AD DNS server to forward requests and list your ISP's DNS
servers as the forwarders.

See:

How to: Configure DNS for Internet Access In Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202





In order for your clients to log on properly, group policy to propagate,
your clients MUST point to a DNS server that hosts records for your domain.
Your ISP *most* likely will not allow your AD domain controllers to register
themselves on their DNS server and if they did those records would be
accessible to all (Not what you want).

When you create a DNS server for your AD domain, it will host records for
your domain, your DCs can and will register themselves and the clients
pointing to your AD DNS server can find the AD servers. Anything not
registered in this zone (basically the entire Internet) gets forwarded to
your ISP's DNS server for resolution.





hth

DDS W 2k MVP MCSE
 
Back
Top