Hello,

I just installed cpanel on a fresh fedora core server. I am using 15 day trial from cpanel.net

When I add an account to the server I get the following error:
Added Entries to httpd.conf (noip)
Bind reloading on ubhosting02 using rndc
Error reloading bind on hostname: rndc: connect failed: connection refused


I have checked in /var/log/messages and see the following:

Nov 5 23:07:40 host named[13588]: shutting down
Nov 5 23:07:40 host named[13588]: no longer listening on 127.0.0.1#53
Nov 5 23:07:40 host named[13588]: no longer listening on 66.79.190.210#53
Nov 5 23:07:40 host named[13586]: exiting
Nov 5 23:07:40 host named: named shutdown succeeded
Nov 5 23:07:42 host named[13938]: starting BIND 9.2.2-P3 -u named
Nov 5 23:07:42 host named[13938]: using 1 CPU
Nov 5 23:07:42 host named[13940]: loading configuration from '/etc/named.conf'
Nov 5 23:07:42 host named: named startup succeeded
Nov 5 23:07:42 host named[13940]: no IPv6 interfaces found
Nov 5 23:07:42 host named[13940]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 5 23:07:42 host named[13940]: listening on IPv4 interface eth0, 66.79.190.210#53
Nov 5 23:07:42 host named[13940]: /etc/named.conf:2: couldn't install keys for command channel 127.0.0.1#953: not found
Nov 5 23:07:42 host named[13940]: /etc/named.conf:2: couldn't add command channel 127.0.0.1#953: not found
Nov 5 23:07:42 host named[13940]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Nov 5 23:07:42 host named[13940]: zone tsting.com/IN: loaded serial 2004110501
Nov 5 23:07:42 host named[13940]: zone localhost/IN: loaded serial 42
Nov 5 23:07:42 host named[13940]: zone hostname/IN: loaded serial 2004110502
Nov 5 23:07:42 host named[13940]: running
Nov 5 23:07:42 host named[13940]: zone hostname/IN: sending notifies (serial 2004110502)
Nov 5 23:07:42 host named[13940]: zone tsting.com/IN: sending notifies (serial 2004110501)
Nov 5 23:07:47 host named[13940]: shutting down
Nov 5 23:07:47 host named[13940]: no longer listening on 127.0.0.1#53
Nov 5 23:07:47 host named[13940]: no longer listening on 66.79.190.210#53
Nov 5 23:07:47 host named[13938]: exiting
Nov 5 23:07:47 host named: named shutdown succeeded
Nov 5 23:07:49 host named[13967]: starting BIND 9.2.2-P3 -u named
Nov 5 23:07:49 host named[13967]: using 1 CPU
Nov 5 23:07:49 host named[13969]: loading configuration from '/etc/named.conf'
Nov 5 23:07:49 host named: named startup succeeded
Nov 5 23:07:49 host named[13969]: no IPv6 interfaces found
Nov 5 23:07:49 host named[13969]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 5 23:07:49 host named[13969]: listening on IPv4 interface eth0, 66.79.190.210#53
Nov 5 23:07:49 host named[13969]: /etc/named.conf:2: couldn't install keys for command channel 127.0.0.1#953: not found
Nov 5 23:07:49 host named[13969]: /etc/named.conf:2: couldn't add command channel 127.0.0.1#953: not found
Nov 5 23:07:49 host named[13969]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Nov 5 23:07:49 host named[13969]: zone tsting.com/IN: loaded serial 2004110501
Nov 5 23:07:49 host named[13969]: zone localhost/IN: loaded serial 42
Nov 5 23:07:49 host named[13969]: zone hostname/IN: loaded serial 2004110502
Nov 5 23:07:49 host named[13969]: running
Nov 5 23:07:49 host named[13969]: zone tsting.com/IN: sending notifies (serial 2004110501)
Nov 5 23:07:49 host named[13969]: zone hostname/IN: sending notifies (serial 2004110502)


Can you please tell me how to fix this error :bawling:

I have 3 new servers of such and this error is occuring in all three of them. And these servers are from managed.com

you should fix the rndc.conf/named.conf file...

What should I fix in that file?

Post your named.conf/rndc.conf file please.

My rndc.conf file seems to be fine.


# Start of rndc.conf
key "rndc-key" {
algorithm hmac-md5;
secret "XIA14I2i7UtmC31OQAB1tg==";
};

options {
default-key "rndc-key";
default-server 127.0.0.1;
default-port 953;
};
# End of rndc.conf

# Use with the following in named.conf, adjusting the allow list as needed:
# key "rndc-key" {
# algorithm hmac-md5;
# secret "XIA14I2i7UtmC31OQAB1tg==";
# };
#
# controls {
# inet 127.0.0.1 port 953
# allow { 127.0.0.1; } keys { "rndc-key"; };
# };
# End of named.conf

Hello I have found that

key "rndc-key" {
algorithm hmac-md5;
secret "XIA14I2i7UtmC31OQAB1tg==";
};

Is not present in named.conf and when I add it. It failes to restart.

What should I do?

Post the named.conf

My named.conf is:


controls {
inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
};


// generated by named-bootconf.pl

options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};

//
// a caching only nameserver config
//
zone "." IN {
type hint;
file "/var/named/named.ca";
};

zone "localhost" IN {
type master;
file "/var/named/localhost.zone";
allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "/var/named/named.local";
allow-update { none; };
};

--
key "rndc-key" {
algorithm hmac-md5;
secret "XIA14I2i7UtmC31OQAB1tg==";
};

controls {
inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
};

zone "." {
type hint;
file "/var/named/named.ca";
};
--

Use this as named.conf and lets see what it comes with.

# service named restart

I have tried restarting it and it worked :)

The key was missing.
I am a beginner and this was a great lesson learned:)

Thank you for your help.

I have removed your localhost entry to keep my post shorter, you may add it to your named.conf again if you have deleted it. Glad, its working.