Problem resolving a host wenn TTL of NS-Servers runs out

[Alexander Sulfrian]

Hi,

> I was able to reproduce the problem locally and have full log of it,
> I'll investigate more tomorrow. While there is a misconfiguration on
> the authoritative side (the TTL of the name servers at the delegation
> should be the same as in the child zone), this sounds like something's
> wrong in the resolver anyway.

Did you have any time to investigate it further?

We are experiencing the same problem when resolving, for example,
www.kit.edu on an IPv4-only server. Immediately after flushing the cache,
the domain resolves; however, after some time, the cached A records for
the nameserver expire and only AAAA records remain in the cache, causing
bind to fail to resolve the domain.

Yes, the TTL of the glue records for the nameservers does not match the
TTL of the records in the child zones, but that should not prevent the
domain from resolving.


Thanks,
Alexander Sulfrian