named-chroot service fails to start after latest updates to: $ rpm -qa | grep bind | sort bind9-next-9.21.11-4.fc42.x86_64 bind9-next-chroot-9.21.11-4.fc42.x86_64 bind9-next-dnssec-utils-9.21.11-4.fc42.x86_64 bind9-next-libs-9.21.11-4.fc42.x86_64 bind9-next-license-9.21.11-4.fc42.noarch bind9-next-utils-9.21.11-4.fc42.x86_64 bind-libs-9.18.39-3.fc42.x86_64 Logs: systemd[1]: Starting named-chroot.service - Berkeley Internet Name Domain (DNS)... bash[1056]: isc_dir_chroot: not implemented systemd[1]: named-chroot.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: named-chroot.service: Failed with result 'exit-code'. systemd[1]: Failed to start named-chroot.service - Berkeley Internet Name Domain (DNS). Reproducible: Always Steps to Reproduce: . Actual Results: . Expected Results: . Additional Information: .
Apologies - copy/paste fail. Versions installed: $ rpm -qa | grep bind | sort bind9-next-9.21.11-4.fc42.x86_64 bind9-next-chroot-9.21.11-4.fc42.x86_64 bind9-next-dnssec-utils-9.21.11-4.fc42.x86_64 bind9-next-libs-9.21.11-4.fc42.x86_64 bind9-next-license-9.21.11-4.fc42.noarch bind9-next-utils-9.21.11-4.fc42.x86_64 bind-libs-9.18.39-3.fc42.x86_64
The fix for this has been merged into 9.21.13.
9.21.14 works for me. I had to explicitly disable fuzzing or the meson build blows up. --- bind9-next.spec.old 2025-10-24 12:32:36.054375071 -0400 +++ bind9-next.spec 2025-10-24 12:32:50.847737291 -0400 @@ -65,7 +65,7 @@ Name: bind9-next License: MPL-2.0 AND ISC AND BSD-3-clause AND MIT AND BSD-2-clause # -Version: 9.21.11 +Version: 9.21.14 Release: %autorelease Epoch: 32 Url: https://www.isc.org/downloads/bind/ @@ -107,7 +107,7 @@ # avoid often fails on i386, unsupported upstream Patch4: bind-9.21-unittest-qpdb-i386.patch # Downstream patch to include version in libraries -Patch5: meson-libs.patch +# Patch5: meson-libs.patch %{?systemd_ordering} Requires: coreutils @@ -400,6 +400,7 @@ %if %{with DOC} -Ddoc=enabled \ %endif + -Dfuzzing=disabled \ ; %if %{with DNSTAP} pushd lib @@ -719,7 +720,7 @@ # TODO: Move from lib/bind to lib/named, as used by upstream # FIXME: current build targets filters into %%_libdir/bind again? %dir %{_libdir}/bind -%{_libdir}/bind/filter*.so +%{_libdir}/bind/*.so %dir %{_libdir}/named %config(noreplace) %verify(not md5 size mtime) %{_sysconfdir}/sysconfig/named %config(noreplace) %attr(0644,root,named) %{_sysconfdir}/named.root.key
Created attachment 2112712 [details] srpm for 9.21.14
FEDORA-2025-b68f7f541d (bind9-next-9.21.14-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-b68f7f541d
FEDORA-2025-d9f9394ecd (bind9-next-9.21.14-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-d9f9394ecd
FEDORA-2025-b68f7f541d has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-b68f7f541d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-b68f7f541d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-d9f9394ecd has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d9f9394ecd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d9f9394ecd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-d9f9394ecd (bind9-next-9.21.14-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-b68f7f541d (bind9-next-9.21.14-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.