From: Evan Hunt <each@isc.org>
Date: Mon, 24 Feb 2020 04:54:58 +0000 (-0800)
Subject: CHANGES and release note
X-Git-Tag: v9.17.1~71^2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0a39181092158ecfe11c160dbc84808d45a58b36;p=thirdparty%2Fbind9.git

CHANGES and release note
---

diff --git a/CHANGES b/CHANGES
index 860b84ba66f..a6a44f5125a 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,10 @@
+5362.	[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]
+
 5361.	[bug]		named might not accept new connections after
 			hitting tcp-clients quota. [GL #1643]
 
diff --git a/doc/arm/notes-9.17.0.xml b/doc/arm/notes-9.17.0.xml
index 38eda27a790..a2ea9c73b21 100644
--- a/doc/arm/notes-9.17.0.xml
+++ b/doc/arm/notes-9.17.0.xml
@@ -51,4 +51,26 @@
     </itemizedlist>
   </section>
 
+  <section xml:id="relnotes-9.17.0-new"><info><title>New Features</title></info>
+    <itemizedlist>
+      <listitem>
+	<para>
+	  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, <command>named</command> 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.
+	</para>
+	<para>
+	  This behavior is controlled by the <command>max-ixfr-ratio</command>
+	  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]
+	</para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
 </section>