Thank you, Tony. You're right.
I do see a difference in behavior when querying other authoritative,
non-AWS servers. I didn't realize it was the job of the authoritative
server to do the math and present the proper ttl. Thanks for the
pointer to the relevant section in the rfc.
Slava
On Tue, Oct
Well, if it works for other zones, it's unlikely to be an OS problem unless
that zone was built in the system using an older version that did things
slightly differently and now it can't be removed because of that difference.
Have you tried comparing a working zone that can be deleted from the
Veaceslav Revutchi wrote:
> Given this soa:
>
> fe80.info. 3600 IN SOA ns-538.awsdns-03.net.
> awsdns-hostmaster.amazon.com. 1 7200 900 1209600 60
>
> I see bind caching negative answers for 3600 instead of 60. The rfc
> and my google searches suggest that it should pick the MIN(soa ttl,
> soa mi
3 matches
Mail list logo
