Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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
Hi I checked the RNDC configuration but I can't see any problems.
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.
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:
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
ps -ef|grep named
This is the only log I found in related to this in message log
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]#
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:
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
/usr/sbin/named -u named
and look at the logs again?
I ran those commands. I have attached the log file for your information.
Thanks
I ran those commands. I have attached the log file for your information.
Thanks
Actually on 30th I was creating some slave zones on this server.Because we had to use this server as also a secondary name server for the other web server. I can remember I didnt installed anything.
But I deleted all the slave domain because of this error.
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:
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
Hi good morning..
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.