Skip to content

add retry/expire min/max options similar to refresh-min-interval

We use knot 3.1.5-cznic.1~stretch als Secondary for customer zones. These zone sometimes have freaky SOAs:

example.at. 600 IN SOA dns1.example.at. hostmaster.example.at. 2022021501 1 1 1 1

This causes constant logging and AXFR in Knot:

21:37:03 [example.at.] zone expired
21:37:03 [example.at.] AXFR, incoming, remote 127.0.0.1@14001, started
21:37:03 [example.at.] AXFR, incoming, remote 127.0.0.1@14001, finished, 0.00 seconds, 4 messages, 5055 bytes
21:37:03 [example.at.] refresh, remote 127.0.0.1@14001, zone updated, 0.02 seconds, serial none -> 2022021501
21:37:03 [example.at.] zone file updated, serial 2022021501
21:37:04 [example.at.] zone expired
21:37:04 [example.at.] AXFR, incoming, remote 127.0.0.1@14001, started
21:37:04 [example.at.] AXFR, incoming, remote 127.0.0.1@14001, finished, 0.00 seconds, 4 messages, 5055 bytes
21:37:04 [example.at.] refresh, remote 127.0.0.1@14001, zone updated, 0.02 seconds, serial none -> 2022021501
21:37:04 [example.at.] zone file updated, serial 2022021501
21:37:05 [example.at.] zone expired
21:37:05 [example.at.] AXFR, incoming, remote 127.0.0.1@14001, started
21:37:05 [example.at.] AXFR, incoming, remote 127.0.0.1@14001, finished, 0.00 seconds, 4 messages, 5055 bytes
21:37:05 [example.at.] refresh, remote 127.0.0.1@14001, zone updated, 0.02 seconds, serial none -> 2022021501
21:37:05 [example.at.] zone file updated, serial 2022021501
...

To avoid AXFRs every second it would be great if you introduce zone config options:

retry-min-interval
retry-max-interval
expire-min-interval
expire-max-interval