• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Plesk DNS Server (BIND) Wont start

BON

New Pleskian
Hello,

My DNS server wont start. I have just noticed this, first I thought the problem was with the domain registrar.

The server throws the following error:

[root@core ~]# systemctl status named
● 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 Mon 2017-06-05 20:10:12 GMT; 2min 50s ago
Process: 11025 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)

Jun 05 20:10:12 core.domain1.tld bash[11025]: zone domain2.tld/IN: loading from master file domain2.tld failed:...found
Jun 05 20:10:12 core.domain1.tld bash[11025]: zone domain2.tld/IN: not loaded due to errors.
Jun 05 20:10:12 core.domain1.tld bash[11025]: _default/domain2.tld/IN: file not found
Jun 05 20:10:12 core.domain1.tld bash[11025]: zone domain1.tld/IN: loading from master file domain1.tld failed: file not found
Jun 05 20:10:12 core.domain1.tld bash[11025]: zone domain1.tld/IN: not loaded due to errors.
Jun 05 20:10:12 core.domain1.tld bash[11025]: _default/domain1.tld/IN: file not found
Jun 05 20:10:12 core.domain1.tld systemd[1]: named.service: control process exited, code=exited status=1
Jun 05 20:10:12 core.domain1.tld systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Jun 05 20:10:12 core.domain1.tld systemd[1]: Unit named.service entered failed state.
Jun 05 20:10:12 core.domain1.tld systemd[1]: named.service failed.
Hint: Some lines were ellipsized, use -l to show in full.



What could be causing this and how do we fix it?

Thanks,
 
plesk repair dns

# plesk repair dns

Checking the DNS configuration file ................................. [OK]
Restoring DNS server configuration
Synchronize DNS zones with the DNS server? [Y/n] y
Synchronizing DNS zones with the DNS server ..................... [OK]
Error messages: 0; Warnings: 0; Errors resolved: 0

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

