From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 22:34:07 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 801451065672 for ; Mon, 20 Sep 2010 22:34:07 +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 308338FC1A for ; Mon, 20 Sep 2010 22:34:07 +0000 (UTC) Received: (qmail 1633 invoked by uid 399); 20 Sep 2010 22:34:06 -0000 Received: from localhost (HELO ?192.168.0.142?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 20 Sep 2010 22:34:06 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C97E15D.7070304@FreeBSD.org> Date: Mon, 20 Sep 2010 15:34:05 -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: Mark Kamichoff References: <20100919183721.GA17616@prolixium.com> <20100919185528.GA28845@prolixium.com> In-Reply-To: <20100919185528.GA28845@prolixium.com> 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 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: Mon, 20 Sep 2010 22:34:07 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 9/19/2010 11:55 AM, Mark Kamichoff wrote: | Well, you can safely ignore this! I realized afterwards that | '--disable-ipv6' just disables the default use of IPv6 in BIND, it | doesn't completely disable the protocol. Turns out I was querying the | wrong address with DIG when testing this, too. listen-on-v6 certainly | works as expected, and enables IPv6 like it should. I'm glad to hear that it worked out for you. | Although, that still does beg the question, No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question | why don't we want IPv6 enabled by default on new BIND installations? It has to do with whether or not IPv6 support is compiled into the FreeBSD base system which is compiling BIND. If the configure option is set to enable but there is not the proper support in the base, then Bad Things(TM) happen. However, the way that it is set up now if the binaries are running on a system that has IPv6 support then that is detected, and you can use it if you choose. If the binaries are running on a system without IPv6 support, no harm, no foul. hth, Doug - -- ... 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/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) iQEcBAEBCAAGBQJMl+FdAAoJEFzGhvEaGryEAxkIAIh6hGy0Anfa4DhE55C4Gd/E J/FV2jpfHuDsc6TNPItwIrojSa2Ql+7EHlAo7xOXEka04ydSfA2UBcWQXIz/+LT0 /4+cRtvKdt6O8tB1LHUg20AZ35/MGU9obnREQB2ZLnb1gTVGLN9ZHhRgDC1H8el3 FlC6rWH4raY63cSzU2m4yDKfBRmmcOuVGmJdN8Au9MGo7XlhtW/A101nb6HAUnCP hySDVsCa2t5vhvZiokFmrlL/OzddeD8QQSusEOMOzlieEIKg/OgrfiOkIm4dYi+r 5QLjS0attGqFEA90FemHJmqeFEa+vBNrTCh1XkB0cD2soB/iNd62fWDi1Bu4CY8= =rHnY -----END PGP SIGNATURE-----