From 400ab0dd0bfbbe16194d0d6712e59bd3082eeb8d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20K=C4=99pie=C5=84?= Date: Fri, 8 Jan 2021 16:16:51 +0100 Subject: [PATCH] Tweak and reword release notes --- doc/notes/notes-current.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index 06c99da9fe..2c04a545d1 100644 --- a/doc/notes/notes-current.rst +++ b/doc/notes/notes-current.rst @@ -34,10 +34,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] @@ -46,18 +46,18 @@ 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]