Date: Mon, 27 Feb 2006 10:55:48 -0500 From: Chuck Swiger <cswiger@mac.com> To: Yar Tikhiy <yar@comp.chem.msu.su> Cc: freebsd-stable@freebsd.org Subject: Re: SSH login takes very long time...sometimes Message-ID: <44032104.40100@mac.com> In-Reply-To: <20060227151954.GV6435@comp.chem.msu.su> References: <20060218012029.e146e2ff.rosti.bsd@gmail.com> <20060219104912.GB20500@comp.chem.msu.su> <20060219225701.0e3e244b.rosti.bsd@gmail.com> <20060221165959.GB77513@comp.chem.msu.su> <20060222024430.ad4b5c60.rosti.bsd@gmail.com> <yge1wxvz5ha.wl%ume@mahoroba.org> <20060223235727.33cddb13.rosti.bsd@gmail.com> <ygefym98o7i.wl%ume@mahoroba.org> <20060224155153.f7da1a52.rosti.bsd@gmail.com> <ygewtfkelbu.wl%ume@mahoroba.org> <20060227151954.GV6435@comp.chem.msu.su>
next in thread | previous in thread | raw e-mail | index | archive | help
Yar Tikhiy wrote: [ ... ] > A similar effect was observed when a `domain' line was specified > in resolv.conf in place of `search'. > > Is there a real reason to retry with a different domain when the > nameserver doesn't respond at all? UDP is lossy, and it may take a nameserver longer to respond that the client resolver library is willing to wait; the fact that a nameserver didn't answer once isn't a sure sign that it won't answer other questions, or even that it won't answer the same question if you just wait a minute. On the other hand, if you make 100 queries and not hear anything back, perhaps it would be useful to log that information and possibly take action. -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44032104.40100>