# journalctl -xe
Jun 06 08:46:33 core.domain1.tld bash[24074]: zone domain3.tld/IN: not loaded due to errors.
Jun 06 08:46:33 core.domain1.tld bash[24074]: _default/domain3.tld/IN: file not found
Jun 06 08:46:33 core.domain1.tld bash[24074]: zone partner.domain2.tld/IN: loading from master file partner.domain2.tld failed: file not found
Jun 06 08:46:33 core.domain1.tld bash[24074]: zone partner.domain2.tld/IN: not loaded due to errors.
Jun 06 08:46:33 core.domain1.tld bash[24074]: _default/partner.domain2.tld/IN: file not found
Jun 06 08:46:33 core.domain1.tld bash[24074]: zone secure.domain2.tld/IN: loading from master file secure.domain2.tld failed: file not found
Jun 06 08:46:33 core.domain1.tld bash[24074]: zone secure.domain2.tld/IN: not loaded due to errors.
Jun 06 08:46:33 core.domain1.tld bash[24074]: _default/secure.domain2.tld/IN: file not found
Jun 06 08:46:33 core.domain1.tld bash[24074]: zone domain2.tld/IN: loading from master file domain2.tld failed: file not found
Jun 06 08:46:33 core.domain1.tld bash[24074]: zone domain2.tld/IN: not loaded due to errors.
Jun 06 08:46:33 core.domain1.tld bash[24074]: _default/domain2.tld/IN: file not found
Jun 06 08:46:33 core.domain1.tld systemd[1]: named.service: control process exited, code=exited status=1
Jun 06 08:46:33 core.domain1.tld systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
-- Subject: Unit named.service has failed
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit named.service has failed.
--
-- The result is failed.
Jun 06 08:46:33 core.domain1.tld systemd[1]: Unit named.service entered failed state.
Jun 06 08:46:33 core.domain1.tld systemd[1]: named.service failed.
Jun 06 08:46:33 core.domain1.tld polkitd[649]: Unregistered Authentication Agent for unix-process:24066:7912106 (system bus name :1.3217, object path /org/freedesktop/PolicyKit1/AuthenticationAgent
Jun 06 08:47:01 core.domain1.tld systemd[1]: Started Session 1577 of user root.
-- Subject: Unit session-1577.scope has finished start-up
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
. . .



Throws an error when I try to restart it. Plesk DNS repair does literally nothing.

What should I try next?
 
Last edited:
Check the status of named-chroot service and try to restart it.

Nope. It's also down. Cannot restart.


# systemctl status named-chroot
● named-chroot.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2017-06-05 20:49:09 GMT; 12h ago
Process: 12853 ExecStartPre=/usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf (code=exited, status=1/FAILURE)

Jun 05 20:49:09 core.domain1.tld named-checkconf[12853]: zone partner.domain2.tld/IN: loaded serial 2017060506
Jun 05 20:49:09 core.domain1.tld named-checkconf[12853]: zone secure.domain2.tld/IN: loaded serial 2017060506
Jun 05 20:49:09 core.domain1.tld named-checkconf[12853]: dns_rdata_fromtext: domain2.tld:37: syntax error
Jun 05 20:49:09 core.domain1.tld named-checkconf[12853]: zone domain2.tld/IN: loading from master file domain2.tld failed: syntax error
Jun 05 20:49:09 core.domain1.tld named-checkconf[12853]: zone domain2.tld/IN: not loaded due to errors.
Jun 05 20:49:09 core.domain1.tld named-checkconf[12853]: _default/domain2.tld/IN: syntax error
Jun 05 20:49:09 core.domain1.tld systemd[1]: named-chroot.service: control process exited, code=exited status=1
Jun 05 20:49:09 core.domain1.tld systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Jun 05 20:49:09 core.domain1.tld systemd[1]: Unit named-chroot.service entered failed state.
Jun 05 20:49:09 core.domain1.tld systemd[1]: named-chroot.service failed.

# systemctl restart named-chroot
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.
 
Let's try find root of "syntax error" issue, run command: /usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf

And post please output of `systemctl list-unit-files | grep ^named`.
 
Let's try find root of "syntax error" issue, run command: /usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf

And post please output of `systemctl list-unit-files | grep ^named`.


Wont it be better if I removed all the domains? And maybe erase all the DNS zones if theres a command for that?


# /usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf
zone 0.0.127.IN-ADDR.ARPA/IN: loading from master file /var/named/chroot/var/localhost.rev failed: file not found
zone 0.0.127.IN-ADDR.ARPA/IN: not loaded due to errors.
_default/0.0.127.IN-ADDR.ARPA/IN: file not found

zone domain5.tld/IN: loading from master file /var/named/chroot/var/domain5.tld failed: file not found
zone domain5.tld/IN: not loaded due to errors.
_default/domain5.tld/IN: file not found

zone domain4.tld/IN: loading from master file /var/named/chroot/var/domain4.tld failed: file not found
zone domain4.tld/IN: not loaded due to errors.
_default/domain4.tld/IN: file not found

zone domain2.tld/IN: loading from master file /var/named/chroot/var/domain3.tld failed: file not found
zone domain3.tld/IN: not loaded due to errors.
_default/domain3.tld/IN: file not found

zone partner.domain2.tld/IN: loading from master file /var/named/chroot/var/partner.domain2.tld failed: file not found
zone partner.domain2.tld/IN: not loaded due to errors.
_default/partner.domain2.tld/IN: file not found

zone secure.domain2.tld/IN: loading from master file /var/named/chroot/var/secure.domain2.tld failed: file not found
zone secure.domain2.tld/IN: not loaded due to errors.
_default/secure.domain2.tld/IN: file not found

zone domain1.tld/IN: loading from master file /var/named/chroot/var/domain1.tld failed: file not found
zone domain1.tld/IN: not loaded due to errors.
_default/domain1.tld/IN: file not found

# systemctl list-unit-files | grep ^named
named-chroot.service enabled
named-setup-rndc.service static
named.service disabled
 
hmm.... but anyway this is strange, it is should be fixed by "repair" tools...

Have you got any settings between texts in file /var/named/chroot/etc/named.conf?

// -- PLEASE ADD YOUR CUSTOM DIRECTIVES BELOW THIS LINE. --
// ...
// -- END OF YOUR CUSTOM DIRECTIVES. --
 
hmm.... but anyway this is strange, it is should be fixed by "repair" tools...

Have you got any settings between texts in file /var/named/chroot/etc/named.conf?

// -- PLEASE ADD YOUR CUSTOM DIRECTIVES BELOW THIS LINE. --
// ...
// -- END OF YOUR CUSTOM DIRECTIVES. --


I tried the command like you said. Same thing.

# systemctl restart named-chroot
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.


It is empty. Theres a bunch of stuff generated by Plesk at the top and bottom of it.



Is there a way to completely cleanse the DNS zones, remove the domains and see if it will cause errors when I add them again?
 
Back
Top