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

DNS Server (BIND) Not running

M

madrussa

Guest
Hi,

I have just updated to 8.1 and noticed that via the plesk cp the DNS Server (BIND) is not running under services management. When I try to start the DNS Server I get the following message:


Unable to make action: Unable to manage service by dnsmng: dnsmng: Service /etc/init.d/named failed to start

0: /usr/local/psa/admin/plib/common_func.php3:155
psaerror(string 'Unable to make action: Unable to manage service by dnsmng: dnsmng: Service /etc/init.d/named failed to start')
1: /usr/local/psa/admin/htdocs/server/restart_services.php:28


I followed instructions on how to start the service:
/etc/init.d/named start

and got a response saying named is already running? So I tried rebooting the server and still the plesk cp is saying the service is stopped.

Some help on convincing Plesk that it is running would be great!

EDIT:

Just loaded up the messages log and this is what I get from rebooting the server


Mar 22 15:34:14 s15248633 named[3223]: exiting
Mar 22 15:35:06 s15248633 named[1831]: starting BIND 9.3.1 -u named -c /etc/named.conf -u named -t /var/named/run-r
Mar 22 15:35:06 s15248633 named[1831]: found 1 CPU, using 1 worker thread
Mar 22 15:35:06 s15248633 named[1831]: loading configuration from '/etc/named.conf'
Mar 22 15:35:06 s15248633 named[1831]: no IPv6 interfaces found
Mar 22 15:35:06 s15248633 named[1831]: listening on IPv4 interface lo, 127.0.0.1#53
Mar 22 15:35:06 s15248633 named[1831]: listening on IPv4 interface eth0, 87.106.69.150#53
Mar 22 15:35:06 s15248633 named[1831]: listening on IPv4 interface eth0:1, 87.106.59.47#53
Mar 22 15:35:06 s15248633 named[1831]: command channel listening on 127.0.0.1#953
Mar 22 15:35:06 s15248633 named[1831]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
Mar 22 15:35:06 s15248633 named[1831]: zone 59.106.87.in-addr.arpa/IN: loaded serial 1174574359
Mar 22 15:35:06 s15248633 named[1831]: zone 69.106.87.in-addr.arpa/IN: loaded serial 1174574359
Mar 22 15:35:06 s15248633 named[1831]: zone hearingdogs.org.uk/IN: loaded serial 1174574359
Mar 22 15:35:06 s15248633 named[1831]: running
Mar 22 16:11:21 s15248633 named[1831]: invalid command from 127.0.0.1#54814: bad auth
Mar 22 16:11:22 s15248633 named[1831]: invalid command from 127.0.0.1#54815: bad auth
Mar 22 16:11:23 s15248633 named[1831]: invalid command from 127.0.0.1#54816: bad auth
Mar 22 16:22:19 s15248633 named[1831]: invalid command from 127.0.0.1#40133: bad auth
Mar 22 16:22:20 s15248633 named[1831]: invalid command from 127.0.0.1#40134: bad auth
Mar 22 16:22:21 s15248633 named[1831]: invalid command from 127.0.0.1#40135: bad auth
Mar 22 16:23:13 s15248633 named[1831]: invalid command from 127.0.0.1#40137: bad auth
Mar 22 16:23:14 s15248633 named[1831]: invalid command from 127.0.0.1#40138: bad auth
Mar 22 16:23:15 s15248633 named[1831]: invalid command from 127.0.0.1#40139: bad auth
Mar 22 16:26:26 s15248633 named[1831]: invalid command from 127.0.0.1#42186: bad auth
Mar 22 16:26:27 s15248633 named[1831]: invalid command from 127.0.0.1#42187: bad auth
Mar 22 16:26:28 s15248633 named[1831]: invalid command from 127.0.0.1#42188: bad auth
 
Sorry I havent got it fixed. It isnt causing any noticable problems. I'm making do with sticking a green working sticker over the top when ever I look at it! :D

I would appreciate it a lot if you do find an answer if you could post it in here.
 
I got it fixed,
in my case it was the key in

/etc/rndc.conf
/etc/rndc.key

there is a value secret, it has to be identical for both, so just change it.

stop named in your console and start it in plesk.

and it shoul be working
 
thank you

Worked perfect for me. the key part in /etc/rndc.key was different than the key part in the /etc/rndc.conf did as you said made the change in the key file to match and worked great. This to happened after upgrade to 8.1 thank you for the fix.
 
Back
Top