rndc: connect failed: 127.0.0.1#953: connection refused
Hi all,
Im having some problem with my DNS. We are using a Linux web server as one of our web server which runs some live websites.When I trying to get the status of the DNS (NAMED) it comes the following error : [root@ns milindras]# /etc/init.d/named status rndc: connect failed: 127.0.0.1#953: connection refused The same error appears when Im trying to apply any changes on zone level for a selected doamin in WEBMIN. (Basically can't apply changes) WEBMIN > Servers > BIND DNS servers > click a selected-domain.co.uk > Apply changes NDC command failed : rndc: connect failed: 127.0.0.1#953: connection refused But the server seems to be running without effecting any probelms to the sites or users. I have been searching weeks for this problem & couldn't find a solution. And also Please note that Im bit new to Linux. Server details : Linux version 2.6.18-1.2257.fc5smp Red Hat 4.1.1-1 Appreciate any help on this problem. Thanks regards Milindra |
Since named is running, the error you get means that rndc is not configured. You can use this guide to configure rndc.
Regards |
Quote:
Thanks regards Milindra |
2 Attachment(s)
Quote:
Please see the attached files. My Key is in a diffrent file called rndc.key in the /etc/rndc.key directory. You can see the path for that key on the attached files. Thanks Milindra |
Change locahost with its IP: 127.0.0.1 in /etc/rndc.conf and in the "controls" statement in named.conf, restart named and see if it works.
|
Quote:
I changed localhost to IP address, but it seems still no luck. named.config file : controls { inet 127.0.0.1 allow { 127.0.0.1; } keys { rndckey; }; }; rndc.conf file : options { default-server 127.0.0.1; default-key "rndckey"; }; server 127.0.0.1 { key "rndckey"; }; [root@ns ~]# /etc/init.d/named restart Stopping named: ...........................................[ OK ]o response, killing with -TERM Starting named: named: already running |
Take a look at /var/log/messages or /var/log/syslog (or whatever file your distro uses for named logs) to see if you find anything
Also what is the output of: Code:
netstat -tan|grep 953 |
Quote:
Mar 30 18:55:58 ns named[25171]: stopping command channel on 127.0.0.1#953 [root@ns log]# netstat -tan|grep 953 [root@ns log]# ps -ef|grep named named 25171 1 0 Feb05 ? 00:02:32 /usr/sbin/named -u named root 28075 26813 0 15:37 pts/6 00:00:00 grep named [root@ns log]# Thanks |
What happened on March 30 that caused rndc to stop? Do you remember upgrading any packages related to bind?
I don't see also in the logs the restarting of bind, so could you try to do it the hard way: Code:
pkill named |
1 Attachment(s)
Quote:
Thanks |
Quote:
But I deleted all the slave domain because of this error. thanks |
According to logs, bind and rndc started normally at 17:57:17.
If you didn't stop bind right after that, they both somehow stopped at 17:59:22 without anything logged. Check if named is running now and listens on port 53: Code:
netstat -tanpl|grep named |
Quote:
Thats correct. I did not do anything at 17:59:22. It has stopped automatically. When I run netstat -tanpl|grep named Nothing comes up. Thanks Milindra |
You can run named in foreground and in debug mode and watch for errors:
Code:
/usr/sbin/named -u named -g -d 3 |
Quote:
Thanks Milindra |
All times are GMT -5. The time now is 03:18 PM. |