Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a local lan DNS server setup that is working properly except for a new machine I'm using. I know for a fact the DNS server is working properly because I have another machine that resolves names fine.
I edited the resolv.conf file to say "nameserver X.X.X.X" where the X's are the IP to the DNS server. When I do a dig on a machine, it sais connection to dns server timed out. But, I can ping the DNS server fine. Is there some configuration I'm missing here?
First, rule out any type of firewall/ipchains/iptables lock-out. From your client, do this:
telnet x.x.x.x 53
If you get:
Trying x.x.x.x...
Connected to dns.foo.com.
..then that rules that out. However, if you cannot connect to port 53 of x.x.x.x (your DNS server) then you're really not getting through.
--
If you ARE getting through, you can't resolve, you need to check your named.conf to make sure that you have it open to do name resolution for that particular client's IP address. It's often a very good idea (not sure if it ships stock) to lock down BIND so that recursive queries aren't performed for outside hosts.
I managed to fix it by using the /usr/sbin/named startup script rather than the /etc/init.d/named one. I had to also use the -u command with the user being named.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.