document CSYNC+upgrade notes+fix in 4.4 notes

diff --git a/.github/actions/spell-check/expect.txt b/.github/actions/spell-check/expect.txt
index dca38257e2afbf9e67ce35f1c8affb5000e32ac1..ec0c775deb9268c745975fd9995d563b4c6f4908 100644 (file)
--- a/.github/actions/spell-check/expect.txt
+++ b/.github/actions/spell-check/expect.txt
@@ -366,6 +366,7 @@ cryptopp
 cryptoshop
 css
 csv
+CSYNC
 ctime
 ctor
 ctx

diff --git a/docs/appendices/types.rst b/docs/appendices/types.rst
index e1ad339b3bf09c409cc9927a15074c5fd467acc5..64c6a621510766f274bd4ad96c758387c247871e 100644 (file)
--- a/docs/appendices/types.rst
+++ b/docs/appendices/types.rst
@@ -100,6 +100,15 @@ The CNAME record specifies the canonical name of a record. It is stored
 plainly. Like all other records, it is not terminated by a dot. A sample
 might be 'webserver-01.yourcompany.com'.
 
+.. _types-csync:
+
+CSYNC
+-----
+
+The CSYNC record is used for 'Child-to-Parent Synchronization in DNS', as described in :rfc:`7477`.
+Right now it is only supported as zone content; no special processing is implemented.
+Note that SOA-EDIT is not applied to serial numbers in CSYNC content.
+
 .. _types-dnskey:
 
 DNSKEY

diff --git a/docs/upgrading.rst b/docs/upgrading.rst
index 915befc3bf1a3cef70b912fdad941cd8b5b9ddf1..19c73e26ff9395f5bc30500c191b7e0f05007728 100644 (file)
--- a/docs/upgrading.rst
+++ b/docs/upgrading.rst
@@ -8,6 +8,21 @@ Please upgrade to the PowerDNS Authoritative Server 4.0.0 from 3.4.2+.
 See the `3.X <https://doc.powerdns.com/3/authoritative/upgrading/>`__
 upgrade notes if your version is older than 3.4.2.
 
+4.4.x to 4.5.0 or master
+------------------------
+
+Record type changes
+^^^^^^^^^^^^^^^^^^^
+
+The in-database format of ``CSYNC`` and ``IPSECKEY`` records has changed from 'generic' format to its specialized format.
+
+API users might notice that replacing records of these types leaves the old TYPExx records around, even if PowerDNS is not serving them.
+To fix this, enable :ref:`setting-upgrade-unknown-types` and replace the records; this will then delete those TYPExx records.
+Then, disable the setting again, because it has a serious performance impact on API operations.
+
+On secondaries, it is recommended to re-transfer, using ``pdns_control retrieve ZONE``, with :ref:`setting-upgrade-unknown-types` enabled, all zones that have records of those types, or ``TYPExx``, for numbers 45 and 62.
+Leave the setting on until all zones have been re-transferred.
+
 4.3.x to 4.4.0
 --------------
 
@@ -46,7 +61,7 @@ API users might notice that replacing records of these types leaves the old TYPE
 To fix this, enable :ref:`setting-upgrade-unknown-types` and replace the records; this will then delete those TYPExx records.
 Then, disable the setting again, because it has a serious performance impact on API operations.
 
-On secondaries, it is recommended to re-transfer, using ``pdns_control retrieve ZONE``, with :ref:`setting-upgrade-unknown-types` enabled, all zones that have records of those types, or ``TYPExx``, for numbers 42, 45, 64, 65.
+On secondaries, it is recommended to re-transfer, using ``pdns_control retrieve ZONE``, with :ref:`setting-upgrade-unknown-types` enabled, all zones that have records of those types, or ``TYPExx``, for numbers 42, 64, 65.
 Leave the setting on until all zones have been re-transferred.
 
 PostgreSQL configuration escaping