On Friday 25 August 2006 13:55, Theo Van Dinter wrote: > On Fri, Aug 25, 2006 at 01:44:54PM -0800, John Andersen wrote: > > It seems likely that he would have notices such a glaring deficiency, No? > > Possibly. My recollection is that Net::DNS only looks at the first server > entry in resolv.conf. So if that server happens to not be running named, > the system may work fine (assuming multiple entries in resolv.conf), but > Net::DNS would barf.
Could be. Simply reversing the order of lines in resolv.conf might determine this. If the first server was down, dns would have to time out (usually 10 to 30 seconds) before the query would fall-over to the second server. If the first server was set to reject connections instantly, fallover is almost instant, but your only if you have (and use) a secondary. Instant rejection is what competent ISPs use when doing maintenance. <rant> Even a minimalist configuration of nscd on the mail server allows for working around this sort of problem and using DNS servers of your choice. Often the secondary server provided by you ISP is less busy than the primary. It is not necessary to blindly take what ever is offered to you via DHCP. </rant> -- _____________________________________ John Andersen
pgpV78E48RK76.pgp
Description: PGP signature
