• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue dns not starting

F

FYI

Basic Pleskian
Hey guys,

actually i'm looking around plesk and gonna a fast-install over the plesk website to my server. Just lookiong a bit around, setting up and looking if plesk is a good system for me.

Actually i'm setting up the first domain. Its created automatically the dns zone and i changed the nameserver on my domain hoster to ns1.mydomain.tld and ns2.mydomain.tld. The hoster is setting up glue records for me (need to register my nameserver with hostname and ip adress).

DNSChecker cant find my NS entries and also not an A Record for the domain or the nsX.domain.tld - but its for than 24 hours.

I've checked and saw, that the DNS Server isnt running. If i try to start the following error coming:
"The service can not be started: Service can not be managed with dnsmng: ('start', 'dns'). error:"

I done a "plesk repair dns" - its checking the dns configuration file - ok. Restoring DNS Server configuration - ok. Sync DNS zones with server - ok.

0 Warnings, 0 Errors, 0 Errors resolved.

What can i do?


Greetings
 
Okay, here some more informations about:

The installlog says the following:
Code: 
===> Installing and configuring Named Server

 Checking for the system groups and users necessary for named (bind)...
 Checking for the group 'bind'...
 Group 'bind' already exists

 Checking for the user 'bind'...
 User 'bind' already exists

Stop running named daemon
 Trying to stop service bind9... done
 Trying to create named run-root directory... done
 Trying to untar named run-root directory structure... done
 Trying to create named.conf... done
 Trying to set up default permissions... done
 Trying to register service bind9... done
 Trying to stop service bind9... done
 Trying to start service bind9... Dec 11 13:56:07 myhostname systemd[1]: bind9.service: Start operation timed out. Terminating.
Dec 11 13:56:07 myhostname named[545]: shutting down
Dec 11 13:56:07 myhostname named[545]: stopping command channel on 127.0.0.1#953
Dec 11 13:56:07 myhostname named[545]: no longer listening on ::#53
Dec 11 13:56:07 myhostname named[545]: no longer listening on 127.0.0.1#53
Dec 11 13:56:07 myhostname named[545]: no longer listening on my.ip.addr.ess#53
Dec 11 13:56:07 myhostname named[545]: exiting
Dec 11 13:56:07 myhostname systemd[1]: Failed to start BIND Domain Name Server.
Dec 11 13:56:07 myhostname systemd[1]: bind9.service: Unit entered failed state.
Dec 11 13:56:07 myhostname systemd[1]: bind9.service: Failed with result 'timeout'.

WARNING!
Some problems are found during start service bind9(see log file: /var/log/plesk/install/plesk_17.8.11_installation.log)

Continue...

Trying to reinstall not working - same error after installation:
Code: 
root@myhostname:~# apt-get remove --purge bind9
root@myhostname:~# /usr/local/psa/admin/sbin/autoinstaller --select-release-current --install-component bind

