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 am trying to set up a Slackware 10 router for my network. I want this server to act as a DNS server as well. I have installed the BIND package that comes with Slackware and am using the default configuration.
My external interface (eth0) gets DHCP. This sets the nameservers in resolv.conf to 10.141.8.1 and 10.141.8.2 which is correct. If I run dig on the router with these nameservers, it resolves correctly. If I then set resolv.conf to use 127.0.0.1 as my nameserver, it will also resolve correctly.
The problem is that on my internal network I set the DNS server to the internal interface of the router (eth1 - 192.168.1.1). The internal computers cannot resolve.
I have looked around and can't figure out why. Do I have to set up a zone for the internal network? Currently the only zones I have are ".","localhost", and"0.0.127.in-addr.arpa". These are the ones that were in the default configuration for a caching DNS server.
Each of the internal computers gets DHCP from the router which assigns the range 192.168.1.100-192.168.1.254/24 and sets the default gateway and DNS server to the router's internal nic (192.168.1.1) using option routers and option domain-name-servers in dhcpd.conf.
For some reason, it is slightly working now. As long as I leave the router's resolv.conf to have the DNS servers it gets from it's DNS, I can resolve from a non-authoritive server, which means it is working off the external servers. But if I set resolv.conf to use itself and restart BIND, the windows computers cannot resolve and the router can.
At least it is working now, but why would it not work with 127.0.0.1 in resolv.conf?
Tracert, and ping bothwork (I wont show you the output, it doesn't show much, pings are blocked on the network I am testing on, they think it uses too much bandwidth), but nslookup gives an error sometimes. Occasionally it will work, and the rest of the time I get:
C:\Documents and Settings\Administrator>nslookup yahoo.com
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.1: Timed out
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
When it does work I get:
C:\Documents and Settings\Administrator>nslookup yahoo.com
*** Can't find server name for address 192.168.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: yahoo.com
Addresses: 216.109.112.135, 66.94.234.13
What is strange is that there is no way to predict which will occur, one will sometimes, and sometimes its the other.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.