--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Sep 20, 2010 at 03:34:05PM -0700, Doug Barton wrote:
> | Although, that still does beg the question,
>=20
> No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question
http://en.wikipedia.org/wiki/Beg_the_question#Modern_usage
> | why don't we want IPv6 enabled by default on new BIND installations?
>=20
> 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.
I see, that makes sense. However, as IPv6 becomes more widely used
(perhaps quite far in the future, when folks are turning /off/ IPv4), it
might need revisiting.
- Mark
--=20
Mark Kamichoff
prox@prolixium.com
http://www.prolixium.com/
--J2SCkAp4GZ/dPZZf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkyYmkQACgkQ0TYC9KtF8BOhGQCdGU60cWaLhr3NkoO4I7pt9nBv
Z24AoI2pnSKtoQahlTj6XnHA30y8Wjew
=5SW0
-----END PGP SIGNATURE-----
--J2SCkAp4GZ/dPZZf--