Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am having a problem with Bind9 that I have been working on for some
time, and it's time to ask for help...
I have two systems, one master and one slave (both recent installs), and it is the master that is having the problem. The primary master seems to have no errors, and the zone files seem to get updated (I suspect that the problem started sometime after I last started the bind service).
Upon issuing the command /etc/init.d/bind9 reload, I get the following error:
Reloading 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.
I am fairly sure my config files are correct, but just in case the relevant portions are listed below. I did regenerate the key using rndc-confgen, but it had no effect. I did double check to make sure the key was the same for both servers in the named.conf and rndc.key files. I also checked file permissions.
Any help will be much appreciated. I've done quite a bit of research on the internet, and nothing I've found has helped. The entries listed below are the same on both servers.