Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
This is really not happening.
I have already set my DNS and now, when i am trying to restart the named service, its throwing the following error.
__________________________-
Stopping named:
named: already running
____________________________
i tried it many a times. Is this what we call stability?
I even tried uninstalling all the named and caching-nameserver rpms and then again installed. that did not work.
I tried stoping xinetd service and restarting that again. That also did not work.
When I tried to do it with GUI , i mean click on services and then stopping the named, then it has thrown this error
------------------------
named failed: the error was: Stopping named:
-------------------------
I want to stop the named service forcibly. How can i do that
I want to manage the named or in that case any service.
Any suggestions will be helpful
Thanks in advance
Locate the process with a "ps auxw | grep named" with it's process ID (PID) in hand, do a "kill -TERM pid#".
To figure out what went boom, check your /var/log/messages (or your syslog setup's equiv.) Also, you can add a " -x" (note the space) to your /etc/init.d/named script's first line... Then you can see in gory detail what's going on when you do a "named stop".
it did not work for me!!!!
service named reload says its not done.
i dont know what the problem is , i tried to reload the rndc key which is the name server utility
tell me what might be the probable reason
Do you have named bound to a port? I'm not familiar with Redhat's /etc/ files but in Slackware you can bind ports to programs in the /etc/inetd.conf file and if 53 is bound to named, it will listen with named and will not let your restart it. Check your inetd.conf << again not sure about filename in Redhat. I'd start there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.