bind/named rndc: connect failed: 127.0.0.1#953: connection refused (solution)
service named status
rndc: connect failed: 127.0.0.1#953: connection refused
named (pid 10557) is running...
This issue is normally caused by a permissions issue where named doesn't have the permissions to read the rndc.key.
Check /var/log/messages:
Jan 4 17:06:22 storagebox named[10753]: none:0: open: /etc/rndc.key: permission denied
Jan 4 17:06:22 storagebox named[10753]: couldn't add command channel 127.0.0.1#953: permission denied
Jan 4 17:06:22 storagebox named[10753]: none:0: open: /etc/rndc.key: permission denied
Jan 4 17:06:22 storagebox named[10753]: couldn't add command channel ::1#953: permission denied
Solution Update /etc/rndc.key Permissions To The Correct Owner:
chown named.named /etc/rndc.key
service named restart
service named status
It is all good now!
version: 9.8.2rc1-RedHat-9.8.2-0.47.rc1.el6_8.3
CPUs found: 8
worker threads: 8
number of zones: 20
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid 11067) is running...
Tags:
bind, rndc, pid, var, storagebox, etc, couldn, chown, restart, rc, redhat, _, cpus, threads, zones, debug, xfers, deferred, soa, queries, query, logging, recursive, tcp, server,