Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Not sure what has caused this error on my home linux server but you may have an idea...
I'm running RH 9 with the standard software version for this distro.
I hit some keys on the keyboard while i was moving some stuff over the weekend and managed to lockup the server. I had no choice but to do a manual power off and on again. Linux fixed the file system and continued to boot as normal but failed to start apache. Now i hadnt touced a thing and the knocking of the keys hadnt done something i dont think.
I tried to manually start the service and it still failed etc. i looked in /var/log/httpd/error_log and notcied it couldnt find the IPv4 name for custard and something about a unique id module. After looking about on the net i disabled that module in /etc/httpd/conf/httpd.conf and the service started OK and everything is fine once again.
But if i go to the command prompt and type just 'host custard' i get a 3(NXDOMAIN) error? I never used to... but if i type the fqdn it works fine as normal. I think something has been currupted in bind? but i havent touched a file for ages.
i havent got a 'search' entry in there i dont think. never have before and it worked fine?
what does the search entry do?
Something i should mention is that i just installed a Watchguard Firebox II on the network and maybe the restart cause linux to request some new external info which is now getting blocked? not sure but my FW rules are fine. I'm not blocking anything i can see from this machine. I'm running my own BIND setup.
I cant see how this would be a firewall problem as the server would be doing a lookup against itself...