ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

regen master

Browse Source
This commit is contained in:
Tinderbox User
2016-06-28 01:04:44 +00:00
parent aea7ab20c0
commit e95f0bb5c0
3 changed files with 94 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

50
doc/arm/Bv9ARM.ch09.html
View File

@@ -48,6 +48,7 @@
<dd><dl>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_intro">Introduction</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_download">Download</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_license">License Change</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_security">Security Fixes</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_features">New Features</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_changes">Feature Changes</a></span></dt>
@@ -85,6 +86,35 @@
</div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="relnotes_license"></a>License Change</h3></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>
With the release of BIND 9.11.0, ISC is changing the open source
license for BIND from the ISC license to the Mozilla Public License
(MPL 2.0). This change is effective from BIND 9.11.0b1 onwards.
</p>
<p>
The MPL-2.0 license requires that if you make changes to licensed
software (e.g. BIND) and distribute them outside your organization,
that you publish those changes under that same license. It does not
require that you publish or disclose anything other than the changes
you made to our software.
</p>
<p>
This new requirement will not affect anyone who is using BIND
without redistributing it, nor anyone redistributing it without changes,
therefore this change will be without consequence for most individuals
and organizations who are using BIND.
</p>
<p>
Those unsure whether or not the license change affects their use of
BIND, or who wish to discuss how to comply with the license may contact
ISC at <a class="link" href="https://www.isc.org/mission/contact/" target="_top">https://www.isc.org/mission/contact/</a>.
</p>
</li></ul></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="relnotes_security"></a>Security Fixes</h3></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
None.
@@ -116,12 +146,16 @@
mechanism.
</p>
<p>
This feature should be considered experimental. It currently
This feature should be considered experimental. It currently
supports only basic features; more advanced features such as
ACLs and TSIG keys are not yet supported. Example catalog
zone configurations can be found in the Chapter 9 of the
BIND Administrator Reference Manual.
</p>
<p>
Support for master entries with TSIG keys has been added to catalog
zones, as well as support for allow-query and allow-transfer.
</p>
</li>
<li class="listitem"><p>
Added rndc python module.
@@ -208,7 +242,8 @@
<a class="link" href="http://dnstap.info" target="_top">http://dnstap.info</a>.
</p>
</li>
<li class="listitem"><p>
<li class="listitem">
<p>
New statistics counters have been added to track traffic
sizes, as specified in RSSAC002. Query and response
message sizes are broken up into ranges of histogram buckets:
@@ -219,7 +254,12 @@
<a class="link" href="http://localhost:8888/xml/v3/traffic" target="_top">http://localhost:8888/xml/v3/traffic</a>
or
<a class="link" href="http://localhost:8888/json/v1/traffic" target="_top">http://localhost:8888/json/v1/traffic</a>.
</p></li>
</p>
<p>
Statistics for RSSAC02v3 traffic-volume, traffic-sizes and
rcode-volume reporting are now collected.
</p>
</li>
<li class="listitem">
<p>
A new DNSSEC key management utility,
@@ -242,6 +282,10 @@
<span class="command"><strong>dnssec-checkds</strong></span>, have been
refactored and updated as part of this work.
</p>
<p>
<span class="command"><strong>dnssec-keymgr</strong></span> now takes a -r
<span style="color: red">&lt;replacable&gt;randomfile&lt;/replacable&gt;</span> option.
</p>
<p>
(Many thanks to Sebastián
Castro for his assistance in developing this tool at the IETF

1
doc/arm/Bv9ARM.html
View File

@@ -254,6 +254,7 @@
<dd><dl>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_intro">Introduction</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_download">Download</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_license">License Change</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_security">Security Fixes</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_features">New Features</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_changes">Feature Changes</a></span></dt>

49
doc/arm/notes.html
View File

@@ -46,6 +46,35 @@
</div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="relnotes_license"></a>License Change</h3></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>
With the release of BIND 9.11.0, ISC is changing the open source
license for BIND from the ISC license to the Mozilla Public License
(MPL 2.0). This change is effective from BIND 9.11.0b1 onwards.
</p>
<p>
The MPL-2.0 license requires that if you make changes to licensed
software (e.g. BIND) and distribute them outside your organization,
that you publish those changes under that same license. It does not
require that you publish or disclose anything other than the changes
you made to our software.
</p>
<p>
This new requirement will not affect anyone who is using BIND
without redistributing it, nor anyone redistributing it without changes,
therefore this change will be without consequence for most individuals
and organizations who are using BIND.
</p>
<p>
Those unsure whether or not the license change affects their use of
BIND, or who wish to discuss how to comply with the license may contact
ISC at <a class="link" href="https://www.isc.org/mission/contact/" target="_top">https://www.isc.org/mission/contact/</a>.
</p>
</li></ul></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="relnotes_security"></a>Security Fixes</h3></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
None.
@@ -77,12 +106,16 @@
mechanism.
</p>
<p>
This feature should be considered experimental. It currently
This feature should be considered experimental. It currently
supports only basic features; more advanced features such as
ACLs and TSIG keys are not yet supported. Example catalog
zone configurations can be found in the Chapter 9 of the
BIND Administrator Reference Manual.
</p>
<p>
Support for master entries with TSIG keys has been added to catalog
zones, as well as support for allow-query and allow-transfer.
</p>
</li>
<li class="listitem"><p>
Added rndc python module.
@@ -169,7 +202,8 @@
<a class="link" href="http://dnstap.info" target="_top">http://dnstap.info</a>.
</p>
</li>
<li class="listitem"><p>
<li class="listitem">
<p>
New statistics counters have been added to track traffic
sizes, as specified in RSSAC002. Query and response
message sizes are broken up into ranges of histogram buckets:
@@ -180,7 +214,12 @@
<a class="link" href="http://localhost:8888/xml/v3/traffic" target="_top">http://localhost:8888/xml/v3/traffic</a>
or
<a class="link" href="http://localhost:8888/json/v1/traffic" target="_top">http://localhost:8888/json/v1/traffic</a>.
</p></li>
</p>
<p>
Statistics for RSSAC02v3 traffic-volume, traffic-sizes and
rcode-volume reporting are now collected.
</p>
</li>
<li class="listitem">
<p>
A new DNSSEC key management utility,
@@ -203,6 +242,10 @@
<span class="command"><strong>dnssec-checkds</strong></span>, have been
refactored and updated as part of this work.
</p>
<p>
<span class="command"><strong>dnssec-keymgr</strong></span> now takes a -r
<span style="color: red">&lt;replacable&gt;randomfile&lt;/replacable&gt;</span> option.
</p>
<p>
(Many thanks to Sebastián
Castro for his assistance in developing this tool at the IETF