1

I followed everything EXACTLY in this tutorial for setting up DNS. I set up everything on a blank server.

However, starting BIND9 failed:

rndc: connect failed: 127.0.0.1#953: connection refused

I have Googled this, and it seems like there is not a good, solid answer.

Alex
  • 8,111
  • 24
  • 71
  • 99
  • 1
    Alex: Please follow the suggestions Florin, Yves, and Unknown gave, and come back here with the results. (Assuming you don't figure it out in the meantime.) – Schof Nov 10 '09 at 00:32
  • Can you post your named.conf in here? and try to find a clue from syslog after start / restarting named service. – david Jan 22 '13 at 09:37

5 Answers5

7

Check the logs, especially /var/log/daemon.log

There's got to be a clue in there somewhere.

Florin Andrei
  • 1,148
  • 1
  • 11
  • 18
1

Review your named.conf file and your procedures. Check the named daemon logs. Most likely you didn't create an rndc key, or it has the wrong permissions.

Usually this command would help:

rndc-confgen -r /dev/urandom -a

Yves Junqueira
  • 671
  • 3
  • 7
0

Find rndc.key and ensure that it has rw file permissions for root and read for user bind. The location below is on Ubuntu 10.04 LTS, yours may vary. 

-rw-r----- 1 root bind 77 Sep 17 17:31 /etc/bind/rndc.key
joseph_morris
  • 235
  • 3
  • 9
0

Check whether you have SELinux or AppArmor, sometimes they mess with way file permissions are handled. /var/log/* should reflect that.

0

The answer is that I had "forwarders" in my named.conf.options file...and this was unrecognized.

Alex
  • 8,111
  • 24
  • 71
  • 99