On Fri, 2003-09-26 at 13:36, wgerrard wrote:
suse@sillwood-acre.co.uk wrote:
I found the same problem with Mozilla-family browsers using 8.2. Extensive googling finally turned up
http://bugzilla.mozilla.org/show_bug.cgi?id=70213 and http://bugzilla.mozilla.org/show_bug.cgi?id=135724#c24.
Thanks, that is interesting, especially the second URL. It mirrors my experience, expecially with non-Mozilla browsers.
Appreciate your comment on running squid to cache DNS (I set up bind as a cacheing server), but a cache can only retain addresses that have already been resolved. Any new lookups won't be affected.
The thing that makes me think something else is going on here is the fact that I ran SuSe on my DSL account without these problems showing up. When I switched to cable, the slow DNS was apparent immediately.
I find that using dnscache speeds things a lot. See http://cr.yp.to/djbdns/run-cache.html It's excellent and easy to get up and running. Dee