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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
We have an internal server that was partially set up by someone who knew way too much for his own good. He set it up do cache dns internally and be the soa for all the zones internally. It's become a real problem when updating dns for domains, and it's cached internally. Restarting named doesnt' flush that internal cache for some reason. I'd like to set up bind so it is simply caching, and remove all the zone files, if that's possible. If not , then I'd like to just disable bind completely and go back to how it was before it was set up. How do I go about doing that. If I simply shut off bind, then nothing will resolve internally. We can't access the internet. What config files do I need to modify to fix this.
If you've never configured BIND before, the howto here is useful for getting a basic understanding. Once you have that, you can decide which will be better in your situation. Disabling that instance of BIND and using a different name server is easy enough - do you have another server you can point /etc/resolv.conf to?
Thanks gilead. That link helped out a lot. I am waiting till most folks leave for the day so I don't screw up the internal network, but I think I got it figured out. I simply removed most of the zones from the named.conf file and that should take care of it. From my understanding, whatever isn't specified in a zone, will resort to using one of the other dns servers listed in the resolv.conf. In this case, I am using our isp's dns servers. Once I restart I'll know if it worked Wish me luck.