From: Michał Kępień Date: Fri, 8 Jan 2021 15:16:51 +0000 (+0100) Subject: Tweak and reword release notes X-Git-Tag: v9.17.10~28^2~6^2~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e343aa5b9456f5d2a69063e314c3113020b46c66;p=thirdparty%2Fbind9.git Tweak and reword release notes --- diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index 95a441124dc..d38095453f2 100644 --- a/doc/notes/notes-current.rst +++ b/doc/notes/notes-current.rst @@ -44,10 +44,10 @@ Removed Features Feature Changes ~~~~~~~~~~~~~~~ -- ``ipv4only.arpa`` is now served when ``dns64`` is configured. [GL #385] +- ``ipv4only.arpa`` is now served when DNS64 is configured. [GL #385] - It is now possible to transition a zone from secure to insecure mode - without making it bogus in the process: changing to ``dnssec-policy + without making it bogus in the process; changing to ``dnssec-policy none;`` also causes CDS and CDNSKEY DELETE records to be published, to signal that the entire DS RRset at the parent must be removed, as described in RFC 8078. [GL #1750] @@ -60,21 +60,21 @@ Feature Changes serial number, ``named`` and ``dnssec-signzone`` silently fell back to the ``increment`` method to prevent the new serial number from being smaller than the old serial number (using serial number arithmetics). - ``dnsssec-signzone`` now prints a warning message, and ``named`` logs - a warning, when such a fallback happens. [GL #2058] + ``dnssec-signzone`` now prints a warning message, and ``named`` logs a + warning, when such a fallback happens. [GL #2058] Bug Fixes ~~~~~~~~~ -- Only assign threads to CPUs in the CPU affinity set, so that ``named`` no - longer attempts to run threads on CPUs outside the affinity set. Thanks to - Ole Bjørn Hessen. [GL #2245] +- ``named`` no longer attempts to assign threads to CPUs outside the CPU + affinity set. Thanks to Ole Bjørn Hessen. [GL #2245] -- When reconfiguring ``named``, removing ``auto-dnssec`` did actually not turn +- When reconfiguring ``named``, removing ``auto-dnssec`` did not turn off DNSSEC maintenance. This has been fixed. [GL #2341] -- Prevent rbtdb instances being destroyed by multiple threads at the same - time. This can trigger assertion failures. [GL #2355] +- Multiple threads could attempt to destroy a single RBTDB instance at + the same time, resulting in an unpredictable but low-probability + assertion failure in ``free_rbtdb()``. This has been fixed. [GL #2317] - KASP incorrectly set signature validity to the value of the DNSKEY signature validity. This is now fixed. [GL #2383]