Dns

[ynilesh]

Can you please try starting with default configuration file.? if it starts then we can say something wrong with configured file and then we can move ahead and check configured file. If you have nmap installed on host. try this

nmap localhost

or try this

netstat -an | grep 53

it will tell us whether named service started.

[aking9]

Can you ping your loopback ip address internally or do you get a similar error?

pinging 127.0.0.1 is fine.

[aking9]

Can you please try starting with default configuration file.? if it starts then we can say something wrong with configured file and then we can move ahead and check configured file. If you have nmap installed on host. try this

nmap localhost

or try this

netstat -an | grep 53

it will tell us whether named service started.

swapping named.conf for the sample one provided with bind gives the same error, so I am assuming it is down to rndc not starting?


the netstat command gives this output:

unix 2 [ ACC ] STREAM LISTENING 10085 /tmp/orbit-a_king/linc-135d-0-534b6d6d8387b
unix 3 [ ] STREAM CONNECTED 10665 /tmp/orbit-a_king/linc-135d-0-534b6d6d8387b
unix 3 [ ] STREAM CONNECTED 10353 /tmp/orbit-a_king/linc-139e-0-24b7869f1f725
unix 3 [ ] STREAM CONNECTED 10333 /tmp/orbit-a_king/linc-135d-0-534b6d6d8387b
unix 3 [ ] STREAM CONNECTED 10314 /tmp/orbit-a_king/linc-135d-0-534b6d6d8387b
unix 3 [ ] STREAM CONNECTED 10247 /tmp/orbit-a_king/linc-135d-0-534b6d6d8387b
unix 3 [ ] STREAM CONNECTED 10183 /tmp/orbit-a_king/linc-135d-0-534b6d6d8387b
unix 3 [ ] STREAM CONNECTED 10161 /tmp/orbit-a_king/linc-135d-0-534b6d6d8387b
unix 3 [ ] STREAM CONNECTED 10091 /tmp/orbit-a_king/linc-135d-0-534b6d6d8387b
unix 3 [ ] STREAM CONNECTED 10090 /tmp/orbit-a_king/linc-135d-0-534b6d6d8387b
unix 3 [ ] STREAM CONNECTED 10053 @/tmp/dbus-CtNZ8HhZXf
unix 3 [ ] STREAM CONNECTED 9353 /tmp/.X11-unix/X0


nmap is not installed.

[aking9]

I changed the named.conf file and now I just get a failed message, I have included the tail messages

[root@localhost etc]# service named start
Starting named: [FAILED]

[root@localhost etc]# tail -f /var/log/messages
Jul 29 19:27:56 localhost named[10390]: starting BIND 9.3.4-P1 -u named
Jul 29 19:27:56 localhost named[10390]: found 1 CPU, using 1 worker thread
Jul 29 19:27:56 localhost named[10390]: loading configuration from '/etc/named.conf'
Jul 29 19:27:56 localhost named[10390]: listening on IPv4 interface lo, 127.0.0.1#953
Jul 29 19:27:56 localhost named[10390]: listening on IPv4 interface eth0, 192.168.50.82#953
Jul 29 19:27:56 localhost named[10390]: /etc/named.conf:13: couldn't add command channel 127.0.0.1#953: address in use
Jul 29 19:27:56 localhost named[10390]: logging channel 'query_log' file 'query.log': permission denied
Jul 29 19:27:56 localhost named[10390]: logging channel 'activity_log' file 'activity.log': permission denied
Jul 29 19:27:56 localhost named[10390]: couldn't open pid file 'var/run/named/named.pid': No such file or directory
Jul 29 19:27:56 localhost named[10390]: exiting (due to early fatal error)

[ynilesh]

Can you please check out which process/deamon is using port 953 and kill it and try ?

I assuming you are all this as root(super user) user not normal user.

[aking9]

netstat -an | grep 953 produces nothing. I tried restarting the network see if that cleared it.

[ynilesh]

I can see you are using same port in rndc.conf and named.conf files. Either keep it in rndc.conf or named.conf.

better comment these lines in named.conf and try restarting named service. Please paste logs if it dint work.

default-port 953;

It clearly says in logs that "127.0.0.1#953: address in use" so port must be used by any other application or defined twice in configuration.

ping me on yahoo id incase it doesnt work.
yahoo id : nilesh_patil82

[aking9]

well that has seemed to clear that error.
I still get this though.
couldn't open pid file 'var/run/named/named.pid': No such file or directory

The .pid exists in that location and its attributes are
-rwxr-x--- 1 named named 5 Jul 29 19:39 /var/run/named/named.pid

Added you to yahoo btw

[aking9]

Aargh!
I changed the pid location in named.conf to have a / at the beginning instead of it being var/run.....
thanks a lot for the help guys

[ynilesh]

Better again set it to /var/run/ as its standard location to store system runtime variable data. Change setting in named.conf to store named.pid to /var/run/.