I just finished installing 2.1.5 on Slackware-Current. Everything went ok, until I try to do nsdc start, nothing happens. I can run ps -aux after doing that and nsd is not listed. I read in the readme that nsd doesn’t do any logging, but I was hoping there was somewhere I could look for errors.
Any help would be greatly appreciated.
Dave
OK, I found the error entries in syslog but I don't understand why it is
happening.
Error:
Dec 31 15:31:32 SlackDNS nsd[894]: can't bind the socket: Address already in
use
I am passing the flag in nsdc.conf -a 192.168.189.6 so that it will only
listen on that interface. I have bind9 listening on 127.0.0.1 and
192.168.189.5. What else could I be missing? Here is the output of netstat
-an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 192.168.189.5:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 192.168.189.5:22 192.168.189.30:3765
ESTABLISHED
udp 0 0 0.0.0.0:53 0.0.0.0:*
udp 0 0 192.168.189.5:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*
Thanks again for looking
dave
OK, I found the error entries in syslog but I don't understand why it is
happening.
Error:
Dec 31 15:31:32 SlackDNS nsd[894]: can't bind the socket: Address already in
use
I am passing the flag in nsdc.conf -a 192.168.189.6 so that it will only
listen on that interface. I have bind9 listening on 127.0.0.1 and
192.168.189.5. What else could I be missing? Here is the output of netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 192.168.189.5:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 192.168.189.5:22 192.168.189.30:3765
ESTABLISHED
udp 0 0 0.0.0.0:53 0.0.0.0:*
udp 0 0 192.168.189.5:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*
You probably have already a programm listening on por 53. I wouldn't be
suprised that that is "named". Do a ps ax | grep named or, if your system
supports that, do a sockstat to find out.
jaap
`
You're right, but shouldn't it be interface specific? I believe the
0.0.0.0:53 in netstat is what is causing the socket to be busy even though
I limited bind to listen-on 127.0.0.1 and 192.168.189.5. I stopped named
and nsd started just fine and answered digs of my zones. Is there another
way to stop bind from using the 0.0.0.0:53? I have had this setup working
before, but it was on nsd 1.X.
Thanks
Dave
0.0.0.0 means listen on all interfaces. its the default, unless there
is an listen-on directive.
for bind, in named.conf, you can add
listen-on { 127.0.0.1; 192.168.189.5; };
to your options {} block to get it to listen to localhost, and
192.168.189.5.
^--- this is your problem. as was already mentioned, something is binding to
INADDR_ANY. netstat -anep to determine what it is. then fix it.
-p