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

[jim lawrence]

All with wireless active to a ad-hoc network  after reboot ( not right)
> What error message do you get when you ping google.com?
[root at JimsNotebook ~]# ping -c4 www.google.com
ping: unknown host www.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 at JimsNotebook ~]# ping -c4 192.168.1.49
PING 192.168.1.49 (192.168.1.49) 56(84) bytes of data.
>From 169.254.73.88 icmp_seq=1 Destination Host Unreachable
>From 169.254.73.88 icmp_seq=2 Destination Host Unreachable
>From 169.254.73.88 icmp_seq=3 Destination Host Unreachable

and from last night after a reboot   i got these messages    
/var/log/messages
Jan 19 21:35:04 JimsNotebook messagebus: messagebus -TERM succeeded
Jan 19 21:35:04 JimsNotebook dbus: avc:  1 AV entries and 1/512
buckets used, longest chain length 1
Jan 19 21:35:05 JimsNotebook atd: atd shutdown succeeded
Jan 19 21:35:05 JimsNotebook xfs[4153]: terminating 
Jan 19 21:35:05 JimsNotebook xfs: xfs shutdown succeeded
Jan 19 21:35:05 JimsNotebook gpm: gpm shutdown succeeded
Jan 19 21:35:05 JimsNotebook sshd: sshd -TERM succeeded
Jan 19 21:35:05 JimsNotebook smartd[4054]: smartd received signal 15:
Terminated
Jan 19 21:35:05 JimsNotebook smartd[4054]: smartd is exiting (exit status 0) 
Jan 19 21:35:05 JimsNotebook smartd: smartd shutdown succeeded
Jan 19 21:35:06 JimsNotebook kernel: audit(1106188506.273:0): avc: 
denied  { read } for  pid=7204 exe=/usr/sbin/rndc name=hosts dev=hda8
ino=460335 scontext=user_u:system_r:ndc_t
tcontext=system_u:object_r:file_t tclass=file
Jan 19 21:35:06 JimsNotebook kernel: audit(1106188506.300:0): avc: 
denied  { read } for  pid=7209 exe=/usr/sbin/rndc name=hosts dev=hda8
ino=460335 scontext=user_u:system_r:ndc_t
tcontext=system_u:object_r:file_t tclass=file
Jan 19 21:35:06 JimsNotebook xinetd[4107]: Exiting...
Jan 19 21:35:06 JimsNotebook xinetd: xinetd shutdown succeeded



> > &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
> > [root at 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 at 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.


-- 

********************************************************
When I'm feeling down, I like to whistle. 
It makes the neighbor's dog run to the end of his chain and gag himself.
************************************
Registered Linux User: #376813

jim lawrence


> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>