valheru_m
asked on
Suse Linux box not resolving DNS
I have a suse linux box that doesn't seem to want to resolve DNS, either from the console (ping, etc) or from the services running on it.
BIND is running locally on the box and /etc/resolv.conf is set to 127.0.0.1 for the DNS server. BIND is setup with proper forwarders and other boxes that use this server for DNS resolve just fine. I can also run nslookup and resolve hostnames just fine, it just doesn't work for other things.
/etc/nsswitch.conf has:
services: files dns
hosts: files dns
Appreciate any ideas. Thanks!
BIND is running locally on the box and /etc/resolv.conf is set to 127.0.0.1 for the DNS server. BIND is setup with proper forwarders and other boxes that use this server for DNS resolve just fine. I can also run nslookup and resolve hostnames just fine, it just doesn't work for other things.
/etc/nsswitch.conf has:
services: files dns
hosts: files dns
Appreciate any ideas. Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN -
udp 0 0 127.0.0.1:53 0.0.0.0:* -
Both of those appear in the output of your command.
udp 0 0 127.0.0.1:53 0.0.0.0:* -
Both of those appear in the output of your command.
in options.conf
allow-query { localhost; localnets; };
In my config:
options {
version "unknown";
directory "/zone";
pid-file "";
dump-file "/var/run/named_dump.db";
statistics-file "/var/run/named.stats";
listen-on { 127.0.0.1; 10.0.0.92;};
forwarders { 8.8.8.8; 213.160.128.3; 80.91.160.2; 83.218.227.100; };
recursion no;
allow-query { localhost; localnets; };
};
ASKER
Bah, I need to get more sleep. I just changed the /etc/resolv.conf to the local IP addy instead of 127.0.0.1 and it's working fine now. I'll give ya the points since your suggestion put my train of thought on the right tracks.
thanks for the help!
thanks for the help!
Example:
Open in new window