Resolved DNS BIND Server not working after restart

[Patrice Kast]

Hello Community,

We have used the DNS BIND Service on Plesk Onyx. Then we switched to an external DNS and we now want to switch back to the local BIND server.

We are now running Plesk Obsidian on CentOS 7 and want to reenable the DNS service under Tools & Settings > DNS Server (BIND) and get the following error:

Unable to start service: Unable to manage service by dnsmng: ('start', 'dns'). Error:

We then fixed the problem with the following solution:
Unable to start DNS service in Plesk: /etc/named.conf syntax error (CentOS 7 section)

This fixes the error, but after a server restart or an systemctl restart named-chroot, we get the same error again.

systemctl status named-chroot.service gives us the following message:
named-chroot.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/named-chroot.service.d
└─respawn.conf
Active: activating (auto-restart) (Result: exit-code) since Sun 2020-03-29 20:09:25 CEST; 4s ago
Process: 29938 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=0/SUCCESS)
Process: 29811 ExecReload=/bin/sh -c /usr/sbin/rndc reload > /dev/null 2>&1 || /bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 26308 ExecStart=/usr/sbin/named -u named -t /var/named/chroot $OPTIONS (code=exited, status=0/SUCCESS)
Process: 10486 ExecStartPre=/usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf (code=exited, status=1/FAILURE)
Main PID: 26310 (code=exited, status=0/SUCCESS)

Mar 29 20:09:25 localhost systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Mar 29 20:09:25 localhost systemd[1]: Unit named-chroot.service entered failed state.
Mar 29 20:09:25 localhost systemd[1]: named-chroot.service failed.

Does anyone have an idea, what the problem could be?

Thank you very much!

 

[AYamshanov]

Hi Patrice Kast,

I suppose the right KB, in this case, is Unable to start named/named-chroot: zone example.com has no address records, bad zone. If it doesn't help, could you please post the output of "named" configuration file syntax checking tool ("/usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf")?