From 3338c3b1417b30b46947992deec88aa76a2273c0 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Jonas=20Sch=C3=A4fer?= Date: Tue, 18 Mar 2025 17:20:03 +0100 Subject: [PATCH] docs: clarify secondary behaviour when xfr-cycle-interval elapses Result of a discussion with @Habbie in IRC (and me misreading the docs, as usual). --- docs/settings.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) 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: -- 2.47.2