• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue named want start

solucionesuno

Regular Pleskian
Centos 7

after restart the service:

Feb 20 22:28:27 ns1 systemd: named-chroot.service: control process exited, code=exited status=1
Feb 20 22:28:27 ns1 systemd: Failed to start Berkeley Internet Name Domain (DNS).
Feb 20 22:28:27 ns1 systemd: Unit named-chroot.service entered failed state.
Feb 20 22:28:27 ns1 systemd: named-chroot.service failed.
 
rpm -qf /etc/named.conf
bind-9.9.4-38.el7_3.2.x86_64


ls -la /etc/named.conf
lrwxrwxrwx 1 root root 32 nov 29 20:15 /etc/named.conf -> /var/named/chroot/etc/named.conf
 
systemctl status named.service
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since lun 2017-02-20 23:45:26 CET; 4s ago
Process: 15720 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE)
Main PID: 2126 (code=exited, status=0/SUCCESS)
 
Service "named-chroot.service" cannot be restarted but you can start it, is it right? Is this reproducible every time?

Could you check "systemctl -l status named-chroot.service" if problem repeated?
 
Last edited:
Back
Top