From owner-freebsd-stable@FreeBSD.ORG Tue Mar 16 19:41:51 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A0EF16A4CE; Tue, 16 Mar 2004 19:41:51 -0800 (PST) Received: from europa.AD.HartBrothers.Com (europa.ad.hartbrothers.com [63.102.100.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id D842143D31; Tue, 16 Mar 2004 19:41:50 -0800 (PST) (envelope-from davehart@davehart.com) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 17 Mar 2004 03:41:49 -0000 Content-class: urn:content-classes:message Message-ID: <255A839665EA24408EB27A6AAE15518EAC1D@europa.ad.hartbrothers.com> X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ftp.perl.org strangeness Thread-Index: AcQLtFLgRlaN8zfaQSyP8AR/9SdWbQAHC1LA From: "Dave Hart" To: "Tim Robbins" , Subject: RE: ftp.perl.org strangeness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2004 03:41:51 -0000 > On Tue, Mar 16, 2004 at 09:27:27AM -0500, Louis A. Mamakos wrote: > >=20 > > Wouldn't it be nice to be able to configure the default behavior of=20 > > the resolver to not query AAAA records first, before looking for A=20 > > records? [...] =20 Tim Robbins noted: > This was discussed recently on -current: > = http://marc.theaimsgroup.com/?l=3Dfreebsd-current&m=3D107607971200977&w=3D= 2 That thread might lead one to believe that destination address selection in -CURRENT would give the described behavior, but I'm not so sure. Destination address selection comes into play after you have resolved names to addresses. My guess is even with IPv4 destination addresses preferred in /etc/ip6addrctl.conf the resolver will still query for both AAAA and A records when the client is IPv6-enabled. If the AAAA query comes first and a bork load balancer returns NXDOMAIN, the negative response will likely be cached and result in the subsequent A query failing as well, meaning no IPv4 address to prefer. Dave Hart davehart@davehart.com