From owner-freebsd-ports Sat Mar 22 12:23:25 2003 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF14B37B401 for ; Sat, 22 Mar 2003 12:23:24 -0800 (PST) Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAA0F43FBD for ; Sat, 22 Mar 2003 12:23:23 -0800 (PST) (envelope-from rsidd@online.fr) Received: from user-0cev132.cable.mindspring.com ([24.239.132.98] helo=bluerondo.a.la.turk) by scaup.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18wpWV-0006CN-00 for ports@freebsd.org; Sat, 22 Mar 2003 12:23:23 -0800 Received: (qmail 51360 invoked by uid 1001); 22 Mar 2003 20:23:11 -0000 Date: Sat, 22 Mar 2003 15:23:10 -0500 From: Rahul Siddharthan To: ports@freebsd.org Subject: Native phoenix, konqueror slow in resolving some hostnames Message-ID: <20030322202309.GA51322@online.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I find that two native graphical browsers on my system, phoenix and konqueror, both have problems on some sites -- specifically, sites which reference ad.*.doubleclick.net (I'm not sure whether all such sites are affected). Examples -- http://www.washingtonpost.com/wp-dyn/opinion (the main page seems to work better); http://www.independent.co.uk; http://www.theregister.co.uk (behaviour erratic). These are three sites where I have fairly consistent problems; offhand I can't think of others. While it's trying to resolve ad.doubleclick.net, phoenix is unable to resolve anything else, even sites it can normally resolve immediately. Konqueror has no such problem -- it can resolve something else while waiting on ad.doubleclick.net. In all these cases, with both these browsers, everything comes through after a long gap. Typing nslookup ad.doubleclick.net (or whatever address it's stuck at) on the command line gives me the address immediately, but doesn't affect the browser in any way. Running a dns cache locally (djbdns) doesn't help either. Lynx works fine on all sites, presumably because it doesn't follow those doubleclick.net links. Linux-mozilla also works fine, perhaps because it uses the glibc resolver? Anyway, this is annoying because I like the native browsers better. What can I do to debug this? - Rahul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message