syslog:
Code: 
Dec 12 08:34:06 myhostname systemd[1]: Starting BIND Domain Name Server...
Dec 12 08:34:06 myhostname named[13900]: starting BIND 9.11.4-P2-3~bpo9+1-Debian (Extended Support Version) <id:7107deb>
Dec 12 08:34:06 myhostname named[13900]: running on Linux x86_64 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27)
Dec 12 08:34:06 myhostname named[13900]: built with[...]
Dec 12 08:34:06 myhostname named[13900]: running as: named -f -t /var/named/run-root -c /etc/named.conf -u bind -n 2
Dec 12 08:34:06 myhostname named[13900]: compiled by GCC 6.3.0 20170516
Dec 12 08:34:06 myhostname named[13900]: compiled with OpenSSL version: OpenSSL 1.1.0f  25 May 2017
Dec 12 08:34:06 myhostname named[13900]: linked to OpenSSL version: OpenSSL 1.1.0j  20 Nov 2018
Dec 12 08:34:06 myhostname named[13900]: compiled with libxml2 version: 2.9.4
Dec 12 08:34:06 myhostname named[13900]: linked to libxml2 version: 20904
Dec 12 08:34:06 myhostname named[13900]: compiled with libjson-c version: 0.12.1
Dec 12 08:34:06 myhostname named[13900]: linked to libjson-c version: 0.12.1
Dec 12 08:34:06 myhostname named[13900]: threads support is enabled
Dec 12 08:34:06 myhostname named[13900]: ----------------------------------------------------
Dec 12 08:34:06 myhostname named[13900]: BIND 9 is maintained by Internet Systems Consortium,
Dec 12 08:34:06 myhostname named[13900]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Dec 12 08:34:06 myhostname named[13900]: corporation.  Support and training for BIND 9 are
Dec 12 08:34:06 myhostname named[13900]: available at https://www.isc.org/support
Dec 12 08:34:06 myhostname named[13900]: ----------------------------------------------------
Dec 12 08:34:06 myhostname named[13900]: adjusted limit on open files from 4096 to 1048576
Dec 12 08:34:06 myhostname named[13900]: found 2 CPUs, using 2 worker threads
Dec 12 08:34:06 myhostname named[13900]: using 1 UDP listener per interface
Dec 12 08:34:06 myhostname named[13900]: using up to 4096 sockets
Dec 12 08:34:06 myhostname named[13900]: loading configuration from '/etc/named.conf'
Dec 12 08:34:06 myhostname named[13900]: unable to open '/etc/bind/bind.keys'; using built-in keys instead
Dec 12 08:34:06 myhostname named[13900]: GeoIP Country (IPv4) (type 1) DB not available
[...]
Dec 12 08:34:06 myhostname named[13900]: GeoIP NetSpeed (type 10) DB not available
Dec 12 08:34:06 myhostname named[13900]: using default UDP/IPv4 port range: [1024, 65535]
Dec 12 08:34:06 myhostname named[13900]: using default UDP/IPv6 port range: [1024, 65535]
Dec 12 08:34:06 myhostname named[13900]: listening on IPv6 interfaces, port 53
Dec 12 08:34:06 myhostname named[13900]: listening on IPv4 interface lo, 127.0.0.1#53
Dec 12 08:34:06 myhostname named[13900]: listening on IPv4 interface eth0, my.ip.addr.ess#53
Dec 12 08:34:06 myhostname named[13900]: listening on IPv4 interface docker0, 172.17.0.1#53
Dec 12 08:34:06 myhostname named[13900]: generating session key for dynamic DNS
Dec 12 08:34:06 myhostname named[13900]: couldn't mkdir '//run': Permission denied
Dec 12 08:34:06 myhostname named[13900]: could not create //run/named/session.key
Dec 12 08:34:06 myhostname named[13900]: failed to generate session key for dynamic DNS: permission denied
Dec 12 08:34:06 myhostname named[13900]: sizing zone task pool based on 3 zones
Dec 12 08:34:06 myhostname named[13900]: none:106: 'max-cache-size 90%' - setting to 3473MB (out of 3859MB)
Dec 12 08:34:06 myhostname named[13900]: set up managed keys zone for view _default, file 'managed-keys.bind'
Dec 12 08:34:06 myhostname named[13900]: automatic empty zone: 10.IN-ADDR.ARPA
[...]
Dec 12 08:34:06 myhostname named[13900]: automatic empty zone: HOME.ARPA
Dec 12 08:34:06 myhostname named[13900]: none:106: 'max-cache-size 90%' - setting to 3473MB (out of 3859MB)
Dec 12 08:34:06 myhostname named[13900]: command channel listening on 127.0.0.1#953
Dec 12 08:34:06 myhostname named[13900]: managed-keys-zone: loaded serial 0
Dec 12 08:34:06 myhostname named[13900]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
Dec 12 08:34:06 myhostname named[13900]: zone myhostname.biz/IN: loaded serial 2018121108
Dec 12 08:34:06 myhostname named[13900]: all zones loaded
Dec 12 08:34:06 myhostname named[13900]: running
Dec 12 08:34:06 myhostname named[13900]: zone myhostname.biz/IN: sending notifies (serial 2018121108)
Dec 12 08:35:36 myhostname systemd[1]: bind9.service: Start operation timed out. Terminating.
Dec 12 08:35:36 myhostname named[13900]: shutting down
Dec 12 08:35:36 myhostname named[13900]: stopping command channel on 127.0.0.1#953
Dec 12 08:35:36 myhostname named[13900]: no longer listening on ::#53
Dec 12 08:35:36 myhostname named[13900]: no longer listening on 127.0.0.1#53
Dec 12 08:35:36 myhostname named[13900]: no longer listening on my.ip.addr.ess#53
Dec 12 08:35:36 myhostname named[13900]: no longer listening on 172.17.0.1#53
Dec 12 08:35:36 myhostname named[13900]: exiting
Dec 12 08:35:36 myhostname systemd[1]: Failed to start BIND Domain Name Server.
Dec 12 08:35:36 myhostname systemd[1]: bind9.service: Unit entered failed state.
Dec 12 08:35:36 myhostname systemd[1]: bind9.service: Failed with result 'timeout'.
 
  1. Open /lib/systemd/system/bind9.service and verify, that the content is exactly as stated:

    [Unit]
    Description=BIND Domain Name Server
    Documentation=man:named(8)
    After=network.target
    Wants=nss-lookup.target
    Before=nss-lookup.target
    [Service]
    EnvironmentFile=/etc/default/bind9
    ExecStart=/usr/sbin/named -f$OPTIONS
    ExecReload=/usr/sbin/rndc reload
    ExecStop=/usr/sbin/rndc stop
    [Install]
    WantedBy=multi-user.target

  2. Apply the configuration and start the service:

    # systemctl daemon-reload
    # systemctl start bind9
 
  • Like
Reactions: FYI
Just for ur correction:
ExecStart=/usr/sbin/named -f$OPTIONS

Should be:
ExecStart=/usr/sbin/named -f $OPTIONS

Its now up and running :) Thank u!
 
You must log in or register to reply here.

Similar threads

O
Issue Wrong TXT record implementation in Plesk DNS
Replies
6
Views
1K
Sebahat.hadzhi
Sebahat.hadzhi
L
Issue error message (Slave DNS Manager)
Replies
1
Views
583
Kaspar@Plesk
Kaspar@Plesk
M
Resolved Lets Encrypt not issuing certs for subdomains
Replies
2
Views
362
mendip_discovery
M
B
Issue Assistance Required: Correct DNS Settings for Mail Servers in Plesk
Replies
0
Views
862
BHK
B
T
DNS not resolvable and websites not working URGENT
Replies
2
Views
3K
Adivl
A
Back
Top