CHANGES and release note

diff --git a/CHANGES b/CHANGES
index 3331514d3307f3d4c1b18d66197f5d6fe7899bb5..f425a84cea6893017139a220e1eb630824064b4c 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -2,6 +2,13 @@
                        BIND 9 version number, in an effort to tightly couple
                        internal libraries with a specific release. [GL #2387]
 
+5562.  [func]          Limit the size of IXFR responses so that AXFR will
+                       be used instead if it would be smaller. This is
+                       controlled by the "max-ixfr-ratio" option, which
+                       is a percentage representing the ratio of IXFR size
+                       to the size of the entire zone. This value cannot
+                       exceed 100%, which is the default. [GL #1515]
+
 5561.  [bug]           KASP incorrectly set signature validity to the value
                        of the DNSKEY signature validity. This is now fixed.
                        [GL #2383]

diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst
index 1a9a6ee168465ea28580ee3fde07d971ba57830a..010b9b948edab9dd22c20a36fc2e0f1602c5846e 100644 (file)
--- a/doc/notes/notes-current.rst
+++ b/doc/notes/notes-current.rst
@@ -24,7 +24,18 @@ Known Issues
 New Features
 ~~~~~~~~~~~~
 
-- None.
+- When a secondary server receives a large incremental zone
+  transfer (IXFR), it can have a negative impact on query
+  performance while the incremental changes are applied to
+  the zone. To address this, ``named`` can now
+  limit the size of IXFR responses it sends in response to zone
+  transfer requests. If an IXFR response would be larger than an
+  AXFR of the entire zone, it will send an AXFR resonse instead.
+
+  This behavior is controlled by the ``max-ixfr-ratio``
+  option - a percentage value representing the ratio of IXFR size
+  to the size of a full zone transfer. This value cannot exceed
+  100%, which is also the default. [GL #1515]
 
 Removed Features
 ~~~~~~~~~~~~~~~~