mirror of
https://gitlab.isc.org/isc-projects/bind9
synced 2025-08-30 22:15:20 +00:00
Tweak and reword release notes
This commit is contained in:
@@ -24,10 +24,10 @@ Known Issues
|
|||||||
New Features
|
New Features
|
||||||
~~~~~~~~~~~~
|
~~~~~~~~~~~~
|
||||||
|
|
||||||
- New ``rndc`` command ``rndc dnssec -checkds`` to tell ``named``
|
- Add a new ``rndc`` command, ``rndc dnssec -checkds``, which signals to
|
||||||
that a DS record for a given zone or key has been published or withdrawn
|
``named`` that a DS record for a given zone or key has been published
|
||||||
from the parent. Replaces the time-based ``parent-registration-delay``
|
or withdrawn from the parent. This command replaces the time-based
|
||||||
configuration option. [GL #1613]
|
``parent-registration-delay`` configuration option. [GL #1613]
|
||||||
|
|
||||||
- Log when ``named`` adds a CDS/CDNSKEY to the zone. [GL #1748]
|
- Log when ``named`` adds a CDS/CDNSKEY to the zone. [GL #1748]
|
||||||
|
|
||||||
@@ -46,30 +46,32 @@ Removed Features
|
|||||||
Feature Changes
|
Feature Changes
|
||||||
~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
- Previously, using ``dig +bufsize=0`` had the side effect of disabling EDNS,
|
- Previously, using ``dig +bufsize=0`` had the side effect of disabling
|
||||||
and there was no way to test the remote server's behavior when it had received
|
EDNS, and there was no way to test the remote server's behavior when
|
||||||
a packet with EDNS0 buffer size set to ``0``. This is no longer the case;
|
it had received a packet with EDNS0 buffer size set to 0. This is no
|
||||||
``dig +bufsize=0`` now sends a DNS message with EDNS version 0 and buffer size
|
longer the case; ``dig +bufsize=0`` now sends a DNS message with EDNS
|
||||||
set to ``0``. To disable EDNS, use ``dig +noedns``. [GL #2054]
|
version 0 and buffer size set to 0. To disable EDNS, use ``dig
|
||||||
|
+noedns``. [GL #2054]
|
||||||
|
|
||||||
Bug Fixes
|
Bug Fixes
|
||||||
~~~~~~~~~
|
~~~~~~~~~
|
||||||
|
|
||||||
- In rare circumstances, named would exit with assertion failure when the number
|
- In rare circumstances, ``named`` would exit with an assertion failure
|
||||||
of nodes stored in the red-black-tree exceeds the maximum allowed size of the
|
when the number of nodes stored in the red-black tree exceeded the
|
||||||
internal hashtable. [GL #2104]
|
maximum allowed size of the internal hash table. [GL #2104]
|
||||||
|
|
||||||
- Silence spurious system log messages for EPROTO(71) error code that has been
|
- Silence spurious system log messages for an EPROTO(71) error code that
|
||||||
seen on older operating systems where unhandled ICMPv6 errors result in a
|
was seen on older operating systems, where unhandled ICMPv6 errors
|
||||||
generic protocol error being returned instead of the more specific error code.
|
resulted in a generic protocol error being returned instead of a more
|
||||||
[GL #1928]
|
specific error code. [GL #1928]
|
||||||
|
|
||||||
- With query minimization enabled, named failed to resolve ip6.arpa. names
|
- With query name minimization enabled, ``named`` failed to resolve
|
||||||
that had more labels before the IPv6 part. For example, when named
|
``ip6.arpa.`` names that had extra labels to the left of the IPv6
|
||||||
implemented query minimization on a name like
|
part. For example, when ``named`` attempted query name minimization on
|
||||||
``A.B.1.2.3.4.(...).ip6.arpa.``, it stopped at the left-most IPv6 label, i.e.
|
a name like ``A.B.1.2.3.4.(...).ip6.arpa.``, it stopped at the
|
||||||
``1.2.3.4.(...).ip6.arpa.`` without considering the extra labels ``A.B``.
|
leftmost IPv6 label, i.e. ``1.2.3.4.(...).ip6.arpa.``, without
|
||||||
That caused a query loop when resolving the name: if named received
|
considering the extra labels (``A.B``). That caused a query loop when
|
||||||
NXDOMAIN answers, then the same query was repeatedly sent until the number
|
resolving the name: if ``named`` received NXDOMAIN answers, then the
|
||||||
of queries sent reached the value in the ``max-recursion-queries``
|
same query was repeatedly sent until the number of queries sent
|
||||||
configuration option. [GL #1847]
|
reached the value of the ``max-recursion-queries`` configuration
|
||||||
|
option. [GL #1847]
|
||||||
|
Reference in New Issue
Block a user