Applicable to:
- Plesk for Linux
Symptoms
DNS records for a domain failed to update with the following error:
PLESK_ERROR: Unable to make action: Unable to manage service by dnsmng: ('start', 'dns'). Error: :
Cause
DNS service was not reloaded because named service is used instead of named-chrooted.
Resolution
-
Connect to the server via SSH;
-
Disable
named.service:# systemctl disable named.service
-
Enable
named-chroot.service:# systemctl enable named-chroot.service
# ln -s '/usr/lib/systemd/system/named-chroot.service' -
Start the
named-chroot.service:# systemctl start named-chroot.service
# systemctl status named-chroot.service
named-chroot.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabled)
Active: active (running) since Wed 2015-01-07 22:57:33 CST; 27min ago
Main PID: 12682 (named)
CGroup: /system.slice/named-chroot.service
└─1035 /usr/sbin/named -u named -t /var/named/chroot -c /etc/named.conf -u named -n 2
Comments
3 comments
If i run step 2. in CentOS 6 this happen:
systemctl: command not found
Tobias, systemctl exists only on CentOS 7. This article don't apply to CentOS 6, because it is running named service, while CentOS 7 only running named-chroot service.
You might be have another reason, please check /var/log/messages on why bind does not start and check for other articles with such symptoms.
Thanks, I found the problem.
There was a DNS entry with an underscore "_" in a subdomain which is not allowed.
Please sign in to leave a comment.