Solaris 10 BIND 9.5.1b1-intermittent no response for root servers and nameservers

JINMEI Tatuya / 神明達哉 Jinmei_Tatuya at isc.org
Tue Jul 29 02:56:31 UTC 2008


At Sun, 27 Jul 2008 18:24:03 -0700 (PDT),
Prabhat Rana <prana9533 at yahoo.com> wrote:

> Everything looks good except for issue that quite frequently it is
> slow to get resolution from the internet. After looking further by
> running snoop on the interface we noticed that either the
> rootservers in some case and the querying nameservers don't respond
> to the query from our DNS so we can see that it keeps on sending
> retries switching the root or nameservers and eventually gets the
> requested IP. This results the resolution being really slow. So in
> the example below , running dig @localhost www.footprints.com, it
> took almost 3 secs to get response due to all the retries due to no
> response as seen in the snoop. 

> ourdns.net -> 192.26.92.30 DNS C www.footprints.com. Internet Addr ?
> ourdns.net -> 192.48.79.30 DNS C www.footprints.com. Internet Addr ?
> ourdns.net -> 192.35.51.30 DNS C www.footprints.com. Internet Addr ?
> ourdns.net -> 67.220.109.10 DNS C www.footprints.com. Internet Addr ?
> ourdns.net -> 67.220.108.10 DNS C www.footprints.com. Internet Addr ?
> ourdns.net -> 67.220.109.10 DNS C www.footprints.com. Internet Addr ?
> ourdns.net -> 67.220.108.10 DNS C www.footprints.com. Internet Addr ?
> 67.220.108.10 -> ourdns.net DNS R www.footprints.com. Internet Addr 67.220.109.42

There may be several scenarios that can explain this, but unless the
snoop missed something the only specific reason I can think of is that
some intermediate node drops the queries.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.


More information about the bind-users mailing list