Network Manager Strikes Again!!!!

[Mark Weaver]

Paul Howarth wrote:
> jim lawrence wrote:
> 
>> ok I did the following  [root at JimsNotebook ~]# service named start
>> Starting named:                                            [  OK  ]
>> [root at JimsNotebook ~]# service NetworkManager start
>> Setting network parameters:                                [  OK  ]
>> Starting NetworkManager daemon:                            [  OK  ]
>> [root at JimsNotebook ~]# ping -c4 64.233.161.104
>> connect: Network is unreachable
>> [root at JimsNotebook ~]# service named start
>> [root at JimsNotebook ~]# chkconfig named on
>> [root at JimsNotebook ~]# ping -c4 64.233.161.104
>> PING 64.233.161.104 (64.233.161.104) 56(84) bytes of data.
>> 64 bytes from 64.233.161.104: icmp_seq=0 ttl=242 time=32.1 ms
>> 64 bytes from 64.233.161.104: icmp_seq=1 ttl=242 time=31.8 ms
>> 64 bytes from 64.233.161.104: icmp_seq=2 ttl=242 time=31.0 ms
>> 64 bytes from 64.233.161.104: icmp_seq=3 ttl=242 time=32.5 ms
>>
>> --- 64.233.161.104 ping statistics ---
>> 4 packets transmitted, 4 received, 0% packet loss, time 3002ms
>> rtt min/avg/max/mdev = 31.051/31.910/32.526/0.586 ms, pipe 2
>> [root at JimsNotebook ~]# ping -c4 www.google.com
>> PING www.google.akadns.net (64.233.161.104) 56(84) bytes of data.
>> 64 bytes from 64.233.161.104: icmp_seq=0 ttl=242 time=31.5 ms
>> 64 bytes from 64.233.161.104: icmp_seq=1 ttl=242 time=122 ms
>> 64 bytes from 64.233.161.104: icmp_seq=2 ttl=242 time=30.6 ms
>> 64 bytes from 64.233.161.104: icmp_seq=3 ttl=242 time=32.2 ms
>>
>> --- www.google.akadns.net ping statistics ---
>> 4 packets transmitted, 4 received, 0% packet loss, time 4485ms
>> rtt min/avg/max/mdev = 30.695/54.166/122.090/39.220 ms, pipe
>>
>> /etc/resolv.conf   now
>>
>> ; generated by NetworkManager, do not edit!
>> ; Use a local caching nameserver controlled by NetworkManager
>> search rochester.rr.com
>>
>> nameserver 127.0.0.1
> 
> 
> So it looks like the caching nameserver is not working properly. What's 
> in /etc/named.conf?
> 
> Do you have the bind-chroot package installed? If so, what's in 
> /var/named/chroot/etc/named.conf?
> 
> Paul.
> 

Ok... for a workstation there is no need for a native caching name 
server to be installed or running. I noticed similar ridiculous behavior 
from NetworkManager and ripped the sucker outa there. I have my own DNS 
service running on my gateway machine which supplies all my DNS, which 
NetworkManager was stomping on. Hell! I couldn't even get resolution on 
my LAN's sub-domains until I got rid of NM and reset my resolv.conf file 
so that it was correct.

Uninstall NM and make sure your upstream DNS server IP's are set 
correctly and all will be fine again. O, and uninstall bind cause ya 
really don't need it on a workstation.

-- 
Mark

"If you have found a very wise man, then you've found
a man that at one time was an idiot and lived long enough
to learn from his own stupidity."