From: Michał Kępień Date: Tue, 8 Nov 2022 12:24:19 +0000 (+0100) Subject: Set up release notes for BIND 9.16.36 X-Git-Tag: v9.16.36~34^2 X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=cc71b0afb0988a8680da18ab6a9441a71b23e0c4;p=thirdparty%2Fbind9.git Set up release notes for BIND 9.16.36 --- diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index d698c3519bc..8879cd9f30c 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.16.35 +Notes for BIND 9.16.36 ---------------------- Security Fixes @@ -35,25 +35,7 @@ Feature Changes Bug Fixes ~~~~~~~~~ -- The RecursClients statistics counter could overflow in certain resolution - scenarios. This has been fixed. :gl:`#3584` - -- BIND would fail to start on Solaris-based systems with hundreds of CPUs. This - has been fixed. ISC would like to thank Stacey Marshall from Oracle for - bringing this problem to our attention. :gl:`#3563` - -- In certain resolution scenarios quotas could be erroneously reached for - servers, including the configured forwarders, resulting in SERVFAIL answers - sent to the clients. This has been fixed. :gl:`#3598` - -- When having Internet connectivity issues during the initial startup of - ``named``, BIND resolver with ``dnssec-validation`` set to ``auto`` could - enter into a state where it would not recover without stopping ``named``, - manually deleting ``managed-keys.bind`` and ``managed-keys.bind.jnl`` files, - and starting ``named`` again. :gl:`#2895` - -- Fixed a crash that happens when you reconfigure a ``dnssec-policy`` - zone that uses NSEC3 to enable ``inline-signing``. :gl:`#3591` +- None. Known Issues ~~~~~~~~~~~~