From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 06:40:08 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 B4D8816A4CE for ; Fri, 6 Feb 2004 06:40:08 -0800 (PST) Received: from gvr.gvr.org (gvr-gw.gvr.org [80.126.103.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1817943D39 for ; Fri, 6 Feb 2004 06:40:07 -0800 (PST) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 654BC50; Fri, 6 Feb 2004 15:40:06 +0100 (CET) Date: Fri, 6 Feb 2004 15:40:06 +0100 From: Guido van Rooij To: freebsd-current@freebsd.org Message-ID: <20040206144006.GA848@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: 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 14:40:08 -0000 It seems there are a lot of broken named's on the Internet that do not answer to AAAA queries. I have a noteboo that sometimes is, and sometimes is not IPv6 connected. However, I do not want to wait too long when on IPv4 only networks. So I would like to eiother have a resolveroption to specify not to ask for AAAA records, or have a smart resolver that figures out that it doesn't need to query AAAA records when only link local IPv6 addresses are found. I do not want to carrie around 2 kernels (one with and the other without ipv6). I'd like to have see some comments on this... -Guido