Opened 4 months ago

Closed 4 months ago

#20792 closed enhancement (fixed)

bind9 bind 9.20.4

Reported by: Bruce Dubbs Owned by: thomas
Priority: normal Milestone: 12.3
Component: BOOK Version: git
Severity: normal Keywords:
Cc:

Description

New point version.

Change History (4)

comment:1 by thomas, 4 months ago

Resolution: fixed
Status: newclosed

https://bind9.readthedocs.io/en/bind-9.20/notes.html#notes-for-bind-9-20-4

New Features

  • Update built-in bind.keys file with the new 2025 IANA root key.

Add an initial-ds entry to bind.keys for the new root key, ID 38696, which is scheduled for publication in January 2025. [GL #4896]

Removed Features

  • Move contributed DLZ modules into a separate repository. DLZ modules should not be used except in testing.

The DLZ modules were not maintained, the DLZ interface itself is going to be scheduled for removal, and the DLZ interface is blocking. Any module that blocks the query to the database blocks the whole server.

The DLZ modules now live in https://gitlab.isc.org/isc-projects/dlz-modules repository. [GL #4865]

Feature Changes

  • dnssec-ksr now supports KSK rollovers.

The tool now allows for KSK generation, as well as planned KSK rollovers. When signing a bundle from a Key Signing Request (KSR), only the key that is active in that time frame is used for signing. Also, the CDS and CDNSKEY records are now added and removed at the correct time. [GL #4697] [GL #4705]

  • Print RFC 7314: EXPIRE option in transfer summary. [GL #5013]
  • Emit more helpful log messages for exceeding max-records-per-type.

The new log message is emitted when adding or updating an RRset fails due to exceeding the max-records-per-type limit. The log includes the owner name and type, corresponding zone name, and the limit value. It will be emitted on loading a zone file, inbound zone transfer (both AXFR and IXFR), handling a DDNS update, or updating a cache DB. It’s especially helpful in the case of zone transfer, since the secondary side doesn’t have direct access to the offending zone data.

It could also be used for max-types-per-name, but this change doesn’t implement it yet as it’s much less likely to happen in practice.

  • Harden key management when key files have become unavailable.

Prior to doing key management, BIND 9 will check if the key files on disk match the expected keys. If key files for previously observed keys have become unavailable, this will prevent the internal key manager from running.

Bug Fixes

  • Use TLS for notifies if configured to do so.

Notifies configured to use TLS will now be sent over TLS, instead of plain text UDP or TCP. Also, failing to load the TLS configuration for notify now results in an error. [GL #4821]

  • {&dns} is as valid as {?dns} in a SVCB’s dohpath.

dig failed to parse a valid SVCB record with a dohpath URI template containing a {&dns}, like dohpath=/some/path?key=value{&dns}”. [GL #4922]

  • Fix NSEC3 closest encloser lookup for names with empty non-terminals.

A previous performance optimization for finding the NSEC3 closest encloser when generating authoritative responses could cause servers to return incorrect NSEC3 records in some cases. This has been fixed. [GL #4950]

  • recursive-clients statement with value 0 triggered an assertion failure.

BIND 9.20.0 broke recursive-clients 0;. This has now been fixed. [GL #4987]

  • Parsing of hostnames in rndc.conf was broken.

When DSCP support was removed, parsing of hostnames in rndc.conf was accidentally broken, resulting in an assertion failure. This has been fixed. [GL #4991]

  • dig options of the form [+-]option=<value> failed to display the value on the printed command line. This has been fixed. [GL #4993]
  • Provide more visibility into TLS configuration errors by logging SSL_CTX_use_certificate_chain_file() and SSL_CTX_use_PrivateKey_file() errors individually. [GL #5008]
  • Fix a race condition when canceling ADB find which could cause an assertion failure. [GL #5024]
  • SERVFAIL cache memory cleaning is now more aggressive; it no longer consumes a lot of memory if the server encounters many SERVFAILs at once. [GL #5025]
  • Fix trying the next primary XoT server when the previous one was marked as unreachable.

In some cases named failed to try the next primary server in the primaries list when the previous one was marked as unreachable. This has been fixed. [GL #5038]

comment:2 by thomas, 4 months ago

Resolution: fixed
Status: closedreopened

Oops, accidently closed instead of accepted

comment:3 by thomas, 4 months ago

Owner: changed from blfs-book to thomas
Status: reopenednew

comment:4 by thomas, 4 months ago

Resolution: fixed
Status: newclosed

Fixed in [9983e2e84a]

Note: See TracTickets for help on using tickets.