BIND8 entering end of life; changes to (affects mirrors)

John Wobus jw354 at
Fri Aug 10 12:34:49 UTC 2007

> There is no pain in moving to Bind9.

No more pain than the usual twinge associated with replacing the  
for a piece of your infrastructure that all your organization's internet
activity depends upon 7x24, with software that has different memory and
CPU needs, that has differences in its configuration rules and  
(e.g. logging channels), that has a different control program (rndc  
versus ndc),
that has modified^H^H^H^H^H^H^H^Hcorrected rules regarding what is
allowed in your your zone files, and has additional restrictions upon  
what it
will cache.


P.S. I'm used to BIND9.  I like BIND9.  I especially like that it is  
more secure.
I suggest anyone making that transition refer to the Top Nine Gotchas: 
With the BIND8 end of life, someone might earn the title of good  
citizen by
updating and amplifying this document.  And if they provided a program  
or script
that pokes around and reliably identifies specific 8-to-9 issues, well,  
they'd be
up for sainthood.

Occasionally someone tells us our DNS server isn't caching some  
Internet name and the issue turns out to be BIND9's restrictions to  
defend against
poisoning.  Based upon the surprise and utter amazement of many DNS  
when the issue is explained to them, I gather that software other than  
BIND9 (e.g.
BIND8?) constitutes a huge portion of the current DNS infrastructure.

More information about the bind-users mailing list