[clue-tech] DNS

[David L. Willson]

Wow Will, you are tenacious. 

God bless men that are willing to use the Source. 

"Tenacious W" doesn't have the same ring as "Tenacious D". 

David L. Willson 
Trainer, Engineer, Enthusiast 
MCT MCSE Network+ A+ Linux+ LPIC-1 NovellCLA UbuntuCP 
tel://720.333.LANS 
Freedom is better when you earn it. Learn Linux. Get Free. 

----- "Will" <will.sterling at gmail.com> wrote: 
> A Linux box will wait 5 seconds and then move on to the next server. 

> 
http://linux.die.net/man/5/resolver 
" timeout: n sets the amount of time the resolver will wait for a response from a remote name server before retrying the query via a different name server. Measured in seconds, the default is RES_TIMEOUT (see < resolv.h > )." 
http://linux.die.net/include/resolv.h 
" # define RES_TIMEOUT 5 /* min. seconds between retries */" 
> 
> 
> On Thu, Nov 18, 2010 at 2:49 PM, Will < will.sterling at gmail.com > wrote: 
> 

Microsoft Technet says that a Windows DNS server will wait three seconds for a DNS server to respond during a recursive lookup before moving on to the next server for the domain. I suspect BIND is similar but I do not see mention of it in the documentation. 

> 
On the client side a Windows machine will give it's preferred DNS server two seconds to respond before moving on to the next DNS server in its list. Again I could not find anything on the BIND light weight resolver. 


> 
> 
> 
> On Thu, Nov 18, 2010 at 1:26 PM, Roy < rjohnston at denverinternet.com > wrote: 
> 

dns will round robin through the servers- so on a no response it may retry but if it does get a response but bad data - it will cache that and stop. 
> which is why all authoritative NS need to be up to date and synced. 
> 



> 
> 
> Chris Ernst < penguin-guy at comcast.net > wrote: 
> 
> >It's up to the client. Typically, if the initial request fails and 
> >there is another NS record, it will just try the next one. 
> > 
> > - Chris 
> > 
> >On 11/18/2010 12:56 PM, David L. Willson wrote: 
> >> If a domain has a couple NS records setup at the registrar, what happens 
> >> if one of name-servers is down? Do lookups fail back to the client or 
> >> fail gracefully to the other NS with no notice to the client? 
> >> 
> >> What if there are more than two name-servers? Are they all tried before 
> >> a failure is reported, or just a certain number? 
> >> 
> >> What if the name-server is up, but there's another sort of failure, like 
> >> "no such domain" or something like that? 
> >> 
> >> I am willing and able to look this up myself, or trace it out myself, 
> >> but I'm short of time, so I thought I'd check if someone knew off the 
> >> top of their head, and wanted to show off a bit. 
> >> 
> >> David L. Willson 
> >> Trainer, Engineer, Enthusiast 
> >> MCT MCSE Network+ A+ Linux+ LPIC-1 NovellCLA UbuntuCP 
> >> tel://720.333.LANS 
> >> Freeing the world from the tyranny (or whatevery) of Microsofty-ness 
> >> 
> >> 
> >> 
> >> _______________________________________________ 
> >> clue-tech mailing list 
> >> clue-tech at cluedenver.org 
> >> http://cluedenver.org/mailman/listinfo/clue-tech 
> > 
> >_______________________________________________ 
> >clue-tech mailing list 
> > clue-tech at cluedenver.org 
> > http://cluedenver.org/mailman/listinfo/clue-tech 
> _______________________________________________ 
> clue-tech mailing list 
> clue-tech at cluedenver.org 
> http://cluedenver.org/mailman/listinfo/clue-tech 
> 
> 
> 
> _______________________________________________ clue-tech mailing list clue-tech at cluedenver.org http://cluedenver.org/mailman/listinfo/clue-tech 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cluedenver.org/pipermail/clue-tech/attachments/20101118/aceb19ba/attachment.html