From owner-freebsd-hackers Sun May 12 13:17: 6 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wartch.sapros.com (rularan.sapros.com [204.182.55.17]) by hub.freebsd.org (Postfix) with ESMTP id D1D4F37B406 for ; Sun, 12 May 2002 13:17:03 -0700 (PDT) Received: from wartch.sapros.com (localhost [127.0.0.1]) by wartch.sapros.com (8.12.3/8.12.3) with ESMTP id g4CKGlUn048082; Sun, 12 May 2002 13:16:47 -0700 (PDT) (envelope-from peterh@wartch.sapros.com) Message-Id: <200205122016.g4CKGlUn048082@wartch.sapros.com> To: Bernd Walter Cc: hackers@freebsd.org Subject: Re: gethostbyname2 and AF_INET6 Date: Sun, 12 May 2002 13:16:47 -0700 From: Peter Haight X-Spam-Status: No, hits=1.8 required=7.0 tests=NO_MX_FOR_FROM version=2.11 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >www.vanguard.com has a broken DNS implementation. >Find out the zone administrator via SOA record or whois and complain. >RFC requires the behavour you saw with google. Ok. The thing is that there are a lot of these sites. Watching the log on the other side of my DNS server it looks like it is sending requests to vanguard's dns server, but not getting any replies. Is there some way I can lower the timeout for IPV6 DNS lookups or maybe disable them? Or is there some change I can make to mozilla to minimize the impact of sites like these? Hmm. Looking at the FreeBSD resolver code, it doesn't look like there is some convenient way to do this. Maybe something like, try the AAAA lookup, but if we don't get any reply in a short timeout, try an A lookup. If we get a reply to that, then log the site as probably not conforming to the RFC. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message