Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
running redhat 8.0 with bind v9 and redhat-config-bind 1.8.1
background: I want to implement a custom configuration for named.conf, specifically the OPTIONS section. I understand that redhat-config-bind will automatically generate named.conf each time I apply changes so I put my custom OPTIONS section in named.custom. I also removed the existing OPTIONS section from named.conf so that named will not get confused by two OPTIONS sections -- one in named.conf and the other in the named.custom.
problem: All works as expected until I apply a change using redhat-config-bind. The result is that the OPTIONS section in named.conf is recreated. This prevents named from loading due to duplicate OPTIONS sections.
question: how can I either
1) prevent redhat-config-bind from recreating the OPTIONS section in named.conf
2) continue to use redhat-config-bind to manage zone records and also be able to implement custom parameters in the OPTIONS section of either named.conf or named.custom.
Perhaps the answer is not to use redhat-config-bind at all since the configurable parameters are so very limited.