2
0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-31 14:35:26 +00:00

some release note corrections

This commit is contained in:
Evan Hunt
2021-02-16 14:28:05 -08:00
parent 62cf011eaa
commit 3126eb652d

View File

@@ -85,7 +85,7 @@ Feature Changes
multiple versions of the same shared library) at startup. [GL #2387] multiple versions of the same shared library) at startup. [GL #2387]
- The default value of ``max-stale-ttl`` has been changed from 12 hours to 1 - The default value of ``max-stale-ttl`` has been changed from 12 hours to 1
day and the default value of ``stale-answer-ttl`` has been changed from 1 day, and the default value of ``stale-answer-ttl`` has been changed from 1
second to 30 seconds, following RFC 8767 recommendations. [GL #2248] second to 30 seconds, following RFC 8767 recommendations. [GL #2248]
- When ``check-names`` is in effect, A records below an ``_spf``, ``_spf_rate`` - When ``check-names`` is in effect, A records below an ``_spf``, ``_spf_rate``
@@ -102,14 +102,14 @@ Bug Fixes
- Previously, ``dnssec-keyfromlabel`` crashed when operating on an ECDSA key. - Previously, ``dnssec-keyfromlabel`` crashed when operating on an ECDSA key.
This has been fixed. [GL #2178] This has been fixed. [GL #2178]
- Named ``allow-update`` acls where broken in BIND 9.17.9 and BIND 9.16.11 - The use of named ACLs in ``allow-update`` was broken in BIND 9.17.9 and
preventing ``named`` starting. [GL #2413] BIND 9.16.11, preventing ``named`` from starting. [GL #2413]
- When migrating to ``dnssec-policy``, BIND considered keys with the "Inactive" - When migrating to ``dnssec-policy``, BIND considered keys with the "Inactive"
and/or "Delete" timing metadata as possible active keys. This has been fixed. and/or "Delete" timing metadata as possible active keys. This has been fixed.
[GL #2406] [GL #2406]
- Fix the "three is a crowd" key rollover bug in ``dnssec-policy``. When keys - Fixed the "three is a crowd" key rollover bug in ``dnssec-policy``. When keys
rolled faster than the time required to finish the rollover procedure, the rolled faster than the time required to finish the rollover procedure, the
successor relation equation failed because it assumed only two keys were successor relation equation failed because it assumed only two keys were
taking part in a rollover. This could lead to premature removal of taking part in a rollover. This could lead to premature removal of
@@ -117,7 +117,7 @@ Bug Fixes
described in the paper "Flexible and Robust Key Rollover" (Equation (2)). described in the paper "Flexible and Robust Key Rollover" (Equation (2)).
[GL #2375] [GL #2375]
- If an invalid key name (e.g. "a..b") was specified in a primaries - If an invalid key name (e.g. "a..b") was specified in a ``primaries``
list in named.conf, the wrong size was passed to ``isc_mem_put()``, list in ``named.conf``, the wrong size was passed to ``isc_mem_put()``,
which resulted in the returned memory being put on the wrong freed which resulted in the returned memory being put on the wrong freed
list. This has been fixed. [GL #2460] list. This has been fixed. [GL #2460]