Preparing for release of version 4.0

[nsc-5.git] / NEWS

diff --git a/NEWS b/NEWS
index a4da74d1d8cde7da478635b12e79e0e7f3e69d28..c5bebcc2f9ecd990db87559c5cff5f38f4324939 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,13 +1,23 @@
-  o  Added FORWARDING macro for generating forward-only zones.
-  o  Added BLACKHOLE macro for blackhole zones as per RFC 6303.
+Version 4.0  [2011-10-22]
+
+  This version brings several incompatible changes with a common
+  goal: instead of generating a full named.conf, produce a fragment
+  which can be included from a parent config file.
+
+  o  BIND_OPTIONS, FORWARD and SLAVE are gone. Just write the
+     options to the parent config file. (If you think it is somewhat
+     inconvenient, ask BIND developers to change the config file
+     parser, so that multiple options { } sections can be specified.)
+  o  Root hints became optional. If you want them, use ROOTHINT().
+
+  Furthermore, several features have been added:
+
+  o  A FORWARDING macro for generating forward-only zones.
+  o  A BLACKHOLE macro for blackhole zones as per RFC 6303.
      Blackhole zones in example cf/domains updated to use this macro.
-  o  Given that BIND does not support combination of options { }
-     sections, we do not generate them any longer -- write the
-     appropriate options to BIND config file and include the part
-     with the list of zones generated by NSC from there. This means
-     that BIND_OPTIONS, FORWARD and SLAVE are gone.
   o  When contents of a zone do not change, the version number is
-     not incremented.
+     not incremented. Unfortunately, BIND tends to produce a warning
+     in such cases, and it be turned off.
 
 Version 3.1  [2008-05-21]