Bind9 failing to start

Hi, I’m experiencing an issue with Bind9.

It seems to have stop when I run service bind9 start it returns:

Job for named.service failed because the control process exited with error code.
See “systemctl status named.service” and “journalctl -xeu named.service” for details.

When I run systemctl status named.service it returns:

× named.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2024-12-01 02:46:22 SAST; 1min 0s ago
Docs: man:named(8)
Process: 3164145 ExecStart=/usr/sbin/named $OPTIONS (code=exited, status=1/FAILURE)
CPU: 19ms

Dec 01 02:46:22 … systemd[1]: named.service: Control process exited, code=exited, status=1/FAILURE
Dec 01 02:46:22 … systemd[1]: named.service: Failed with result ‘exit-code’.
Dec 01 02:46:22 … systemd[1]: Failed to start BIND Domain Name Server.
Dec 01 02:46:22 … systemd[1]: named.service: Scheduled restart job, restart counter is at 5.
Dec 01 02:46:22 … systemd[1]: Stopped BIND Domain Name Server.
Dec 01 02:46:22 … systemd[1]: named.service: Start request repeated too quickly.
Dec 01 02:46:22 … systemd[1]: named.service: Failed with result ‘exit-code’.
Dec 01 02:46:22 … systemd[1]: Failed to start BIND Domain Name Server.

Finally when I run journalctl -xeu named.service it returns:

Dec 01 02:46:22 … named[3164146]: TKEY mode 3 support (GSS-API): yes

Dec 01 02:46:22 … named[3164146]: loading configuration from ‘/etc/bind/named.conf’

Dec 01 02:46:22 … named[3164146]: directory ‘/var/cache/bind’ is not writable

Dec 01 02:46:22 … named[3164146]: /etc/bind/named.conf.options:2: parsing failed: permission denied

Dec 01 02:46:22 … named[3164146]: loading configuration: permission denied

Dec 01 02:46:22 … named[3164146]: exiting (due to fatal error)

Dec 01 02:46:22 … systemd[1]: named.service: Control process exited, code=exited, status=1/FAILURE

░░ Subject: Unit process exited

░░ Defined-By: systemd

░░ Support: Enterprise open source support | Ubuntu

░░

░░ An ExecStart= process belonging to unit named.service has exited.

░░

░░ The process’ exit code is ‘exited’ and its exit status is 1.

Dec 01 02:46:22 … systemd[1]: named.service: Failed with result ‘exit-code’.

░░ Subject: Unit failed

░░ Defined-By: systemd

░░ Support: Enterprise open source support | Ubuntu

░░

░░ The unit named.service has entered the ‘failed’ state with result ‘exit-code’.

Dec 01 02:46:22 … systemd[1]: Failed to start BIND Domain Name Server.

░░ Subject: A start job for unit named.service has failed

░░ Defined-By: systemd

░░ Support: Enterprise open source support | Ubuntu

░░

░░ A start job for unit named.service has finished with a failure.

░░

░░ The job identifier is 74839 and the job result is failed.

Dec 01 02:46:22 … systemd[1]: named.service: Scheduled restart job, restart counter is at 5.

░░ Subject: Automatic restarting of a unit has been scheduled

░░ Defined-By: systemd

░░ Support: Enterprise open source support | Ubuntu

░░

░░ Automatic restarting of the unit named.service has been scheduled, as the result for

░░ the configured Restart= setting for the unit.

Dec 01 02:46:22 … systemd[1]: Stopped BIND Domain Name Server.

░░ Subject: A stop job for unit named.service has finished

░░ Defined-By: systemd

░░ Support: Enterprise open source support | Ubuntu

░░

░░ A stop job for unit named.service has finished.

░░

░░ The job identifier is 74925 and the job result is done.

Dec 01 02:46:22 … systemd[1]: named.service: Start request repeated too quickly.

Dec 01 02:46:22 … systemd[1]: named.service: Failed with result ‘exit-code’.

░░ Subject: Unit failed

░░ Defined-By: systemd

░░ Support: Enterprise open source support | Ubuntu

░░

░░ The unit named.service has entered the ‘failed’ state with result ‘exit-code’.

Dec 01 02:46:22 … systemd[1]: Failed to start BIND Domain Name Server.

░░ Subject: A start job for unit named.service has failed

░░ Defined-By: systemd

░░ Support: Enterprise open source support | Ubuntu

░░

░░ A start job for unit named.service has finished with a failure.

░░

░░ The job identifier is 74925 and the job result is failed.

Has anyone ever experienced this, or know how to fix it?

@sahsanu or @eris has anyone posted an error like this before?

Dec 01 02:46:22 … named[3164146]: directory ‘/var/cache/bind’ is not writable

Dec 01 02:46:22 … named[3164146]: /etc/bind/named.conf.options:2: parsing failed: permission denied

Check here …