From: Michał Kępień Date: Wed, 11 Mar 2020 08:45:31 +0000 (+0100) Subject: Reorder release note sections X-Git-Tag: v9.17.1~57^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6537aaffdcdd974354df0e984cc60074104a77d2;p=thirdparty%2Fbind9.git Reorder release note sections --- diff --git a/doc/arm/notes-9.17.0.xml b/doc/arm/notes-9.17.0.xml index 16111e780a0..7f0227a95b5 100644 --- a/doc/arm/notes-9.17.0.xml +++ b/doc/arm/notes-9.17.0.xml @@ -30,6 +30,28 @@ +
New Features + + + + 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. The default is + 100%. [GL #1515] + + + +
+
Feature Changes @@ -70,26 +92,4 @@
-
New Features - - - - 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. The default is - 100%. [GL #1515] - - - -
-