bind-9.16 fails to start with error "directory '/path/to/directory' is not writable" in RHEL9

Solution Unverified - Updated -

Issue

After bind configuration migration to Red Hat Enterprise Linux 9 (bind-9.16) from earlier releases, named.service or named-chroot.service fail to start with the following error messages:

Dec 11 22:47:14 rhel-9.4 named[5884]: loading configuration from '/etc/named.conf'
Dec 11 22:47:14 rhel-9.4 named[5884]: directory '/etc/named' is not writable
Dec 11 22:47:14 rhel-9.4 named[5884]: /etc/named.conf:3: parsing failed: permission denied
Dec 11 22:47:14 rhel-9.4 named[5884]: loading configuration: permission denied
Dec 11 22:47:14 rhel-9.4 named[5884]: exiting (due to fatal error)
Dec 11 22:47:14 rhel-9.4 systemd[1]: named-chroot.service: Control process exited, code=exited, status=1/FAILURE
Dec 11 22:47:14 rhel-9.4 systemd[1]: named-chroot.service: Failed with result 'exit-code'.
Dec 11 22:47:14 rhel-9.4 systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).

The same bind configuration doesn't cause service failure for bind-9.11 on RHEL7 and RHEL8.

Environment

  • Red Hat Enterprise Linux 9
  • bind-9.16 and above

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content