Hello,

I'm currently facing with the eternal resolving host delay problem with most browsers if not all.

Mozilla Firefox also doesn't solve the problem of exhaustive delays in resolving host names, most noticably Google.com

I don't understand why this problem occurs on Linux and not on Windows XP, on the same box. Reading previous forum posts regarding this indicate that it's the IPv6 support enabled in the kernel.

And some others point to your router's IP DNS settings, etc.

Well, I use a DLINK router to connect to my cable modem! My router is 192.168.0.1

And my /etc/resolv.conf contained 192.168.0.1 as my DNS servers, agreeable, since that's my gateway.

I also started running named (bind), with the caching configuration only to speed up the process, no luck there.

Ofcourse I did add 127.0.0.1 in my /etc/resolv.conf

reflecting my /etc/resolv.conf to :
127.0.0.1
192.168.0.1

Are these settings incorrect? Do i need to add my internet provider's DNS settings which show up on my router's status page??

Or is it the IPv6 thing ?

You should have your ISP's DNS servers IP in
there ... whether your router passes the requests
on itself or not.

And unless you're actually running your own
bind server you certainly wouldn't want localhost
in rescolv :}


Cheers,
Tink

Ok I changed my resolv.conf to reflect the two ip's my cable service provides on the status page... and 127.0.0.1

since I do run named on my machine. I want it to however cache all requests.

Anyhow, this hasn't stopped the extra oridinary long time you need to wait for name resolution.

Why is this still happening?
Thanks.

In my /etc/resolv.conf I have "nameserver ... ... ..." where ... ... ... is the IP address of my ISP's nameserver. How about leaving out "127.0.0.1"?

Ok .. changed it to the isp's nameservers... i beleive resolv.conf is re-read by the app every time it starts.. still it takes ages... to resolve dns entries.

don't understand what to do.