Date: Wed, 4 Dec 2013 10:47:31 +0100 From: Erwin Lansing <erwin@FreeBSD.org> To: freebsd-stable@freebsd.org, stable@freebsd.org Subject: Re: BIND chroot environment in 10-RELEASE...gone? Message-ID: <20131204094730.GX29825@droso.dk> In-Reply-To: <20131203211606.F2E17B100EB@rock.dv.isc.org> References: <529D9CC5.8060709@rancid.berkeley.edu> <529DF7FA.7050207@passap.ru> <529E179D.7030701@rancid.berkeley.edu> <20131203211606.F2E17B100EB@rock.dv.isc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 04, 2013 at 08:16:06AM +1100, Mark Andrews wrote: > > As for 9.9.x ESV it will be support for to at least June 2017, which > is 5+ years from BIND 9.9.0, and 4 years after 9.9.x was announced > as the ESV series with BIND 9.9.3. > > BIND 9.6 went ESV in Mar 2010 and will be EoL in Jan 2014. > > BIND 9.10 in is alpha at the moment. > > BIND 10 is still in development. > Thanks for chiming in Mark. As you can see, there's some confusion about BIND9's lifetime, so getting this straight from the horse's mouth is good. I did a presentation at the recent ICANN meeting about why BIND was removed from base, slides are at http://people.freebsd.org/~erwin/presentations/20131118-ICANN-FreeBSD-DNS.pdf Note that most of the reasons all fall back to reducing code base and complexity, and some of the other bullets all follow from that. It has more to do with how BIND was integrated into FreeBSD than BIND itself and unbound just has the advantage that it does not have an authoritatve part (and key management etc), with associated options and potential security vulnerabilities, and thus hopefully will be easier to maintain in the base system. Erwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131204094730.GX29825>