dns on win2000 on NT4 domain

  • Thread starter Thread starter Sneakie
  • Start date Start date
S

Sneakie

Is it possible to configure a dns server on an NT4 domain with all clients
using win 2000.
Unfortunately, the domain name is "domain"
We have already configured DHCP on 2000 and it's working well.
(We will be migrating to a 2003 domain shortly)

Thanks

Pierre
 
Pierre,

You can setup a Windows 2000 DNS server on an NT domain. Just leave the DNS server as stand-alone (do not join it to the domain) and set up a primary standard zone.
 
Hi Jason,

The server that's running the DNS is also my dhcp, and wins server. It is a
member of the domain already. What is the reason for not joining it to the
domain?

Thanks for your appreciated help.

Pierre
J Parks said:
Pierre,

You can setup a Windows 2000 DNS server on an NT domain. Just leave the
DNS server as stand-alone (do not join it to the domain) and set up a
primary standard zone.
 
In
Sneakie said:
Is it possible to configure a dns server on an NT4 domain with all
clients using win 2000.
Unfortunately, the domain name is "domain"
We have already configured DHCP on 2000 and it's working well.
(We will be migrating to a 2003 domain shortly)

Thanks

Pierre


Sure, no problem. Actually it's your best bet to setup the infrastructure
first and insure DNS, DHCP and WINS functions cleanly prior to an upgrade,
especially for DNS.

As for the single label name, under NT4 that;s fine, but when you choose an
AD DNS Domain name, it needs to be in the form of at least two levels, such
as 'domain.com'm domain.net', etc, but preferrably NOT your external domain
name. Configure a forwarder and just point all your current machines to this
DNS for Internet resolution. Since NT4 doesn't require DNS, you can still
use it.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Hi Jason,

The server that's running the DNS is also my dhcp, and wins server. It is a
member of the domain already. What is the reason for not joining it to the
domain?

None. I think he meant configure as a member server, not a domain
controller.

Jeff
 
Thank you for your assistance.
I am not sure how to configure a 'forwarder' as you mentioned. Also why
would I use more than 1 zone?

Thanks

Pierre

"Ace Fekay [MVP]"
 
In
Sneakie said:
Thank you for your assistance.
I am not sure how to configure a 'forwarder' as you mentioned. Also
why would I use more than 1 zone?

Thanks

Pierre

To configure a forwarder, see this article and use your ISP as the
forwarder. You can also use 4.2.2.2, which is reliable.
http://support.microsoft.com/?id=300202


More than one zone? I didn't mention anything about multiple zones. I just
mentioned that your AD domain name must be in the form of domain.com,
domain.net, domain.local, domain.sneakie, etc, but cannot be in the form of
just "DOMAIN" (a single label name) or numerous errors will result out of
this choice. You can read back in the newsgroup about people having problems
with a single label name.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top