5 Commits

Author	SHA1	Message	Date
Evan Hunt	79ce3a9e82	3128. [func] Inserting an NSEC3PARAM via dynamic update in an ... auto-dnssec zone that has not been signed yet will cause it to be signed with the specified NSEC3 parameters when keys are activated. The NSEC3PARAM record will not appear in the zone until it is signed, but the parameters will be stored. [RT #23684]	2011-06-10 01:51:09 +00:00
Automatic Updater	c41b2924a5	update copyright notice	2011-02-15 23:47:36 +00:00
Francis Dupont	931814de4a	typo in comment	2011-02-15 18:23:34 +00:00
Automatic Updater	8a07de2f03	update copyright notice	2009-10-09 23:48:09 +00:00
Mark Andrews	d1bcaec0d6	2708. [func] Insecure to secure and NSEC3 parameter changes via ... update are now fully supported and no longer require defines to enable. We now no longer overload the NSEC3PARAM flag field, nor the NSEC OPT bit at the apex. Secure to insecure changes are controlled by by the named.conf option 'secure-to-insecure'. Warning: If you had previously enabled support by adding defines at compile time to BIND 9.6 you should ensure that all changes that are in progress have completed prior to upgrading to BIND 9.7. BIND 9.7 is not backwards compatible.	2009-10-09 00:33:39 +00:00