Re: Understanding TTL in "rndc dumpdb"-output

2018-10-24 Thread Michał Kępień
> I've checked the serve-stale status, which is currently off. > # rndc serve-stale status > _default: off (stale-answer-ttl=1 max-stale-ttl=604800) > _bind: off (stale-answer-ttl=1 max-stale-ttl=604800) > > Is this a normal behavior, that in the "rndc dumpdb" nevertheless the TTL in > the form

Re: Understanding TTL in "rndc dumpdb"-output

2018-10-23 Thread Tom
Hi Michal Thank you for this feedback. I've checked the serve-stale status, which is currently off. # rndc serve-stale status _default: off (stale-answer-ttl=1 max-stale-ttl=604800) _bind: off (stale-answer-ttl=1 max-stale-ttl=604800) Is this a normal behavior, that in the "rndc dumpdb"

Re: Understanding TTL in "rndc dumpdb"-output

2018-10-23 Thread Michał Kępień
> After querying my resolver for "testbla11.example.com", I receive a NXDOMAIN > response with a minimum-ttl (in the soa) of 3600. > When I afterwards dump the cache of my resolver (9.12.2-P1) with "rndc > dumpdb" and look for the negative ttl, then a value much bigger than 3600 is > shown

Understanding TTL in "rndc dumpdb"-output

2018-10-22 Thread Tom
Hi After querying my resolver for "testbla11.example.com", I receive a NXDOMAIN response with a minimum-ttl (in the soa) of 3600. When I afterwards dump the cache of my resolver (9.12.2-P1) with "rndc dumpdb" and look for the negative ttl, then a value much bigger than 3600 is shown (608363):