From: Jonas Schäfer Date: Tue, 18 Mar 2025 16:20:03 +0000 (+0100) Subject: docs: clarify secondary behaviour when xfr-cycle-interval elapses X-Git-Tag: dnsdist-2.0.0-alpha2~136^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F15322%2Fhead;p=thirdparty%2Fpdns.git docs: clarify secondary behaviour when xfr-cycle-interval elapses Result of a discussion with @Habbie in IRC (and me misreading the docs, as usual). --- diff --git a/docs/settings.rst b/docs/settings.rst index 25b5dc8d7f..50ad302072 100644 --- a/docs/settings.rst +++ b/docs/settings.rst @@ -2189,8 +2189,9 @@ If enabled, only a single RR will be put into each AXFR chunk, making some zones On a primary, this is the amount of seconds between the primary checking the SOA serials in its database to determine to send out NOTIFYs to the -secondaries. On secondaries, this is the number of seconds between the secondary -checking for updates to zones. +secondaries. On secondaries, this is the number of seconds between the +check for zones where the REFRESH period has expired. For zones where +that is the case, secondaries will request updates from the primary. .. _setting-xfr-max-received-mbytes: