mirror of
https://gitlab.isc.org/isc-projects/bind9
synced 2025-08-28 21:17:54 +00:00
Tweak and reword release notes
This commit is contained in:
parent
59a9fa4863
commit
451b29cbbf
@ -24,17 +24,18 @@ Known Issues
|
||||
New Features
|
||||
~~~~~~~~~~~~
|
||||
|
||||
- New configuration options, ``tcp-receive-buffer``, ``tcp-send-buffer``,
|
||||
``udp-receive-buffer``, and ``udp-send-buffer``, have been added. These
|
||||
options allows the operator to fine tune the receiving and sending
|
||||
buffers in the operating system. On busy servers, increasing the value
|
||||
of the receive buffers can prevent the server from dropping the packets
|
||||
during short spikes, and decreasing the value would prevent the server to
|
||||
became clogged up with queries that are too old and have already timeouted
|
||||
on the receiving side. :gl:`#2313`
|
||||
- New configuration options, ``tcp-receive-buffer``,
|
||||
``tcp-send-buffer``, ``udp-receive-buffer``, and ``udp-send-buffer``,
|
||||
have been added. These options allow the operator to fine-tune the
|
||||
receiving and sending buffers in the operating system. On busy
|
||||
servers, increasing the size of the receive buffers can prevent the
|
||||
server from dropping packets during short traffic spikes, and
|
||||
decreasing it can prevent the server from becoming clogged with
|
||||
queries that are too old and have already timed out. :gl:`#2313`
|
||||
|
||||
- Run zone dumping tasks on separate asynchronous thread pools. This change
|
||||
makes zone dumping no longer block networking I/O. :gl:`#2732`
|
||||
- Zone dumping tasks are now run on separate asynchronous thread pools.
|
||||
This change prevents zone dumping from blocking network I/O.
|
||||
:gl:`#2732`
|
||||
|
||||
Removed Features
|
||||
~~~~~~~~~~~~~~~~
|
||||
@ -46,35 +47,37 @@ Removed Features
|
||||
Feature Changes
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
- The interface handling code has been refactored to use fewer resources,
|
||||
which should lead to less memory fragmentation and better startup
|
||||
performance. :gl:`#2433`
|
||||
- The interface handling code has been refactored to use fewer
|
||||
resources, which should lead to less memory fragmentation and better
|
||||
startup performance. :gl:`#2433`
|
||||
|
||||
Bug Fixes
|
||||
~~~~~~~~~
|
||||
|
||||
- Fix a race condition in reading and writing key files for KASP zones in
|
||||
multiple views. :gl:`#1875`
|
||||
- A race condition could occur when reading and writing key files for
|
||||
zones using KASP and configured in multiple views. This has been
|
||||
fixed. :gl:`#1875`
|
||||
|
||||
- Check ``key-directory`` conflicts in ``named.conf`` for zones in multiple
|
||||
views with different ``dnssec-policy``. Using the same ``key-directory`` for
|
||||
such zones is not allowed. :gl:`#2463`
|
||||
- Zones which are configured in multiple views, with different values
|
||||
set for ``dnssec-policy`` and with identical values set for
|
||||
``key-directory``, are now detected and treated as a configuration
|
||||
error. :gl:`#2463`
|
||||
|
||||
- The calculation of the estimated IXFR transaction size by
|
||||
`dns_journal_iter_init()` was invalid. This resulted in excessive
|
||||
AXFR-style-IXFR responses. :gl:`#2685`
|
||||
- The calculation of the estimated IXFR transaction size in
|
||||
``dns_journal_iter_init()`` was invalid. This resulted in excessive
|
||||
AXFR-style IXFR responses. :gl:`#2685`
|
||||
|
||||
- If a query was answered with stale data on a server with DNS64 enabled,
|
||||
an assertion could occur if a non-stale answer arrived afterward. This
|
||||
has been fixed. :gl:`#2731`
|
||||
- If a query was answered with stale data on a server with DNS64
|
||||
enabled, an assertion could occur if a non-stale answer arrived
|
||||
afterward. This has been fixed. :gl:`#2731`
|
||||
|
||||
- Fixed an assertion failure that could occur if stale data was used
|
||||
to answer a query, and then a prefetch was triggered after the query
|
||||
was restarted (for example, to follow a CNAME). :gl:`#2733`
|
||||
- Fixed an assertion failure that could occur if stale data was used to
|
||||
answer a query, and then a prefetch was triggered after the query was
|
||||
restarted (for example, to follow a CNAME). :gl:`#2733`
|
||||
|
||||
- Fix an error that would enable don't fragment socket option instead
|
||||
of disabling it leading to errors when sending the oversized UDP
|
||||
packets. [GL #2746]
|
||||
- Fixed an error which caused the ``IP_DONTFRAG`` socket option to be
|
||||
enabled instead of disabled, leading to errors when sending oversized
|
||||
UDP packets. :gl:`#2746`
|
||||
|
||||
- Fixed a bug that caused the NSEC salt to be changed for KASP zones on
|
||||
every startup. :gl:`#2725`
|
||||
|
Loading…
x
Reference in New Issue
Block a user