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@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@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
This is an underlying network issue. Named won't work because the network isn't working.
What's the output of: # ifconfig -a # netstat -rn # rpm -q NetworkManager wireless-tools
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
These are selinux issues but probably unrelated to your problem. In any case, the named.conf generated by NetworkManager explicitly disables rndc, which would probably explain why "service named status" doesn't work - the named initscript uses rndc to get the status.
Paul.
