From: Michal Nowak Date: Mon, 12 Jun 2023 14:12:40 +0000 (+0200) Subject: Set up release notes for BIND 9.19.15 X-Git-Tag: v9.19.15~36^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a04301f936a3195452db5803e1e547ee550cd503;p=thirdparty%2Fbind9.git Set up release notes for BIND 9.19.15 --- diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index a3bce92751e..ad7c115ce68 100644 --- a/doc/notes/notes-current.rst +++ b/doc/notes/notes-current.rst @@ -9,7 +9,7 @@ .. See the COPYRIGHT file distributed with this work for additional .. information regarding copyright ownership. -Notes for BIND 9.19.14 +Notes for BIND 9.19.15 ---------------------- Security Fixes @@ -20,53 +20,22 @@ Security Fixes New Features ~~~~~~~~~~~~ -- Add support for multi-signer model 2 (RFC 8901) when using - ``inline-signing``. :gl:`#2710` - -- A new option to :any:`dnssec-policy` has been added, :any:`cdnskey`, that - allows you to enable or disable the publication of CDNSKEY records. - :gl:`#4050` - -- The read timeout in ``rndc`` can now be specified on the command line - using the ``-t`` option, allowing commands that take a long time to - complete sufficient time to do so. :gl:`#4046` - -- The system test suite can now be executed with pytest (along with - pytest-xdist for parallel execution). :gl:`#3978` +- None. Removed Features ~~~~~~~~~~~~~~~~ -- Special-case code that was originally added to allow GSS-TSIG to work - around bugs in the Windows 2000 version of Active Directory has now - been removed since Windows 2000 is long past end-of-life. - The ``nsupdate -o`` option and the ``oldgsstsig`` command to ``nsupdate`` - have been deprecated, and are now treated as synonyms for ``nsupdate -g`` - and ``gsstsig`` respectively. :gl:`#4012` +- None. Feature Changes ~~~~~~~~~~~~~~~ -- Improve the responsiveness of the ``named`` serving as an authoritative DNS - server for a delegation-heavy zone(s) shortly after loading such zone(s). - :gl:`#4045` +- None. Bug Fixes ~~~~~~~~~ -- When the :any:`stale-answer-enable` option was enabled and the - :any:`stale-answer-client-timeout` option was enabled and larger than 0, - ``named`` was taking two places from the :any:`clients-per-query` limit for - each client and was failing to gradually auto-tune its value, as configured. - This has been fixed. :gl:`#4074` - -- It could happen that after the :any:`stale-answer-client-timeout` duration, - a delegation from cache was returned to the client. This has now been fixed. - :gl:`#3950` - -- BIND could allocate too big buffers when sending data via - stream-based DNS transports, leading to increased memory usage. - This has been fixed. :gl:`#4038` +- None. Known Issues ~~~~~~~~~~~~