On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Articles in this section

See more

DNS records for domain are not updated: Unable to manage service by dnsmng

Avatar
Miguel Monteiro
Updated
Follow
Plesk for Linux kb: technical ABT: Group B

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

  1. Connect to the server via SSH;

  2. Disable named.service:

    # systemctl disable named.service

  3. Enable named-chroot.service:

    # systemctl enable named-chroot.service
    # ln -s '/usr/lib/systemd/system/named-chroot.service'

  4. 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

5 comments

Sort by Date Votes
  • Avatar
    Tobias Buschor

    If i run step 2. in CentOS 6 this happen:

    systemctl: command not found

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    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.

    0
    Comment actions Permalink
  • Avatar
    Tobias Buschor

    Thanks, I found the problem.

    There was a DNS entry with an underscore "_" in a subdomain which is not allowed.

    0
    Comment actions Permalink
  • Avatar
    Regis

    Houston we have a problem...

    # systemctl start named-chroot.service
    Job for named-chroot.service failed because the control process exited with error code. See "systemctl status named-chroot.service" and "journalctl -xe" for details.

    # systemctl status named-chroot.service
    ● 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 ven. 2020-12-04 07:55:13 CET; 303ms ago
    Process: 5663 ExecStartPre=/usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf (code=exited, status=1/FAILURE)

    déc. 04 07:55:13 kal-srv-01.local systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
    déc. 04 07:55:13 kal-srv-01.local systemd[1]: Unit named-chroot.service entered failed state.
    déc. 04 07:55:13 kal-srv-01.local systemd[1]: named-chroot.service failed.

    0
    Comment actions Permalink
  • Avatar
    BNB

    Having the exact same problem on CentOS 7 - the commands didn't work.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles