From owner-freebsd-current@FreeBSD.ORG Sun Feb 8 09:06:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77D8F16A4CE for ; Sun, 8 Feb 2004 09:06:16 -0800 (PST) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C41B43D1F for ; Sun, 8 Feb 2004 09:06:15 -0800 (PST) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id B32B55311; Sun, 8 Feb 2004 18:06:13 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id 1A039530D; Sun, 8 Feb 2004 18:06:03 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id 9E2CD33C6F; Sun, 8 Feb 2004 18:06:03 +0100 (CET) To: David Malone References: <20040206144006.GA848@gvr.gvr.org> <20040206150401.GA625@walton.maths.tcd.ie> From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Sun, 08 Feb 2004 18:06:03 +0100 In-Reply-To: <20040206150401.GA625@walton.maths.tcd.ie> (David Malone's message of "Fri, 6 Feb 2004 15:04:01 +0000") Message-ID: User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.63 cc: freebsd-current@freebsd.org Subject: Re: resolver issues: AAAA in ipv4 only environment X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2004 17:06:16 -0000 David Malone writes: > I've done some measurements, and it seems about half a percent of > names and nameservers have some problem answering AAAA queries. > Unfortunately, those names crop up alot, as several ad servers have > problems. However, I think Doubliclick are now actually working > toward fixing their name servers (though more people letting them > know what a pain it is would probably help). Actually, the best solution for DoubleClick is probably to blackhole their IP block and/or add .doubleclick.net to the deny list in your web proxy. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no