mirror of
https://github.com/isc-projects/bind9.git
synced 2026-06-12 20:10:01 -04:00
regen v9_10
This commit is contained in:
parent
0f3d3f825f
commit
3edf86ac26
3 changed files with 62 additions and 0 deletions
|
|
@ -49,6 +49,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#root_key">New DNSSEC Root Key</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>
|
||||
|
|
@ -88,6 +89,36 @@
|
|||
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="root_key"></a>New DNSSEC Root Key</h3></div></div></div>
|
||||
<p>
|
||||
ICANN is in the process of introducing a new Key Signing Key (KSK) for
|
||||
the global root zone. BIND has multiple methods for managing DNSSEC
|
||||
trust anchors, with somewhat different behaviors. If the root
|
||||
key is configured using the <span class="command"><strong>managed-keys</strong></span>
|
||||
statement, or if the pre-configured root key is enabled by using
|
||||
<span class="command"><strong>dnssec-validation auto</strong></span>, then BIND can keep
|
||||
keys up to date automatically. Servers configured in this way
|
||||
will roll seamlessly to the new key when it is published in
|
||||
the root zone. However, keys configured using the
|
||||
<span class="command"><strong>trusted-keys</strong></span> statement are not automatically
|
||||
maintained. If your server is performing DNSSEC validation
|
||||
and is configured using <span class="command"><strong>trusted-keys</strong></span>, you are
|
||||
advised to change your configuration before the root zone begins
|
||||
signing with the new KSK. This is currently scheduled for
|
||||
October 11, 2017.
|
||||
</p>
|
||||
<p>
|
||||
This release includes an updated version of the
|
||||
<code class="filename">bind.keys</code> file containing the new root
|
||||
key. This file can also be downloaded from
|
||||
<a class="link" href="https://www.isc.org/bind-keys" target="_top">
|
||||
https://www.isc.org/bind-keys
|
||||
</a>.
|
||||
</p>
|
||||
</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">
|
||||
|
|
|
|||
|
|
@ -244,6 +244,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#root_key">New DNSSEC Root Key</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>
|
||||
|
|
|
|||
|
|
@ -50,6 +50,36 @@
|
|||
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="root_key"></a>New DNSSEC Root Key</h3></div></div></div>
|
||||
<p>
|
||||
ICANN is in the process of introducing a new Key Signing Key (KSK) for
|
||||
the global root zone. BIND has multiple methods for managing DNSSEC
|
||||
trust anchors, with somewhat different behaviors. If the root
|
||||
key is configured using the <span class="command"><strong>managed-keys</strong></span>
|
||||
statement, or if the pre-configured root key is enabled by using
|
||||
<span class="command"><strong>dnssec-validation auto</strong></span>, then BIND can keep
|
||||
keys up to date automatically. Servers configured in this way
|
||||
will roll seamlessly to the new key when it is published in
|
||||
the root zone. However, keys configured using the
|
||||
<span class="command"><strong>trusted-keys</strong></span> statement are not automatically
|
||||
maintained. If your server is performing DNSSEC validation
|
||||
and is configured using <span class="command"><strong>trusted-keys</strong></span>, you are
|
||||
advised to change your configuration before the root zone begins
|
||||
signing with the new KSK. This is currently scheduled for
|
||||
October 11, 2017.
|
||||
</p>
|
||||
<p>
|
||||
This release includes an updated version of the
|
||||
<code class="filename">bind.keys</code> file containing the new root
|
||||
key. This file can also be downloaded from
|
||||
<a class="link" href="https://www.isc.org/bind-keys" target="_top">
|
||||
https://www.isc.org/bind-keys
|
||||
</a>.
|
||||
</p>
|
||||
</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">
|
||||
|
|
|
|||
Loading…
Reference in a new issue