NS TTL Discrepancy??
Barry Margolin
barmar at alum.mit.edu
Mon Mar 8 22:08:00 UTC 2004
In article <c2io0n$1mff$1 at sf1.isc.org>,
Mark Andrews <Mark_Andrews at isc.org> wrote:
> > If the glue A records time out of the cache before the NS records do,
> > the chicken-and-egg problem returns. So you should ensure that the TTLs
> > on your nameservers' A records are at least as long as the TTLs on the
> > NS records.
>
> Resolvers just have to detect this situation and ask the parent
> server for the missing glue.
Does BIND do this? I was under the impression it doesn't -- I've seen
plenty of times when a domain couldn't be resolved and it appeared to be
because of this situation. So I assume that when it's trying to resolve
the hostnames in the NS records, it simply uses the standard resolution
algorithm, and doesn't treat this loop as a special case.
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
More information about the bind-users
mailing list