mirror of
https://github.com/isc-projects/bind9.git
synced 2026-06-11 08:59:59 -04:00
Tweak and reword release notes
This commit is contained in:
parent
d0e094e81e
commit
5c0e3a1d8d
1 changed files with 17 additions and 19 deletions
|
|
@ -37,30 +37,28 @@ Feature Changes
|
|||
|
||||
- None.
|
||||
|
||||
- Add a new configuration option ``reuseport`` to disable
|
||||
load balancing on sockets in scenarios in which processing of
|
||||
Response Policy Zones (RPZ), Catalog Zones, or large zone transfers
|
||||
can cause service disruptions. See the BIND 9 ARM for more detail.
|
||||
:gl:`#3249`
|
||||
- Add a new configuration option ``reuseport`` to disable load balancing
|
||||
on sockets in situations where processing of Response Policy Zones
|
||||
(RPZ), Catalog Zones, or large zone transfers can cause service
|
||||
disruptions. See the BIND 9 ARM for more detail. :gl:`#3249`
|
||||
|
||||
Bug Fixes
|
||||
~~~~~~~~~
|
||||
|
||||
- Invalid dnssec-policy definitions were being accepted where the
|
||||
defined keys did not cover both KSK and ZSK roles for a given
|
||||
algorithm. This is now checked for and the dnssec-policy is
|
||||
rejected if both roles are not present for all algorithms in use.
|
||||
:gl:`#3142`
|
||||
- Invalid ``dnssec-policy`` definitions, where the defined keys did not
|
||||
cover both KSK and ZSK roles for a given algorithm, were being
|
||||
accepted. These are now checked, and the ``dnssec-policy`` is rejected
|
||||
if both roles are not present for all algorithms in use. :gl:`#3142`
|
||||
|
||||
- Handling of the TCP write timeouts has been improved to track timeout
|
||||
for each TCP write separately leading to faster connection tear down
|
||||
- Handling of TCP write timeouts has been improved to track the timeout
|
||||
for each TCP write separately, leading to a faster connection teardown
|
||||
in case the other party is not reading the data. :gl:`#3200`
|
||||
|
||||
- Zone maintenance DNS queries would retry forever while the
|
||||
destination server was unreachable. These queries include outgoing
|
||||
- Previously, zone maintenance DNS queries retried forever if the
|
||||
destination server was unreachable. These queries included outgoing
|
||||
NOTIFY messages, refresh SOA queries, parental DS checks, and stub
|
||||
zone NS queries. For example, if a zone has any nameservers with
|
||||
IPv6 addresses and a secondary server without IPv6 connectivity, the
|
||||
IPv4-only server would keep trying to send a growing amount of
|
||||
NOTIFY traffic over IPv6. This futile traffic was not logged.
|
||||
:gl:`#3242`
|
||||
zone NS queries. For example, if a zone had any nameservers with IPv6
|
||||
addresses and a secondary server without IPv6 connectivity, that
|
||||
server would keep trying to send a growing amount of NOTIFY traffic
|
||||
over IPv6. This futile traffic was not logged. This excessive retry
|
||||
behavior has been fixed. :gl:`#3242`
|
||||
|
|
|
|||
Loading…
Reference in a new issue