Hiya folks - also using Mandy 10 and had no joy with any of the above - I discovered I've got IPv6 DNS lookups happening, which are (eventually) timing out. According to http://weblogs.mozillazine.org/darin...es/005753.html this is turned on in the kernel and setting it off in mozilla doesn't help. ( I was having the same problem in konquerer )

The fix is to add "alias net-pf-10 off" to the end of /etc/modprobe.conf (but only if you don't need IPv6 in your kernel, of course) and reboot.

Disabling it on one interface at a time would be cute, and make the reboot unnecessary, but I don't need IPv6 at all, so I've not gone there.

HopeThisHelpsSomeone.......

ipv6 dns was the culprit
 

Icenov's solution worked for me. I use Mozilla 1.7.3 and the 10-20 seconds that some sites took was bothering me. Google and Yahoo, for instance, were snappy but www.nytimes.com took about 20 seconds. Disabling ipv6 dns lookups in Mozilla, as icenov suggested in this thread, fixed it for Mozilla.

Incidentally, this delay is there in Lynx and is therefore a general problem. I have Suse 9.1 with no wifi network segments.

Thanks icenow.

Problems with "resolving host"
 

I'm using Fedora Core 2 and have installed Firefox. I was running into the exact same problem (even though we have a 1.5Mb fibre optic connection) and every fix I tried didn't work.

However, I recently stumbled over a solution (Network admin isn't really my strong point) which has solved the "resolving host" problem. I swapped the order of the nameserver entries and suddenly it's flying.

Does anyone know why this would have solved the problem. We have a number of Windows machines as well and they have no problems at all. One assumption I have is that one nameserver is more reliable than the other. Would this be correct?

Mozilla slow resolving host
 

icenov's solution worked for me too, on the "Warty Warthog" version Ubuntu 4.10, which comes with "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20041013 Firefox/0.9.3 (Ubuntu)."

Thanks a lot for that.