From owner-freebsd-questions@FreeBSD.ORG Fri Apr 23 12:06:47 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE5CC16A4CE for ; Fri, 23 Apr 2004 12:06:46 -0700 (PDT) Received: from therub.org (pantheon-ws-13.direct.hickorytech.net [216.114.200.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1A4043D1D for ; Fri, 23 Apr 2004 12:06:45 -0700 (PDT) (envelope-from drue@therub.org) Received: from drue by therub.org with local (Exim 3.35 #1 (Debian)) id 1BH60F-0001zm-00; Fri, 23 Apr 2004 14:06:23 -0500 Date: Fri, 23 Apr 2004 14:06:23 -0500 To: Charles Swiger Message-ID: <20040423190623.GA5777@therub.org> Mail-Followup-To: drue@FreeBSD.ORG, Charles Swiger , jammet@swbell.net, freebsd-questions@freebsd.org References: <1082741893.26067.18.camel@Desolation> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i From: Dan Rue cc: jammet@swbell.net cc: freebsd-questions@freebsd.org Subject: Re: Slow loading websites X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Apr 2004 19:06:47 -0000 On Fri, Apr 23, 2004 at 02:13:13PM -0400, Charles Swiger wrote: > On Apr 23, 2004, at 1:38 PM, Jammet wrote: > >When i go to a website, say Slashdot or freshmeat, or any where that > >involves ads on the page some where, about 99% of the time it can take > >upwards of 2-3 minutes to load the entire page. [ ... ] > >I guess my main question is, anyone ever seen this, if so ever get it > >fixed? > > Most probably, you are running into delays because your browser queries > websites for an IPv6 address before trying an IPv4 address. > Reportedly, many ad-sites use broken nameservers which botch IPv6 > queries, causing the delay. The problem lies on their end, not yours, > but disabling IPv6 or using a proxy server like Squid will probably > remove the delays. Most of that is true. However, I found it to be a problem with firefox specifically - in that firefox waits for the 75 second timeout. Forced me to switch to opera :) It looks like it will be fixed in the next version of mozilla, though: http://bugzilla.mozilla.org/show_bug.cgi?id=68796 The quickest workaround is to add ::0 ad.doubleclick.com ::0 ad.doubleclick.net to /etc/hosts (not a bad thing to keep in there, really). hth, dan