DNS timeouts

  • Thread starter Thread starter NAN
  • Start date Start date
N

NAN

On a client pc, what is the timeout period to go to the
2nd listed DNS server, if the primary DNS listed is
offline? So - how long before it will try contacting the
2nd dns server?
THanks.
 
NAN said:
On a client pc, what is the timeout period to go to the
2nd listed DNS server, if the primary DNS listed is
offline? So - how long before it will try contacting the
2nd dns server?
THanks.
Click to expand...

3 tries, 2 seconds each. But it won't go back to the previous entries unless
you restart the machine or the DNS client service. There's an article
explaining all this. When I get home, I can post it.

Keep in mind a rule of thumb, in an AD environment, don't mix internal and
your ISP's DNS, just use the internal DNS only and configure a forwarder so
you won't have to worry how the client side resolver works or any need to
minupulate 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
 
Two great knowledge base articles that describe how this works are:

261968 - Explanation of the Server List Management Feature in the Domain
Name Resolver Client (http://support.microsoft.com/?id=261968).

286834 - The DNS Client Service Does Not Revert to Using the First Server in
the List (http://support.microsoft.com/?id=286834).

--
J.C. Hornbeck, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
 
I would appreciate it.
Thanks.
-----Original Message-----



3 tries, 2 seconds each. But it won't go back to the previous entries unless
you restart the machine or the DNS client service. There's an article
explaining all this. When I get home, I can post it.

Keep in mind a rule of thumb, in an AD environment, don't mix internal and
your ISP's DNS, just use the internal DNS only and configure a forwarder so
you won't have to worry how the client side resolver works or any need to
minupulate 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
--
=================================


.
Click to expand...
 
Pretty much the same way. That's why the mutliple entries are meant as a
fault tolerance mechanism rather than a load balancing mechanism.

Ace
 
Thanks for posting them J.C.!

Ace


J.C. Hornbeck said:
Two great knowledge base articles that describe how this works are:

261968 - Explanation of the Server List Management Feature in the Domain
Name Resolver Client (http://support.microsoft.com/?id=261968).

286834 - The DNS Client Service Does Not Revert to Using the First Server in
the List (http://support.microsoft.com/?id=286834).

--
J.C. Hornbeck, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
Click to expand...
 
Back
Top