New Features
~~~~~~~~~~~~
-- The ``tls`` block was extended with a new ``cipher-suites`` option
- that allows setting allowed cipher suites for TLSv1.3. Please
- consult the documentation for additional details.
- :gl:`#3504`
-
-- The statistics channel now includes counters that indicate the number
- of currently connected TCP IPv4/IPv6 clients. :gl:`#4425`
-
- The statistics channel's incoming zone transfers information now also shows
the zones' "first refresh" flag, which indicates that a zone is not fully
ready yet, and its first ever refresh is pending or is in-progress. The number
of such zones is now also exposed by the ``rndc status`` command. :gl:`#4241`
+- The statistics channel now includes counters that indicate the number
+ of currently connected TCP IPv4/IPv6 clients. :gl:`#4425`
+
- Add HSM support to :any:`dnssec-policy`. You can now configure keys with a
``key-store`` that allows you to set the directory to store the key files and
set a PKCS#11 URI string. The latter requires OpenSSL 3 and a valid PKCS#11
provider to be configured for OpenSSL. :gl`#1129`.
+- The ``tls`` block was extended with a new ``cipher-suites`` option
+ that allows setting allowed cipher suites for TLSv1.3. Please
+ consult the documentation for additional details.
+ :gl:`#3504`
+
- Add support for RESINFO record type. :gl:`#4413`
Removed Features
Bug Fixes
~~~~~~~~~
+- A regression in cache-cleaning code enabled memory use to grow
+ significantly more quickly than before, until the configured
+ :any:`max-cache-size` limit was reached. This has been fixed.
+ :gl:`#4596`
+
+- Using :option:`rndc flush` inadvertently caused cache cleaning to
+ become less effective. This could ultimately lead to the configured
+ :any:`max-cache-size` limit being exceeded and has now been fixed.
+ :gl:`#4621`
+
- Changes to ``listen-on`` statements were ignored on reconfiguration
unless the port or interface address was changed, making it
impossible to change a related listener transport type. That issue
ISC would like to thank to Jinmei Tatuya from Infoblox for bringing
this issue to our attention.
-- A regression in cache-cleaning code enabled memory use to grow
- significantly more quickly than before, until the configured
- :any:`max-cache-size` limit was reached. This has been fixed.
- :gl:`#4596`
-
-- Using :option:`rndc flush` inadvertently caused cache cleaning to
- become less effective. This could ultimately lead to the configured
- :any:`max-cache-size` limit being exceeded and has now been fixed.
- :gl:`#4621`
-
Known Issues
~~~~~~~~~~~~