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/

_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Reply via email to