2
0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-24 11:08:45 +00:00

Reorder release notes

This commit is contained in:
Michał Kępień 2021-01-08 16:16:51 +01:00
parent e343aa5b94
commit 09ff03bb1c

View File

@ -24,7 +24,7 @@ Known Issues
New Features New Features
~~~~~~~~~~~~ ~~~~~~~~~~~~
- None. - ``ipv4only.arpa`` is now served when DNS64 is configured. [GL #385]
Removed Features Removed Features
~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~
@ -44,8 +44,6 @@ Removed Features
Feature Changes 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 - 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 none;`` also causes CDS and CDNSKEY DELETE records to be published, to
@ -66,15 +64,15 @@ Feature Changes
Bug Fixes 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 - ``named`` no longer attempts to assign threads to CPUs outside the CPU
affinity set. Thanks to Ole Bjørn Hessen. [GL #2245] affinity set. Thanks to Ole Bjørn Hessen. [GL #2245]
- When reconfiguring ``named``, removing ``auto-dnssec`` did not turn - When reconfiguring ``named``, removing ``auto-dnssec`` did not turn
off DNSSEC maintenance. This has been fixed. [GL #2341] 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 - KASP incorrectly set signature validity to the value of the DNSKEY signature
validity. This is now fixed. [GL #2383] validity. This is now fixed. [GL #2383]