Re: Beware of bind-9.2.4-8_FC3:20 (was BIND (Network Manager Strikes Again!!!!))

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



jim lawrence wrote:
i had everything back to the way it way before the update last night. this morning i tried to connect and couldn't. could ping my router
with wireless and wired but not google.com. plugged in my wire and had
to turn off named, and Viola connected. So i'm totally confused as to
wht only 6 hours ago, it works and now it doesn't. so far i tried to
turn named back on and it says it is running i try to turn it off
says its off weird

What error message do you get when you ping google.com?

If it's "host not found" then the DNS lookup has failed but pinging by IP address may still work (e.g. ping 216.239.37.99), in which case your underlying network is still working properly.

&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
[root@JimsNotebook ~]# ps -ef | grep named root      5264     1  0
Jan19 ?        00:00:00 /usr/sbin/named -f -c /tmp/Netwo
rkManager-named.conf-gItjSL
root     12770 12397  0 06:32 pts/1    00:00:00 grep named
[root@JimsNotebook tmp]# gedit NetworkManager-named.conf-gItjSL

// Named configuration, generated by NetworkManager

options {
directory "/"; query-source address * port 53;
forward only;
forwarders { 24.93.1.118; 24.93.1.120; 24.93.1.247; };
listen-on { 127.0.0.1; };
pid-file "/tmp/NetworkManager-named-pid-5dCMlh";
};


// Disable rndc
controls { };
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

This is a very basic named.conf that just forwards queries directly to your regular nameservers, i.e. 24.93.1.118, 24.93.1.120, 24.93.1.247. If named is actually running then it should work very similarly to having those IPs listed as nameserver records in your /etc/resolv.conf


Can you ping those IPs when NM is running?

Can you do lookups using those nameservers directly?

$ dig @24.93.1.118 google.com

Can you do lookups using your own nameserver?

$ dig @127.0.0.1 google.com

With NM running /etc/resolv.conf
; generated by NetworkManager, do not edit!
; Use a local caching nameserver controlled by NetworkManager
search rochester.rr.com


nameserver 127.0.0.1

This makes DNS lookups use your local named.

Paul.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux