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.
Location: Under the bridge where proper engineers walkover
Distribution: Various Linux, Solaris, BSD, Cisco
Posts: 443
Original Poster
Rep:
Quote:
What do you mean by totally down? You aren't running it as a service are you? What does it say when you try a command like the one above?
I don't know maybe I worded it wrong adn I'm really tired aswell now since I've been at this all day plus studying too so sorry if I miss lead you, but it isn't working as bind fails to stop or restart however if I issue the command /etc/init.d/bind9 start it works fine???
When I issue command above output is posted above but for clarity; output of rndc status gives:
Code:
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
I don't know maybe I worded it wrong adn I'm really tired aswell now since I've been at this all day plus studying too so sorry if I miss lead you, but it isn't working as bind fails to stop or restart however if I issue the command /etc/init.d/bind9 start it works fine???
When I issue command above output is posted above but for clarity; output of rndc status gives:
Code:
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
with -V option is above in post!
I don't follow the bit about bind fails to stop or restart but then you say /etc/init.d/bind9 start works. Are you trying to stop it with rndc (which obviously won't work with the error you are getting). Note my manpage says rndc restart isn't implemented yet in any case.
Location: Under the bridge where proper engineers walkover
Distribution: Various Linux, Solaris, BSD, Cisco
Posts: 443
Original Poster
Rep:
Code:
Stopping domain name service...: bindrndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
failed!
Is it just me or does rndc seem tied into bind??
Maybe Debian did it this way I don't know but these are meant to be two seperate things no?
Location: Under the bridge where proper engineers walkover
Distribution: Various Linux, Solaris, BSD, Cisco
Posts: 443
Original Poster
Rep:
Ok now I'm falling asleep at my console so am off to bed, shucks 5:30 in the morning wow ok.
Thanks again for everyones help and I hope that tomorow or well... later will bring better results but please if anyone has any ideas to post and I will try them out with a fresh head!
I just loaded bind9 on a debian install I have. Looks like the init script uses rndc for everything, which pretty much sucks if you havea problem like yours.
I would think that you are going to have to force restart, so kill the running named daemon (using kill) and then /etc/init.d/bind9 start
Location: Under the bridge where proper engineers walkover
Distribution: Various Linux, Solaris, BSD, Cisco
Posts: 443
Original Poster
Rep:
Damn was I whacked this morning; working on DNS all day going round in circles and studying for a Cisco CCNA course all at the same time. My brain cells got fried in the end TTL down to 0 and neural processing time out. hehe
Thanks so much billymayday, maybe a little Debian bug I presume as after running killall -KILL named then restarting its ok now!!!! )
rndc reload works!
So now I just need to make my DNS server authoritive and I guess I will be alright.
Now I guess we can work on the next stage: Authority?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
)
