From 5c0e3a1d8d5090eb80dcb0193a062548a79fbd41 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20K=C4=99pie=C5=84?= Date: Mon, 11 Apr 2022 15:56:43 +0200 Subject: [PATCH] Tweak and reword release notes --- doc/notes/notes-current.rst | 36 +++++++++++++++++------------------- 1 file changed, 17 insertions(+), 19 deletions(-) diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index 12c624491c..c99b6c4bcd 100644 --- a/doc/notes/notes-current.rst +++ b/doc/notes/notes-current.rst @@ -37,30 +37,28 @@ Feature Changes - None. -- Add a new configuration option ``reuseport`` to disable - load balancing on sockets in scenarios in which processing of - Response Policy Zones (RPZ), Catalog Zones, or large zone transfers - can cause service disruptions. See the BIND 9 ARM for more detail. - :gl:`#3249` +- Add a new configuration option ``reuseport`` to disable load balancing + on sockets in situations where processing of Response Policy Zones + (RPZ), Catalog Zones, or large zone transfers can cause service + disruptions. See the BIND 9 ARM for more detail. :gl:`#3249` Bug Fixes ~~~~~~~~~ -- Invalid dnssec-policy definitions were being accepted where the - defined keys did not cover both KSK and ZSK roles for a given - algorithm. This is now checked for and the dnssec-policy is - rejected if both roles are not present for all algorithms in use. - :gl:`#3142` +- Invalid ``dnssec-policy`` definitions, where the defined keys did not + cover both KSK and ZSK roles for a given algorithm, were being + accepted. These are now checked, and the ``dnssec-policy`` is rejected + if both roles are not present for all algorithms in use. :gl:`#3142` -- Handling of the TCP write timeouts has been improved to track timeout - for each TCP write separately leading to faster connection tear down +- Handling of TCP write timeouts has been improved to track the timeout + for each TCP write separately, leading to a faster connection teardown in case the other party is not reading the data. :gl:`#3200` -- Zone maintenance DNS queries would retry forever while the - destination server was unreachable. These queries include outgoing +- Previously, zone maintenance DNS queries retried forever if the + destination server was unreachable. These queries included outgoing NOTIFY messages, refresh SOA queries, parental DS checks, and stub - zone NS queries. For example, if a zone has any nameservers with - IPv6 addresses and a secondary server without IPv6 connectivity, the - IPv4-only server would keep trying to send a growing amount of - NOTIFY traffic over IPv6. This futile traffic was not logged. - :gl:`#3242` + zone NS queries. For example, if a zone had any nameservers with IPv6 + addresses and a secondary server without IPv6 connectivity, that + server would keep trying to send a growing amount of NOTIFY traffic + over IPv6. This futile traffic was not logged. This excessive retry + behavior has been fixed. :gl:`#3242`