Re: BIND 8.4.5 as cache server, long delay to resolve some domains...

Jacques-Andre Petit <japetit@ccis.be> wrote:

> I get some delays before response from BIND 8.4.5 running as cache DNS
> in "erratic" domains.
>
> After debugging a while, it seems that the problem arises when the
> requested domain info depends of one root and the DNS record for that
> domain is depending of another root.
> A sample : domain would be my_domain.*net* with a NS record pointing
> to ns.another_domain.*com*
>
> BIND behave as if it "forgot" the primary request (www.my_domain.net) to
> resolve ns.another_domain.com.

That's exactly what it does: it drops the request and hopes to have
the information ready by the time the client asks again.

> Once resolved (ns.another_domain.com), BIND stops and never resolves
> www.my_domain.net
>
> Then, after about 5 seconds, there is a new request from the client
> (timeout) and BIND can resolve further as it then knows how to resolve
> ns.another_domain.com.
>
> A realworld example would be www.isfc.org (dig response pasted below)
>
> We suppose that this situation is not RFC compliant (where NS pointers
> must belong to the same root as the domain they manage), and that this

Which RFC?

> cannot "semantically" be considered as bug, but from the user point of
> view, it is translated as long delays and frustration.
>
> Is there a way to fix that behavior?

Install BIND9 ...

--
Ronan Flood <R.Flood@noc.ulcc.ac.uk>
working for but not speaking for
Network Services, University of London Computer Centre
(which means: don't bother ULCC if I've said something you don't like)