From: Michał Kępień Date: Fri, 8 Jan 2021 15:16:51 +0000 (+0100) Subject: Reorder release notes X-Git-Tag: v9.17.10~28^2~6^2~2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=09ff03bb1cf55f35c2c3c60f7d19ee57aabfd511;p=thirdparty%2Fbind9.git Reorder release notes --- diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index d38095453f2..cc00a8586bb 100644 --- a/doc/notes/notes-current.rst +++ b/doc/notes/notes-current.rst @@ -24,7 +24,7 @@ Known Issues New Features ~~~~~~~~~~~~ -- None. +- ``ipv4only.arpa`` is now served when DNS64 is configured. [GL #385] Removed Features ~~~~~~~~~~~~~~~~ @@ -44,8 +44,6 @@ Removed Features Feature Changes ~~~~~~~~~~~~~~~ -- ``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 none;`` also causes CDS and CDNSKEY DELETE records to be published, to @@ -66,15 +64,15 @@ Feature Changes Bug Fixes ~~~~~~~~~ +- 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] + - ``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 not turn off DNSSEC maintenance. This has been fixed. [GL #2341] -- 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]