From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] bind: Update to 9.16.35
Date: Sat, 19 Nov 2022 11:52:54 +0000 [thread overview]
Message-ID: <3F914625-3CA3-4D43-8262-9EBE2101FFFC@ipfire.org> (raw)
In-Reply-To: <20221118191926.2244-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4112 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 18 Nov 2022, at 19:19, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> For details for 9.16.35 and 9.16.34 (we skipped the last) see:
> https://downloads.isc.org/isc/bind9/9.16.35/doc/arm/html/notes.html#notes-for-bind-9-16-35
>
> "Notes for BIND 9.16.35
> Bug Fixes
>
> A crash was fixed that happened when a dnssec-policy zone that used
> NSEC3 was reconfigured to enable inline-signing. [GL #3591]
>
> In certain resolution scenarios, quotas could be erroneously reached
> for servers, including any configured forwarders, resulting in SERVFAIL
> answers being sent to clients. This has been fixed. [GL #3598]
>
> rpz-ip rules in response-policy zones could be ineffective in some
> cases if a query had the CD (Checking Disabled) bit set to 1. This has
> been fixed. [GL #3247]
>
> Previously, if Internet connectivity issues were experienced during the
> initial startup of named, a BIND resolver with dnssec-validation set to
> auto could enter into a state where it would not recover without
> stopping named, manually deleting the managed-keys.bind and
> managed-keys.bind.jnl files, and starting named again. This has been
> fixed. [GL #2895]
>
> The statistics counter representing the current number of clients
> awaiting recursive resolution results (RecursClients) could overflow in
> certain resolution scenarios. This has been fixed. [GL #3584]
>
> Previously, BIND failed to start on Solaris-based systems with hundreds
> of CPUs. This has been fixed. [GL #3563]
>
> When a DNS resource record’s TTL value was equal to the resolver’s
> configured prefetch “eligibility” value, the record was erroneously not
> treated as eligible for prefetching. This has been fixed. [GL #3603]
>
> ...
>
> Notes for BIND 9.16.34
>
> Bug Fixes
>
> Changing just the TSIG key names for primaries in catalog zones’ member
> zones was not effective. This has been fixed. [GL #3557]"
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> config/rootfiles/common/bind | 14 +++++++-------
> lfs/bind | 4 ++--
> 2 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/config/rootfiles/common/bind b/config/rootfiles/common/bind
> index 879f8c832..6a83df8ce 100644
> --- a/config/rootfiles/common/bind
> +++ b/config/rootfiles/common/bind
> @@ -271,24 +271,24 @@ usr/bin/nsupdate
> #usr/include/pk11/site.h
> #usr/include/pkcs11
> #usr/include/pkcs11/pkcs11.h
> -usr/lib/libbind9-9.16.33.so
> +usr/lib/libbind9-9.16.35.so
> #usr/lib/libbind9.la
> #usr/lib/libbind9.so
> -usr/lib/libdns-9.16.33.so
> +usr/lib/libdns-9.16.35.so
> #usr/lib/libdns.la
> #usr/lib/libdns.so
> -usr/lib/libirs-9.16.33.so
> +usr/lib/libirs-9.16.35.so
> #usr/lib/libirs.la
> #usr/lib/libirs.so
> -usr/lib/libisc-9.16.33.so
> +usr/lib/libisc-9.16.35.so
> #usr/lib/libisc.la
> #usr/lib/libisc.so
> -usr/lib/libisccc-9.16.33.so
> +usr/lib/libisccc-9.16.35.so
> #usr/lib/libisccc.la
> #usr/lib/libisccc.so
> -usr/lib/libisccfg-9.16.33.so
> +usr/lib/libisccfg-9.16.35.so
> #usr/lib/libisccfg.la
> #usr/lib/libisccfg.so
> -usr/lib/libns-9.16.33.so
> +usr/lib/libns-9.16.35.so
> #usr/lib/libns.la
> #usr/lib/libns.so
> diff --git a/lfs/bind b/lfs/bind
> index aeff480a2..16fc9ba97 100644
> --- a/lfs/bind
> +++ b/lfs/bind
> @@ -25,7 +25,7 @@
>
> include Config
>
> -VER = 9.16.33
> +VER = 9.16.35
>
> THISAPP = bind-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -43,7 +43,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 4246b61ce91af3d494ace4b8065b4c0043b2cfaf28c6de326691a969837e7d1cfbc0dac6b1e1a5182fc32af68048abcfa1202d00022951f3caa13afb03ebeb69
> +$(DL_FILE)_BLAKE2 = c3d23e939c882e9bebe2aa83d91ab40bfe8c4b9882890acdb0908d4bfe16f00a98b87ba9155da68e75936be5d057ec025efa80541bf86a08a5bb85e4b4bd10e2
>
> install : $(TARGET)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2022-11-19 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 19:19 Matthias Fischer
2022-11-18 19:37 ` Peter Müller
2022-11-19 11:52 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F914625-3CA3-4D43-8262-9EBE2101FFFC@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox