DNS conifguration problem!!

[irky_blue_stone]

I consulted some of the threads and configured DNS on my linux machine running Fedora Core 1....
I have made appropriate changes in /etc/resolv.conf and named.conf

Now i start named(BIND) it starts sucessfully
andnow i try "host" for some site say www.yahoo.com
then it shows the following message.....

;;connection timed out;no servers could be reached

I m connected to internet through a LAN.And i am not a proxy server..
please help me

[SilentRage]

What's the contents of your resolv.conf?

[irky_blue_stone]

it has only 1 entry

nameserver 127.0.0.1

Do i need to write something else????

[SilentRage]

No, that is fine. Now show me the results for these commands:

ps -Af | grep 'named'
netstat -an | grep ':53'

[irky_blue_stone]

named 3877 1 0 Apr02 ? 00:00:00 usr/sbin/named -u named -t /var/named/chroot
root 17228 27730 0 01:25 pts/1 00:00:00 grep named

and for netstat -an | grep ':53'

tcp 0 0 192.168.0.30:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:53 0.0.0.0:*
udp 0 0 192.168.0.30:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*


actually i dont want to do zone hosting ...i just want ip adresses of the domain names..

[SilentRage]

I understand that. There is something strange listening on:

udp 0 0 0.0.0.0:53 0.0.0.0:*

Show me the results for this command:

lsof -nPiTCP:53

[irky_blue_stone]

named 3877 named 8u IPv4 3710 TCP 127.0.0.1:53 (LISTEN)
named 3877 named 10u IPv4 3712 TCP 192.168.0.30:53 (LISTEN)

above is the output of the command

[SilentRage]

Oops, should've used UDP. Show me the results for this command:

lsof -nPiUDP:53

[irky_blue_stone]

named 3877 named 6u IPv4 3723 UDP *:53
named 3877 named 7u IPv4 3709 UDP 127.0.0.1:53
named 3877 named 9u IPv4 3711 UDP 192.168.0.30:53

[SilentRage]

Well that's interesting. I've never seen BIND listen on 0.0.0.0:53 before. *shrug* it doesn't matter. Let's test out these connectivity issues you've got.

Show me the results for the following commands:

dig www.google.com
dig www.google.org

I'm testing out a problem that only effects .COM/.NET domains. The above .com might timeout while the .org works.