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

[Paul Howarth]

jim lawrence wrote:
> ok i have had a connection for about 45 minutes No problems.    open a
> new tab, go to a site, and firefox sits there and does nothing.  But
> on the current tab that I'm in, i can browse the page just fine. open
> the terminal and pinged my router ok. tried to ping google  reply of
> unknown host.  Is the google site experiencing problems or is it just
> me?  the page that I'm currently viewing in Linuxquestions.org, and
> can browse that entire site without a problem,  as soon as i try to
> leave it, i get the super long looking up what ever url I try. e.g
> www.google.com   So is DNS messed up?

Looks that way, given that you can still ping external IP addresses by 
address.

> All this is from a Wireless Connection
> 
> /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
> ***********************************
> from the terminal 
> 
> [root at JimsNotebook ~]# ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:40:D0:5E:70:4F
>           UP BROADCAST NOTRAILERS MULTICAST  MTU:1500  Metric:1
>           RX packets:156 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:173 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:65478 (63.9 KiB)  TX bytes:23283 (22.7 KiB)
>           Interrupt:3
> 
> eth1      Link encap:Ethernet  HWaddr 00:0E:35:1F:CE:CF
>           inet addr:192.168.1.52  Bcast:192.168.1.255  Mask:255.255.255.0
>           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:6090 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:3284 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1239436 (1.1 MiB)  TX bytes:279460 (272.9 KiB)
>           Interrupt:11 Base address:0x6000 Memory:e0001000-e0001fff
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:2266 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2266 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1580248 (1.5 MiB)  TX bytes:1580248 (1.5 MiB)
> *******************************************
> [root at JimsNotebook ~]# netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
> 192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth1
> 169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 lo
> 0.0.0.0         192.168.1.49    0.0.0.0         UG        0 0          0 eth1
> 0.0.0.0         0.0.0.0         0.0.0.0         U         0 0          0 eth1
> 
> *****************************************
> 
> [root at JimsNotebook ~]# ping -c4 24.93.1.118
> PING 24.93.1.118 (24.93.1.118) 56(84) bytes of data.
> 64 bytes from 24.93.1.118: icmp_seq=0 ttl=253 time=10.1 ms
> 64 bytes from 24.93.1.118: icmp_seq=1 ttl=253 time=13.2 ms
> 64 bytes from 24.93.1.118: icmp_seq=2 ttl=253 time=48.9 ms
> 64 bytes from 24.93.1.118: icmp_seq=3 ttl=253 time=10.9 ms
> 
> --- 24.93.1.118 ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3003ms
> rtt min/avg/max/mdev = 10.180/20.835/48.955/16.274 ms, pipe 2
> 
> ****************************************
> 
> [root at JimsNotebook ~]# ping -c4 www.yahoo.com
> ping: unknown host www.yahoo.com

At this point it would be useful to try "dig @127.0.0.1 www.yahoo.com" 
to see what response (if any) your local nameserver provides. dig is 
part of the bind-utils package.

If the response is "connection timed out; no servers could be reached", 
the nameserver isn't working.

Paul.