DNS resolution question

  • Thread starter Thread starter Rejean Roy
  • Start date Start date
R

Rejean Roy

We use to have a network containing Windows NT
workstations. Also, we do have 2 bind server hosting 2
differents zones (one is hosting xxx.yyy and the other
one hosts rrr.zzz); we are usgin this configuration
because we do not have control on the DNS. With NT 4, we
used 1 DNS server as primary and the other one as
secondary. When we trying to resolve an adress that the
primary zone do not hosts, NT 4 used the secondary to
resolve the adress (if we trying to resove abc.xxx.yyy
the primary DNS answer; if we trying to resolve
abc.rrr.zzz, NT do a query to the primary, get not
resolve so it tries the secondary to get an answer).

Now my problem is with Windows 2000 or XP, it doesn't
seems to work like that. It simply try the fisrt DNS, it
the name it not resolve it doesn't continu by trying the
secondary DNS; it simply reply unknow hosts.

Does it have a way to chnage the way it works without
chnaging DNS configuration. Maybe a registry key.

Thanks for help


Rejean Roy. MCSE
(e-mail address removed)
 
W2K-server wants DNS-server installed and DNS on the servernic(s) should
point to the server-IP only. The ISP-DNS-numbers should be set in tab
Forwarders of DNS-server.
All clients should point to the server-IP for gateway, DHCP, DNS and WINS.

Marina
 
The fonctionnality I am trying to have in W2K pro is the
one discribed in Q195611:

The DNS query algorithm has been modified to attempt
other servers in the server list if an error is received
from a server that may be resolved by trying another
server in the list. The new algorithm will retry servers
until:

The name query is answered successfully.
An authoritative answer is received from a server that
the requested host does not exists (rcode 3).
The server list is exhausted.
 
I understand that but we do not have control of the DNS.
I am looking for a way to reproduce the NT4
functionnality like discribe in Q195611

The DNS query algorithm has been modified to attempt
other servers in the server list if an error is received
from a server that may be resolved by trying another
server in the list. The new algorithm will retry servers
until:

The name query is answered successfully.
An authoritative answer is received from a server that
the requested host does not exists (rcode 3).
The server list is exhausted.
 
There is no way to directly replicate this behavior.
Nor is that behavior "correct" in the sense that it is
the way DNS resolution should act. Which is no comfort
to you I realize, but it does mean you probably shouldn't
wait around for some kind of "fix".

The only way I can think of to make this work is
to turn up your own local DNS server with Win2K3
Server and use conditional forwarding on those zones.
Other than this you are stuck with hosts files, etc.

Steve Duff, MCSE
Ergodic Systems, Inc.
 
Back
Top