Clients do not fail over to secondary DNS if primary fails

  • Thread starter Thread starter Akuinnen
  • Start date Start date
A

Akuinnen

2 win2k AD DNS servers
Win2k clients
Both DNS servers work, no problems. Both DNS servers are listed on the
client machines. Everything is running great for months.

Overnight the primary DNS server crashes. It can't be accessed by
TCP/IP.. it's dead. In the morning the users get in and can't resolve
domain names. Again both servers are still listed as DNS servers on
the client machines. Client machines are trying to access the primary
DNS server which has failed.

If the primary DNS entry is removed from the ipconfig and replaced
with the secondary DNS, clients are then able to resolve domain names.

Why do the clients continue to try to resolve DNS through the primary
even though it doesn't respond and the secondary works fine? Why don't
they flag the primary as non-responsive after a time out period and
goto the secondary?
 
Back
Top