Unable to upgrade BIND v9.19.11 on Ubuntu without error

[Darren Ankney]

Hi Richard,

It looks like you have an error in the configuration file
/etc/bind/named.conf.logging on line 147:

Jul 10 19:49:07 flons3 named[1140]: /etc/bind/named.conf.logging:147:
undefined category: 'delegation-only'
Jul 10 19:49:07 flons3 named[1140]: loading configuration: failure

I assume this is an included file that has your logging configuration?

It would be helpful to see the named configuration.  You can get that
with named-checkconf -px which will hide any keys and pull in any
includes.

Thank you,

Darren Ankney

On Mon, Jul 10, 2023 at 3:59 PM Richard T.A. Neal
<richard at richardneal.com> wrote:
>
> For the past few releases I’ve been unable to successfully upgrade my BIND v9.19.11 on Ubuntu 22.04.2 LTS.
>
>
>
> The upgrade appears to go OK at first but then it stumbles at the following line. I’ve had to re-type this because my console tool can’t copy/paste this segment for some reason:
>
>
>
> Process: 6162 ExecStart=/usr/sbin/named -f $OPTIONS (code=exited, status=1/FAILURE)
>
>
>
> Upon a reboot I then get the following in Syslog:
>
>
>
> Jul 10 19:49:07 flons3 named[1140]: BIND 9 is maintained by Internet Systems Consortium,
>
> Jul 10 19:49:07 flons3 named[1140]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
>
> Jul 10 19:49:07 flons3 named[1140]: corporation.  Support and training for BIND 9 are
>
> Jul 10 19:49:07 flons3 named[1140]: available at https://www.isc.org/support
>
> Jul 10 19:49:07 flons3 named[1140]: ----------------------------------------------------
>
> Jul 10 19:49:07 flons3 named[1140]: adjusted limit on open files from 1024 to 524288
>
> Jul 10 19:49:07 flons3 named[1140]: found 2 CPUs, using 2 worker threads
>
> Jul 10 19:49:07 flons3 named[1140]: using 2 UDP listeners per interface
>
> Jul 10 19:49:07 flons3 named[1140]: DNSSEC algorithms: RSASHA1 NSEC3RSASHA1 RSASHA256 RSASHA512 ECDSAP256SHA256 ECDSAP384SHA384 ED25519 ED448
>
> Jul 10 19:49:07 flons3 named[1140]: DS algorithms: SHA-1 SHA-256 SHA-384
>
> Jul 10 19:49:07 flons3 named[1140]: HMAC algorithms: HMAC-MD5 HMAC-SHA1 HMAC-SHA224 HMAC-SHA256 HMAC-SHA384 HMAC-SHA512
>
> Jul 10 19:49:07 flons3 named[1140]: TKEY mode 2 support (Diffie-Hellman): no
>
> Jul 10 19:49:07 flons3 named[1140]: TKEY mode 3 support (GSS-API): yes
>
> Jul 10 19:49:07 flons3 named[1140]: Disabling periodic interface re-scans timer
>
> Jul 10 19:49:07 flons3 named[1140]: config.c: option 'trust-anchor-telemetry' is experimental and subject to change in the future
>
> Jul 10 19:49:07 flons3 named[1140]: loading configuration from '/etc/bind/named.conf'
>
> Jul 10 19:49:07 flons3 named[1140]: /etc/bind/named.conf.logging:147: undefined category: 'delegation-only'
>
> Jul 10 19:49:07 flons3 named[1140]: loading configuration: failure
>
> Jul 10 19:49:07 flons3 named[1140]: exiting (due to fatal error)
>
> Jul 10 19:49:07 flons3 systemd[1]: named.service: Main process exited, code=exited, status=1/FAILURE
>
> Jul 10 19:49:07 flons3 systemd[1]: named.service: Failed with result 'exit-code'.
>
> Jul 10 19:49:07 flons3 systemd[1]: Failed to start BIND Domain Name Server.
>
>
>
> Would someone be kind enough to let me know what other info I can provide so this can be troubleshooted?
>
>
>
> Thanks,
>
>
>
> Richard.
>
>
>
> --
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
>
> ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
>
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users