Log message:
revbump after devel/protobuf update

Log message:
net/bind918: update to 9.18.32

9.18.32 (2024-12-11)

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

* 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

* {&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 faulty optimization has been
  removed.  [GL #4950]

* 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]

Log message:
*: recursive bump for icu 76 shlib major version bump

Log message:
*: revbump for icu downgrade

Log message:
*: recursive bump for icu 76.1 shlib bump

Log message:
net/bind918: update to 9.18.31

9.18.31 (2024-10-16)

New Features

* Added WALLET type.

  Add the new record type WALLET (262).  This provides a mapping from a
  domain name to a cryptographic currency wallet.  Multiple mappings can
  exist if multiple records exist.  [GL #4947]

Feature Changes

* Allow IXFR-to-AXFR fallback on DNS_R_TOOMANYRECORDS.

  This change allows fallback from an IXFR failure to AXFR when the reason
  is DNS_R_TOOMANYRECORDS.  [GL #4928]

Bug Fixes

* Fix a statistics channel counter bug when "forward only" zones are used.

  When resolving a zone with a "forward only" policy, and finding out that
  all the forwarders were marked as "bad", the "ServerQuota" \ 
counter of the
  statistics channel was incorrectly increased.  This has been fixed.  [GL
  #1793]

* Fix a bug in the static-stub implementation.

  Static-stub addresses and addresses from other sources were being mixed
  together, resulting in static-stub queries going to addresses not
  specified in the configuration, or alternatively, static-stub addresses
  being used instead of the correct server addresses.  [GL #4850]

* Don't allow statistics-channels if libxml2 and libjson-c are not
  configured.

  When BIND 9 is not configured with the libxml2 and libjson-c libraries,
  the use of the statistics-channels option is a fatal error.  [GL #4895]

* Limit the outgoing UDP send queue size.

  If the operating system UDP queue got full and the outgoing UDP sending
  started to be delayed, BIND 9 could exhibit memory spikes as it tried to
  enqueue all the outgoing UDP messages.  It now tries to deliver the
  outgoing UDP messages synchronously; if that fails, it drops the outgoing
  DNS message that would get queued up and then timeout on the client side.
  [GL #4930]

* Do not set SO_INCOMING_CPU.

  Remove the SO_INCOMING_CPU setting as kernel scheduling performs better
  without constraints. [GL #4936]

Known Issues

* There are no new known issues with this release.  See above for a list of
  all known issues affecting this BIND 9 branch.

Log message:
*: recursive bump for protobuf 28.2

two static library became shared libraries - bump to be on the safe side

Log message:
net/bind918: update to 9.18.30

BIND 9.18.30 (2024-09-18)

New Features

* Print the full path of the working directory in startup log messages.

  named now prints its initial working directory during startup, and the
  changed working directory when loading or reloading its configuration
  file, if it has a valid directory option defined.  [GL #4731]

Feature Changes

* Follow the number of CPUs set by taskset/cpuset.

  Administrators may wish to constrain the set of cores that named runs on
  via the taskset, cpuset, or numactl programs (or equivalents on other
  OSes).

  If the admin has used taskset, named now automatically uses the given
  number of CPUs rather than the system-wide count. [GL #4884]

Bug Fixes

* Verification of the privacy of an EDDSA key was broken.

  The check could lead to an attempt to sign records with a public key,
  which could cause a segmentation failure (read of a NULL pointer) within
  OpenSSL.  This has been fixed. [GL #4855]

* Fix algorithm rollover bug when there are two keys with the same keytag.

  If there was an algorithm rollover and two keys of different algorithms
  shared the same keytags, there was the possibility that the check of
  whether the key matched a specific state could be performed against the
  wrong key.  This has been fixed by not only checking for the matching key
  tag but also the key algorithm.  [GL #4878]

Known Issues

* There are no new known issues with this release. See above for a list of
  all known issues affecting this BIND 9 branch.