From: Petr Špaček <pspacek@isc.org>
Date: Tue, 28 Jun 2022 15:23:19 +0000 (+0200)
Subject: Resurrect DNS NOTIFY chapter in the ARM
X-Git-Tag: v9.19.3~17^2~4
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2630cf8e76249d6971a169b0e445dadac432890e;p=thirdparty%2Fbind9.git

Resurrect DNS NOTIFY chapter in the ARM

It was accidentally removed in the heat of
25eb91d23c5a2056f36902c90dfe8ca69f6a9400.
---

diff --git a/doc/arm/advanced.inc.rst b/doc/arm/advanced.inc.rst
index 0be6df020d2..50347e68c27 100644
--- a/doc/arm/advanced.inc.rst
+++ b/doc/arm/advanced.inc.rst
@@ -88,6 +88,25 @@ journal file without stopping dynamic updates; this may be useful for
 viewing the current zone state. To remove the ``.jnl`` file after
 updating the zone file, use :option:`rndc sync -clean <rndc sync>`.
 
+.. _notify:
+
+NOTIFY
+------
+
+DNS NOTIFY is a mechanism that allows primary servers to notify their
+secondary servers of changes to a zone's data. In response to a NOTIFY message
+from a primary server, the secondary checks to see that its version of
+the zone is the current version and, if not, initiates a zone transfer.
+
+For more information about DNS NOTIFY, see the description of the
+:namedconf:ref:`notify` and :namedconf:ref`also-notify` statements.
+The NOTIFY protocol is specified in :rfc:`1996`.
+
+.. note::
+
+   As a secondary zone can also be a primary to other secondaries, :iscman:`named`, by
+   default, sends NOTIFY messages for every zone it loads.
+
 .. _incremental_zone_transfers:
 
 Incremental Zone Transfers (IXFR)