A way to use DNS forwarders and still list ISP DNS servers?

  • Thread starter Thread starter MyndPhlyp
  • Start date Start date
M

MyndPhlyp

One thread in this NG uncovered a nit I've been tolerating for some time but
I'd like to find a way to make this work.

The symptom was that local machines would appear to "stall" periodically
whenever the WAN services were not available even though no user
applications were attempting to access the WAN. The cause appears to have
been that the WAN DNS machines were listed in the LANs DHCP Option 006 along
with the LAN DNS machine. Removing the WAN DNS machines from that DHCP
option seems to have cleared up the symptom (but the jury is still out).

All machines (currently all Win2K but I work with a mixed bag) are connected
to a common hub (firewall/router) that uses PPPoE to connect to the ISP via
a DSL modem.

The Win2K server is set up with AD, DNS, DHCP, WINS. DNS has forwarders to
the ISPs DNS machines. DHCP Option 006 is currently set up listing only the
inside DNS.

All workstations use the hub as a gateway rather than utilizing connection
sharing at the server.

Occasionally I'll take the Win2K server off the hub obviously making it's
DNS service (and the accompanying forwarding) unavailable.

Is there a way to allow the workstations to have the ISPs DNS machines
listed in their TCP/IP configuration without causing the "stalling" symptom
when the WAN is down?
 
Is there a way to allow the workstations to have the ISPs DNS machines
listed in their TCP/IP configuration without causing the "stalling"
symptom
when the WAN is down?
Click to expand...


Clients of an AD domain should only have the DNS servers listed that hold
the SRV records for the domain. Having any other DNS server listed that does
not hold the SRV records for the domain will cause the client to "stall"
while it searches (unsuccessfully) for the SRV record that is not there.

hth
DDS W 2k MVP MCSE
 
Danny Sanders said:
Clients of an AD domain should only have the DNS servers listed that hold
the SRV records for the domain. Having any other DNS server listed that does
not hold the SRV records for the domain will cause the client to "stall"
while it searches (unsuccessfully) for the SRV record that is not there.
Click to expand...

So the natural conclusion is that one cannot (should not) configure an AD
domain client to have WAN DNS machines listed and if the AD domain's DNS
machine is unavailable, thereby removing the forwarders, the AD clients are
SOL?
 
Back
Top