From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 19:24:52 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B69A81065675 for ; Tue, 21 Sep 2010 19:24:52 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 4CF048FC0A for ; Tue, 21 Sep 2010 19:24:52 +0000 (UTC) Received: (qmail 15203 invoked by uid 399); 21 Sep 2010 19:24:51 -0000 Received: from localhost (HELO ?192.168.0.142?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 21 Sep 2010 19:24:51 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C990683.8070302@FreeBSD.org> Date: Tue, 21 Sep 2010 12:24:51 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Kevin Oberman References: <20100921191517.AF60A1CC3D@ptavv.es.net> In-Reply-To: <20100921191517.AF60A1CC3D@ptavv.es.net> X-Enigmail-Version: 1.2a1pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Mark Kamichoff Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Sep 2010 19:24:52 -0000 On 9/21/2010 12:15 PM, Kevin Oberman wrote: > I'd suggest looking at it when IPv6 becomes a standard part of system > software and routing . That will happen long before IPv4 becomes an > exception. I think you missed the bit where I pointed out that the current configuration works in all modern cases, both common and uncommon. The point I tried to humorously make in my previous post was that the current configuration will continue to work until such time as systems are commonly built without any IPv4 at all. BIND does not even have a configuration knob for "no IPv4" atm, nor should it, since it works perfectly well on IPv6-only systems. In short, there is no reason to make a change now, and long before there is any reason to make such a change the underlying software will have changed sufficiently to make the discussion moot. As always, users with special needs beyond what the base BIND provides are welcome to configure to their heart's content either with the port(s) of BIND, or if that's not enough knobs for you you can always build it yourself. hth, Doug PS, pardon the humorless nature of this reply, as attempting to make my point(s) with humor was apparently not very effective. -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/