2
0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-31 06:25:31 +00:00

Merge branch 'michal/set-up-version-and-release-notes-for-bind-9.19.8' into 'main'

Set up version and release notes for BIND 9.19.8

See merge request isc-projects/bind9!7053
This commit is contained in:
Michał Kępień
2022-11-08 12:30:09 +00:00
2 changed files with 4 additions and 29 deletions

View File

@@ -16,7 +16,7 @@
#
m4_define([bind_VERSION_MAJOR], 9)dnl
m4_define([bind_VERSION_MINOR], 19)dnl
m4_define([bind_VERSION_PATCH], 7)dnl
m4_define([bind_VERSION_PATCH], 8)dnl
m4_define([bind_VERSION_EXTRA], -dev)dnl
m4_define([bind_DESCRIPTION], [(Development Release)])dnl
m4_define([bind_SRCID], [m4_esyscmd_s([git rev-parse --short HEAD | cut -b1-7])])dnl

View File

@@ -9,7 +9,7 @@
.. See the COPYRIGHT file distributed with this work for additional
.. information regarding copyright ownership.
Notes for BIND 9.19.7
Notes for BIND 9.19.8
---------------------
Security Fixes
@@ -20,10 +20,7 @@ Security Fixes
New Features
~~~~~~~~~~~~
- ``check-svcb`` has been added to control the checking of additional
constraints on SVBC records. This change impacts on ``named``,
``named-checkconf``, ``named-checkzone``, ``named-compilezone``
and ``nsupdate``. :gl:`#3576`
- None.
Removed Features
~~~~~~~~~~~~~~~~
@@ -35,32 +32,10 @@ Feature Changes
- None.
- On Linux, libcap is now required dependency to help us keep needed
privileges. :gl:`#3583`
Bug Fixes
~~~~~~~~~
- 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`
- The port in remote servers such as in :any:`primaries` and
:any:`parental-agents` could be wrongly configured because of an inheritance
bug. :gl:`#3627`
- When having Internet connectivity issues during the initial startup of
``named``, BIND resolver with :any:`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
~~~~~~~~~~~~