Hi Daniel, thanks for your explanation about influencing factors when it comes to propagation delays.
No big deal that knot.conf keywords cannot be used as variables as well. I will set propagation-delay to my liking. Regards, Michael > On 13. Feb 2024, at 15:01, Daniel Salzman <daniel.salz...@nic.cz> wrote: > > Hi Michael, > > There is no universal rule for propagation delay calculation, as the value is > deployment-dependent. > For example, the value depends on the latency (affects big zone XFR) between > primary and secondary servers, > or if someone has a long chain of servers where each level adds some delay. > Additionally, the value should > account for possible recovery delay in case of failures. > > Daniel > > On 2/13/24 14:27, Michael Grimm wrote: >> Hi, >> I wonder if it would be possible that one may use arithmetics in knot.conf >> such as: >> propagation-delay: 5 * dnskey-ttl >> I'd like to set apropagation-delay safety net during ZSK rotations depending >> on SOA TTL set for any given zone. >> As dnskey-ttl defaults to zone SOA TTL that would allow for >> propagation-delay definitions as multiples of SOA TTLs. >> As I couldn't find that in the documentation, I do assume that this cannot >> be done, right? >> Are there alternatives at hand I overlooked? >> Regards, >> Michael >> -- > -- --
