Archived from groups: microsoft.public.win2000.dns (
More info?)
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]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:OS#dNgEWEHA.3740@TK2MSFTNGP12.phx.gbl...
> In news:utz7DW7VEHA.1764@TK2MSFTNGP10.phx.gbl,
> Sneakie <sneakie@absamail.co.za> posted their thoughts, then I offered
mine
> > 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. --
> =================================
>
>