On Tue, Sep 21, 2021 at 03:11:30PM +0200, Tom wrote:
> The documentation says, that "any record encountered with a TTL higher
> than max-zone-ttl is capped at the maximum permissible TTL value".
>
> Is the documentation wrong here?
It does appear to be wrong, yes.
It also differs from the behav
Hi Matthijs
Thank you for your explanation.
The documentation says, that "any record encountered with a TTL higher
than max-zone-ttl is capped at the maximum permissible TTL value".
Is the documentation wrong here?
Thank you.
Kind regards,
Tom
On 21.09.21 09:47, Matthijs Mekking wrote:
H
I started this thread back in April in response to high levels of abuse of
my nameserver. A short summary of the discussion which resulted is that
bind does not provide any way of preventing abuse I was experiencing. (The
abuse was clearly designed to get past any use of rate-limiting to mitigate
Hi Tom,
The max-zone-ttl is there to calculate the right timings for key
rollovers. It won't alter the zone TTL values.
You should set the max-zone-ttl to whatever the highest TTL is in your
zone to make sure key rollovers timings are correct.
This value exists until we have added code to t
4 matches
Mail list logo
