NS record TTL versus nameserver's A record TTL

We received a report that a domain we serve was not resolving at a remote site. The site also reported their own analysis that the issue appeared to be that the domain's NS record had a longer TTL than its target nameserver's A record and their caching server didn't seem able to handle this.

Re: NS record TTL versus nameserver's A record TTL

Hi John, El 2013-10-08 11:49:24, John Wobus escribió: They took responsibility for their nameserver's deficiency, but it makes me wonder: -Is this addressed by a standard? E.g., the nameserver's A record have the same TTL as NS records pointing at it. -Is this addressed by a best

Re: NS record TTL versus nameserver's A record TTL

On 08.10.13 11:49, John Wobus wrote: We received a report that a domain we serve was not resolving at a remote site. The site also reported their own analysis that the issue appeared to be that the domain's NS record had a longer TTL than its target nameserver's A record and their caching