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.

So, we're switching our main DNS over to a new system. The old one ran RH7.3 and the new one is 9.0. After a bit of twiddling, I decided it was easiest to just type all of the stuff into redhat-config-bind rather than trying to move over the files, given that they're different versions of bind (and redhat-config-bind) and so forth.

I have set the new machine up identically with the old one, as far as I can see. Bind is run -u named (that is, as the user named.) The / and /var directories are readable and executable by everyone, and /var/named is owned by named. All the files in /var/named are owned by named, and are read/write by user and readable by everyone else.

However, when I start up named, I get the following in the log: (Note that the moos and the foos and so forth are for disguising purposes)

Yes, I'm sure that / and /private and /var are all publicly readable and executable, and that named is running as user named.

Now, that would be a solution to my problem, except that every time someone plays with redhat-config-bind, it resets those paths back to the simple filename again, and things stop working again. And we have to play with our name server fairly frequently, and there's more than one of us, and trust me when I say that things are just going to stop working if I use this, so I really want to figure out what's ACTUALLY wrong.

Oh, and no, I'm not using any fancy-schmancy change-of-root settings for this. (Of course, if I were, /etc/named.conf probably wouldn't be found either.)