Tweak and reword release notes

This commit is contained in:
Michal Nowak 2025-06-05 15:34:39 +02:00
parent 917d6a61c0
commit 7fdd3cd656
No known key found for this signature in database

View file

@ -15,13 +15,13 @@ Notes for BIND 9.20.10
New Features
~~~~~~~~~~~~
- Implement a new 'notify-defer' configuration option.
- Implement a new :namedconf:ref:`notify-defer` configuration option.
This new option sets a delay (in seconds) to wait before sending a set
of NOTIFY messages for a zone. Whenever a NOTIFY message is ready to
be sent, sending will be deferred for this duration. This option is
not to be confused with the :any:`notify-delay` option. The default is
0 seconds. :gl:`#5259`
of ``NOTIFY`` messages for a zone. Whenever a ``NOTIFY`` message is
ready to be sent, sending is deferred for this duration. This option
should not be confused with the :namedconf:ref:`notify-delay` option.
The default is 0 seconds. :gl:`#5259`
Removed Features
~~~~~~~~~~~~~~~~
@ -29,21 +29,6 @@ Removed Features
- Implement the systemd notification protocol manually to remove
dependency on libsystemd.
libsystemd, despite being useful, adds a huge surface area for just
using the sd_notify API. libsystemd's surface has been exploited in
the past [1].
Implement the systemd notification protocol by hand since it is just
sending newline-delimited datagrams to a UNIX socket. The code
shouldn't need more attention in the future since the notification
protocol is covered under systemd's stability promise [2].
We don't need to support VSOCK-backed service notifications since they
are only intended for virtual machine inits.
[1]: https://www.openwall.com/lists/oss-security/2024/03/29/4 [2]:
https://systemd.io/PORTABILITY_AND_STABILITY/
Bug Fixes
~~~~~~~~~
@ -57,8 +42,8 @@ Bug Fixes
- Fix a zone refresh bug.
A secondary zone could fail to further refresh with new versions of
the zone from a primary server if named was reconfigured during the
SOA request step of an ongoing zone transfer. This has been fixed.
:gl:`#5307`
the zone from a primary server if :iscman:`named` was reconfigured
during the SOA request step of an ongoing zone transfer. This has been
fixed. :gl:`#5307`