From owner-freebsd-stable@FreeBSD.ORG Mon Mar 15 23:55:58 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 2BFB016A4D0 for ; Mon, 15 Mar 2004 23:55:58 -0800 (PST) Received: from europa.AD.HartBrothers.Com (europa.ad.hartbrothers.com [63.102.100.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8E1943D4C for ; Mon, 15 Mar 2004 23:55:57 -0800 (PST) (envelope-from davehart@davehart.com) Date: Tue, 16 Mar 2004 07:55:57 -0000 Message-ID: <255A839665EA24408EB27A6AAE15518EAC1B@europa.ad.hartbrothers.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Thread-Topic: ftp.perl.org strangeness Thread-Index: AcQLHKm49LjlaY9VSZKm15NAT36/SgADYY2w From: "Dave Hart" To: "Mark Andrews" , "Rick Knospler" , , 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: Tue, 16 Mar 2004 07:55:58 -0000 I've run across this issue with a few websites in the last 18 months. It might help to ask if they're using a "load balancer" on ddns5.develooper.com (the nameserver for ddns.develooper.com which is the zone containing ftp.cpan.ddns.develooper.com which is CNAMEd from ftp.perl.org). One DNS-based load balancing product exhibited this broken behavior, though I don't know which product it was. When queried for type A or any type, the correct responses are returned, but when querying for AAAA, NXDOMAIN is returned, which is evil because it communicates false information that there are no records of any type at that name. Since IPv6-enabled clients query AAAA before A or any, they tend to trip up 100% of the time. I've not yet heard of a general-purpose DNS server getting this wrong, I assume any such offenders were fixed earlier in the 8 years of AAAA. DNS-based load balancers are on average greener. I ran across this first with a major computer reseller website and complained to their admins. It took many months for them to get the fix from their load-balancing vendor and convince themselves it was safe, but they did eventually correct the fault. ask develooper.com is listed as the contact in the SOA for ddns.develooper.com, hopefully including them on this email will get the ball rolling. Dave Hart davehart@davehart.com