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.
I recently installed dnsmasq on my linux box. Everything seems to be working ok locally--I changed the resolv.conf to show that the loopback address is the nameserver and when I do an nslookup (locally) I get a very quick reply:
UPDATE: I removed dnsmasq and installed BIND instead, just to see if it is an issue with DNSMasq. BIND has the same issue. Local requests (via my terminal window) work fine. Requests from other PCs do not.
So now I am figuring that it is a firewall issue. I've opened port 53 in both directions (from fw to net and from net to fw). Are there other ports which need to be opened?
Does port 53 need to be open to both UDP and TCP requests?
I have been reading a bit more about how DNS works and one site mentioned that the initial request comes in via UDP on port 53 (and then reverts to TCP if the reply is too large for a UDP packet). Is this the case and if so do I need to open port 53 for UDP requests in Shorewall? (Right now it is only configured to allow TCP requests.)