From bb5b732ac581428ca6936837190fa3a8e04d5c98 Mon Sep 17 00:00:00 2001 From: Pieter Lexis Date: Fri, 8 Jan 2021 14:48:57 +0100 Subject: [PATCH] Fix comments by @Habbie --- docs/modes-of-operation.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/modes-of-operation.rst b/docs/modes-of-operation.rst index 5b0d8c70c1..867cdc2614 100644 --- a/docs/modes-of-operation.rst +++ b/docs/modes-of-operation.rst @@ -202,8 +202,8 @@ must be met: - :ref:`setting-superslave` support must be enabled -- The supermaster must carry a SOA record for the notified domain corresponding with one of the NS records for that domain -- The supermaster IP must be present in the 'supermasters' table in the database on the slave, along with the name mentioned in the SOA +- The supermaster must carry a SOA record for the notified domain +- The supermaster IP must be present in the 'supermasters' table in the database on the slave, along with any name that is in the NS set. - The set of NS records for the domain, as retrieved by the slave from the supermaster, must include the name that goes with the IP address in the supermasters table - If your master sends signed NOTIFY it will mark that TSIG key as the TSIG key used for retrieval as well - If you turn off :ref:`setting-allow-unsigned-supermaster`, then your supermaster(s) are required to sign their notifications. -- 2.47.2