Resolving a specific zone with a specific DNS

  • Thread starter Thread starter Jonathan de Boyne Pollard
  • Start date Start date
J

Jonathan de Boyne Pollard

P> Is there a way do to this without creating a secondary zone
P> and doing zone tranfer ?

Yes. There are actually two: conditional forwarding and stub zones.
 
I actually have a W2K DNS server who is resolving dns request from clients
computer. It is not working under an Active Directory environment.

For a specific purpose I need to resolve dns requests for a specific domain
name (A private one, not registered on the internet) with an other dns
server. So i want that the name resolution request for this domain to be
forwarded to an other DNS server, not the root-servers on the Internet.

Is there a way do to this without creating a secondary zone and doing zone
tranfer ? Someone told me that it is possible under Unix/Linux, but I want
to do it under Win2K.

Thank you !

PLP
 
For a specific purpose I need to resolve dns requests for a specific
domain
name (A private one, not registered on the internet) with an other dns
server. So i want that the name resolution request for this domain to be
forwarded to an other DNS server, not the root-servers on the Internet.
Click to expand...

Add a forwarder on your existing DNS server, pointing to the special name
server is question. That'll do it.
 
In
posted their thoughts said:
But do it will only forward request for this specific domain ? Is
their a way to specify a domain to forward ?

Thank you for your help.

PLP
Click to expand...


That's called conditional forwarding and is available with Win2k3, not
Win2k.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
BIND can do it. Windows 2000 cannot.

PLP said:
But do it will only forward request for this specific domain ? Is their a
way to specify a domain to forward ?

Thank you for your help.

PLP
Click to expand...
 
He has a compelling reason to upgrade to Windows 2003 DNS (or, as he
suggested, switching to a Unix or Linux DNS server), then.
Click to expand...

Sure does :) I haven't tried the 2003 DNS server, but most of the
documentation indicates that they're really starting to standardize, perhaps
in a long overdue attempt to offer a realistic BIND alternative.
 
In
posted their thoughts said:
Sure does :) I haven't tried the 2003 DNS server, but most of the
documentation indicates that they're really starting to standardize,
perhaps in a long overdue attempt to offer a realistic BIND
alternative.
Click to expand...

It's a great operating system!!!

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
KWM> I haven't tried the 2003 DNS server, but most of the
KWM> documentation indicates that they're really starting to
KWM> standardize, perhaps in a long overdue attempt to offer
KWM> a realistic BIND alternative.

As far as I can tell, the 2000 DNS server adhered to the standards reasonably,
and the level of standards conformance isn't changed all that much in the 2003
DNS server. (Incidentally: Strict conformance with the DNS standards, and
various other ancillary RFCs, is a tricky matter and not actually wholly
desirable. The RFCs aren't well written, having predated much of the
formalisation of RFCs; they use an idiosyncratic terminology that is wildly at
variance with the terminology used in most other RFCs for equivalent entities
and that is not always used consistently; and they are downright wrong in
places.)

What _has_ been one of the major changes in the 2003 DNS server is the
addition of _non-standard_ features to match non-standard BINDisms, such as
the conditional forwarders and "stub zones" that were mentioned before. These
are not specified by any DNS standards.
 
Back
Top