On 18. Jul 2024, at 19:41, Daniel Salzman via
knot-dns-users <knot-dns-users(a)lists.nic.cz> wrote:
Michael,
FYI
I hope this solves your issue.
Daniel
On 7/15/24 23:43, Michael Grimm wrote:
Daniel Salzman via knot-dns-users
<knot-dns-users(a)lists.nic.cz> wrote:
I don't understand why it's that
important if you can add one TTL directive to the zone?
Example:
1) if one does has X zones to configure.
2) now, one needs to modify TTL for all zones to whatever reason.
3) given that one uses a $INCLUDE ___TTL___ directive in all those X zone files …
4) one would need to modifying *one* file only instead of X!
I did expect knot's parser to follow *my* intended directive to follow that (POLA).
But that is not the case, as I found out and why I started this thread.
It is not of utmost importance, though.
*But* it would make my setup much easier to administer.
A configurable default RR limit instead of hardcoded 3600 seconds would help as well.
Regards,
Michael
>
> Daniel
>
> Dne 2024-07-15 23:07, Michael Grimm napsal:
>> Daniel Salzman via knot-dns-users <knot-dns-users(a)lists.nic.cz> wrote:
>>> It's a hardcoded default of 3600 seconds.
>> Ah, now I understand.
>>> We could simply change the parser to keep the default TTL set within an
included zone file. However, it seems that Bind
>>> parses the zone in the same way as Knot. So it's a tough decision :-)
>> :-)
>> Or make that hardcoded 3600s a configurable option in knot.conf …
>> Regards,
>> Michael
> --