DHCP - DNS not applying...
 

My /etc/resolv.conf file...

nameserver 127.0.0.1
nameserver 192.168.1.100

192.168.1.100 is my router... 127.0.0.1 is... well, if you don't know that, leave.
Anyway, it takes 15 seconds to resolve a DNS address in a web browser... It takes 0 seconds to ping something...

[kane@localhost kane]$ ping yourmom.com
PING yourmom.com (64.246.50.9) 56(84) bytes of data.
64 bytes from yourmom.com (64.246.50.9): icmp_seq=1 ttl=46 time=73.7 ms
64 bytes from yourmom.com (64.246.50.9): icmp_seq=2 ttl=46 time=70.8 ms
64 bytes from yourmom.com (64.246.50.9): icmp_seq=3 ttl=46 time=84.7 ms
64 bytes from yourmom.com (64.246.50.9): icmp_seq=4 ttl=46 time=71.5 ms

[1]+ Stopped ping yourmom.com
[kane@localhost kane]$

=/

so is your computer(127.0.0.1) an actual nameserver running caching dns or something like it?

run a sniffer and see what happening to the traffic

192.168.1.100 is my router... 127.0.0.1 is... well, if you don't know that, leave.

Not the type of wording I would use if I was hoping to generate replies to my question.

Anyway, it takes 15 seconds to resolve a DNS address in a web browser... It takes 0 seconds to ping something...

Obviously a timeout problem of some sort. I know, duh! Have you verified the following?

1) Is there a DNS server running at 127.0.0.1?
2) If yes, are you posiibly restricting query access? i.e. allow-query?
3) Is there a DNS server running at 192.168.1.100?
4) If yes, are you possibly restricting query access? i.e. allow-query?
5) Are you sure your ping results were not using cached results from previous queries?

6) From the host at 127.0.0.1, does the output of "dig yourmom.com a" show proper name resolution without a timeout?
7) How about the other name server you have specified? i.e. dig @192.168.1.100 yourmom.com a

I know the above questions seem basic, but it might at least help pinpoint whether or not this problem is application specific -or- your systems resolver lib config specific. Also, I would think that a web browser running on the same system is calling the same resolver lib utillites that ping uses. i.e. gethostbyname and gethostbyaddr. But then, I haven't looked at the source code.