-1
$/etc/init.d/bind9 restart
Stopping domain name service...: bind9rndc: connect failed: 127.0.0.1#953: connection refused
.
Starting domain name service...: bind9.

(By the way, this is a continuation of the question here: Can someone see why my DNS won't work? I followed everything in the tutorial, but won't work)

Community
  • 1
Alex
  • 8,471
  • 26
  • 75
  • 99
  • 1
    There is insufficient information here to be able to take a reasonable stab at an answer, and you've been given guidance on what information to provide in your previous question, which should have been extended rather than asking another question. – womble Nov 06 '09 at 23:53

2 Answers2

4

You need to configure Bind and rndc if you want that rndc talk to Bind.

You should have something like that in your named.conf:

controls {
  inet 127.0.0.1 allow { localhost; } keys { <key-name>; };
};

...

key "<key-name>" {
  algorithm hmac-md5;
  secret "<key-value>";
};

and something like that in your rndc.conf:

options {
  default-server  localhost;
  default-key     "<key-name>";
};

...

key "<key-name>" {
  algorithm hmac-md5;
  secret "<key-value>";
};

But you should read named.conf and rndc.conf manuals first ! :)

man named.conf
man rndc.conf
sebthebert
  • 1,234
  • 8
  • 21
1

#953 is the rndc socket for controlling bind. the restart is giving you an error because it tried to connect to the socket and couldn't, probably because bind wasn't actually running.

After the startup script is finished running, does ps auxww show a 'named' process running? if so, and restart doesn't work, check your rndc key setup. If named isn't starting at all, look in the logs for why.

based on your other question you should do some reading before attempting to run dns. I recommend the cricket liu "DNS & Bind" O'Reilley book.

Froggiz
  • 3,043
  • 1
  • 19
  • 30
eric sorenson
  • 971
  • 8
  • 10
  • Yes, it is running. bind 16922 0.0 6.8 215020 22452 ? Ssl 09:49 0:00 /usr/sbin/named -u bind – Alex Nov 06 '09 at 22:20