When the freshness of a domain cannot be checked, e.g. because the
master is offline, PowerDNS will retry the domain after
-:ref:`setting-slave-cycle-interval` seconds.
+:ref:`setting-xfr-cycle-interval` seconds.
Every time the domain fails it's freshness check, PowerDNS will hold
back on checking the domain for
-``amount of failures * slave-cycle-interval`` seconds, with a maximum of
+``amount of failures * xfr-cycle-interval`` seconds, with a maximum of
:ref:`setting-soa-retry-default` seconds
between checks. With default settings, this means that PowerDNS will
back off for 1, then 2, then 3 etc. minutes, to a maximum of 60 minutes
``slave-cycle-interval``
------------------------
-- Integer
-- Default: 60
-
-On a master, this is the amount of seconds between the master checking
-the SOA serials in its database to determine to send out NOTIFYs to the
-slaves. On slaves, this is the number of seconds between the slave
-checking for updates to zones.
+.. deprecated:: 4.5.0
+ Renamed to :ref:`setting-xfr-cycle-interval`.
.. _setting-slave-renotify:
If a PID file should be written.
+.. _setting-xfr-cycle-interval:
+
+``xfr-cycle-interval``
+----------------------
+
+.. versionchanged:: 4.5.0
+ This was called :ref:`setting-slave-cycle-interval` before 4.5.0.
+
+- Integer
+- Default: 60
+
+On a master, this is the amount of seconds between the master checking
+the SOA serials in its database to determine to send out NOTIFYs to the
+slaves. On slaves, this is the number of seconds between the slave
+checking for updates to zones.
+
.. _setting-xfr-max-received-mbytes:
``xfr-max-received-mbytes``