rndc: connect failed: 127.0.0.1#953: connection refused

Question

This is a very annoying problem that i am having with the rndc reload

I am getting the following error:

rndc: connect failed: 127.0.0.1#953: connection refused

However the following work fine,

[root@cbgfx ~]# service named restart
Stopping named: .                                          [  OK  ]
Starting named:                                            [  OK  ]

[root@cbgfx ~]# tail -f /var/log/messages
Aug  7 12:51:09 cbgfx named[31990]: zone 120.88.167.in-addr.arpa/IN: loaded serial 14
Aug  7 12:51:09 cbgfx named[31990]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
Aug  7 12:51:09 cbgfx named[31990]: zone domain.com/IN: domain.com/MX 'mail.servergreek.com' has no address records (A or AAAA)
Aug  7 12:51:09 cbgfx named[31990]: zone domain.com/IN: loaded serial 14
Aug  7 12:51:09 cbgfx named[31990]: zone localhost.localdomain/IN: loaded serial 0
Aug  7 12:51:09 cbgfx named[31990]: zone localhost/IN: loaded serial 0
Aug  7 12:51:09 cbgfx named[31990]: managed-keys-zone ./IN: loaded serial 4
Aug  7 12:51:09 cbgfx named[31990]: zone domain.com/IN: sending notifies (serial 14)
Aug  7 12:51:09 cbgfx named[31990]: zone 120.88.167.in-addr.arpa/IN: sending notifies (serial 14)
Aug  7 12:51:09 cbgfx named[31990]: running

The vps has ipv6 ip address, is there anything i missed here?

Thanks in advance guys

score 12 · Accepted Answer · edited Jun 20 '20 at 09:12

12

I fixed it myself , it was a permission and ownership issue.To fix it you need to execute those ssh commands

Fix rndc connection refused error

chown root:named /etc/rndc.key

chmod 640 /etc/rndc.key

edited Jun 20 '20 at 09:12

Community

1
1

answered Aug 10 '14 at 05:14

user2650277

6,289
17
63
132

9

or in ubuntu, `chown root:bind /etc/bind/rndc.key` – Nacht Aug 10 '17 at 12:14
3

This only worked for me after I restarted bind9. `service bind9 restart` – jdhildeb Jul 05 '18 at 03:11

score 6 · Answer 2 · answered Aug 31 '15 at 16:55

6

clear the file of directory /var/cache/bind/ and after in terminal bash /etc/bind/bind9 restart

answered Aug 31 '15 at 16:55

Jorge Huamani

91
1
1

score 1 · Answer 3 · answered Mar 03 '15 at 12:06

1

The problem might not only be in rndc.key.

The easiest way to detect is running:

service named restart

Check if there is any error, if there is an error, run:

systemctl status named.service

Check any permission denied error. It could be in the log files as well.

answered Mar 03 '15 at 12:06

bsentosa

166
1
3

In my case, I need to change permission to zone folder (named) to named – bsentosa Apr 21 '15 at 15:45

Vader · Answer 4 · 2019-03-22T12:45:55.197

0

In my case as bsentosa comment I needed start process named, you can enable to named start together within system

$ systemctl enable named

edited Mar 22 '19 at 12:45

answered Mar 15 '19 at 00:39

Vader

123
7

1

Waht is "caso as bsentosa"? I think the question is poor quality already: Obviously when named is *not* running, you cannot tell it to reload. So the question should be "how do I start named"? IMHO too trivial to ask here... – U. Windl Mar 15 '19 at 00:45

score 0 · Answer 5 · answered Jan 24 '23 at 05:03

I am on Mac OS X (Ventura), with Bind9 installed through Brew. I ran into the same issue. I had to run named with sudo to make this error disappear: It was an ownership issue.

Also, you should pay attention to named logs, sometimes you have just errors in your *.zone file.

I hope it will help Mac users landing here.

rndc: connect failed: 127.0.0.1#953: connection refused

5 Answers5

Fix rndc connection refused error