From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 07:20:59 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 32A4F16A4DC for ; Fri, 6 Feb 2004 07:20:59 -0800 (PST) Received: from sarevok.webteckies.org (node123e0.a2000.nl [24.132.35.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E8DA43D73 for ; Fri, 6 Feb 2004 07:20:37 -0800 (PST) (envelope-from mdev@sarevok.webteckies.org) Received: by sarevok.webteckies.org (Postfix, from userid 100) id 3D7CDB91C; Fri, 6 Feb 2004 16:20:36 +0100 (CET) From: Melvyn Sopacua Organization: WebTeckies.org To: current@FreeBSD.org Date: Fri, 6 Feb 2004 16:20:30 +0100 User-Agent: KMail/1.5.94 References: <20040206144006.GA848@gvr.gvr.org> <20040206150401.GA625@walton.maths.tcd.ie> In-Reply-To: <20040206150401.GA625@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_ED7IAppJAl5ZXmK"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402061620.36023.freebsd-current@webteckies.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: Fri, 06 Feb 2004 15:20:59 -0000 --Boundary-02=_ED7IAppJAl5ZXmK Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 06 February 2004 16:04, David Malone wrote: > On Fri, Feb 06, 2004 at 03:40:06PM +0100, Guido van Rooij wrote: > > It seems there are a lot of broken named's on the Internet that do not > > answer to AAAA queries. > > [Not really answering your question, but...] > > 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). Yep, DoubleClick is working on it. They have been testing new loadbalancers= ,=20 since this is the cause. I have no idea what the current status is, but we= =20 (at IDG Netherlands) have a tech-rep coming in this month, so I can stress= =20 the issue once again. If our collegaes at O'Reilly could do the same, it would surely help. I'll= =20 raise the issue within IDG internationally also. =2D-=20 Melvyn =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =46reeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Ja= n 28=20 18:01:18 CET 2004 =20 root@sarevok.lan.webteckies.org:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG = =20 i386 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D --Boundary-02=_ED7IAppJAl5ZXmK Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAI7DEOv9JNmfFN5URAoN3AJ9T2ft0giNenWFUNVIqdTtduB02swCcC3QN uggQuqIpCaoTU2TO6AboU20= =py6F -----END PGP SIGNATURE----- --Boundary-02=_ED7IAppJAl5ZXmK--