diff options
Diffstat (limited to 'doc/arm/dnssec.xml')
| -rw-r--r-- | doc/arm/dnssec.xml | 146 |
1 files changed, 73 insertions, 73 deletions
diff --git a/doc/arm/dnssec.xml b/doc/arm/dnssec.xml index 4b058eb8b0e5..467bc725fe8b 100644 --- a/doc/arm/dnssec.xml +++ b/doc/arm/dnssec.xml @@ -1,4 +1,3 @@ -<?xml version="1.0" encoding="utf-8"?> <!-- - Copyright (C) 2010, 2011, 2015 Internet Systems Consortium, Inc. ("ISC") - @@ -15,24 +14,25 @@ - PERFORMANCE OF THIS SOFTWARE. --> -<sect1 id="dnssec.dynamic.zones"> - <title>DNSSEC, Dynamic Zones, and Automatic Signing</title> +<!-- Converted by db4-upgrade version 1.0 --> +<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="dnssec.dynamic.zones"><info><title>DNSSEC, Dynamic Zones, and Automatic Signing</title></info> + <para>As of BIND 9.7.0 it is possible to change a dynamic zone from insecure to signed and back again. A secure zone can use either NSEC or NSEC3 chains.</para> - <sect2> - <title>Converting from insecure to secure</title> - </sect2> + <section><info><title>Converting from insecure to secure</title></info> + + </section> <para>Changing a zone from insecure to secure can be done in two - ways: using a dynamic DNS update, or the + ways: using a dynamic DNS update, or the <command>auto-dnssec</command> zone option.</para> - <para>For either method, you need to configure - <command>named</command> so that it can see the + <para>For either method, you need to configure + <command>named</command> so that it can see the <filename>K*</filename> files which contain the public and private parts of the keys that will be used to sign the zone. These files - will have been generated by + will have been generated by <command>dnssec-keygen</command>. You can do this by placing them - in the key-directory, as specified in + in the key-directory, as specified in <filename>named.conf</filename>:</para> <programlisting> zone example.net { @@ -47,9 +47,9 @@ with the ZSK, and the DNSKEY RRset to be signed with the KSK as well. An NSEC chain will be generated as part of the initial signing process.</para> - <sect2> - <title>Dynamic DNS update method</title> - </sect2> + <section><info><title>Dynamic DNS update method</title></info> + + </section> <para>To insert the keys via dynamic update:</para> <screen> % nsupdate @@ -59,7 +59,7 @@ > send </screen> <para>While the update request will complete almost immediately, - the zone will not be completely signed until + the zone will not be completely signed until <command>named</command> has had time to walk the zone and generate the NSEC and RRSIG records. The NSEC record at the apex will be added last, to signal that there is a complete NSEC @@ -77,27 +77,27 @@ > send </screen> <para>Again, this update request will complete almost - immediately; however, the record won't show up until + immediately; however, the record won't show up until <command>named</command> has had a chance to build/remove the relevant chain. A private type record will be created to record the state of the operation (see below for more details), and will be removed once the operation completes.</para> <para>While the initial signing and NSEC/NSEC3 chain generation is happening, other updates are possible as well.</para> - <sect2> - <title>Fully automatic zone signing</title> - </sect2> - <para>To enable automatic signing, add the - <command>auto-dnssec</command> option to the zone statement in - <filename>named.conf</filename>. - <command>auto-dnssec</command> has two possible arguments: - <constant>allow</constant> or + <section><info><title>Fully automatic zone signing</title></info> + + </section> + <para>To enable automatic signing, add the + <command>auto-dnssec</command> option to the zone statement in + <filename>named.conf</filename>. + <command>auto-dnssec</command> has two possible arguments: + <constant>allow</constant> or <constant>maintain</constant>.</para> - <para>With - <command>auto-dnssec allow</command>, + <para>With + <command>auto-dnssec allow</command>, <command>named</command> can search the key directory for keys matching the zone, insert them into the zone, and use them to - sign the zone. It will do so only when it receives an + sign the zone. It will do so only when it receives an <command>rndc sign <zonename></command>.</para> <para> <!-- TODO: this is repeated in the ARM --> @@ -105,7 +105,7 @@ functionality, but will also automatically adjust the zone's DNSKEY records on schedule according to the keys' timing metadata. (See <xref linkend="man.dnssec-keygen"/> and - <xref linkend="man.dnssec-settime"/> for more information.) + <xref linkend="man.dnssec-settime"/> for more information.) </para> <para> <command>named</command> will periodically search the key directory @@ -119,7 +119,7 @@ </para> <para> If keys are present in the key directory the first time the zone - is loaded, the zone will be signed immediately, without waiting for an + is loaded, the zone will be signed immediately, without waiting for an <command>rndc sign</command> or <command>rndc loadkeys</command> command. (Those commands can still be used when there are unscheduled key changes, however.) @@ -141,16 +141,16 @@ the zone is signed and the NSEC3 chain is completed, the NSEC3PARAM record will appear in the zone. </para> - <para>Using the + <para>Using the <command>auto-dnssec</command> option requires the zone to be - configured to allow dynamic updates, by adding an - <command>allow-update</command> or + configured to allow dynamic updates, by adding an + <command>allow-update</command> or <command>update-policy</command> statement to the zone configuration. If this has not been done, the configuration will fail.</para> - <sect2> - <title>Private-type records</title> - </sect2> + <section><info><title>Private-type records</title></info> + + </section> <para>The state of the signing process is signaled by private-type records (with a default type value of 65534). When signing is complete, these records will have a nonzero value for @@ -186,19 +186,19 @@ 0x20 NONSEC </literallayout> </para> - <sect2> - <title>DNSKEY rollovers</title> - </sect2> + <section><info><title>DNSKEY rollovers</title></info> + + </section> <para>As with insecure-to-secure conversions, rolling DNSSEC - keys can be done in two ways: using a dynamic DNS update, or the + keys can be done in two ways: using a dynamic DNS update, or the <command>auto-dnssec</command> zone option.</para> - <sect2> - <title>Dynamic DNS update method</title> - </sect2> + <section><info><title>Dynamic DNS update method</title></info> + + </section> <para> To perform key rollovers via dynamic update, you need to add - the <filename>K*</filename> files for the new keys so that + the <filename>K*</filename> files for the new keys so that <command>named</command> can find them. You can then add the new - DNSKEY RRs via dynamic update. + DNSKEY RRs via dynamic update. <command>named</command> will then cause the zone to be signed with the new keys. When the signing is complete the private type records will be updated so that the last octet is non @@ -212,15 +212,15 @@ be able to verify at least one signature when you remove the old DNSKEY.</para> <para>The old DNSKEY can be removed via UPDATE. Take care to - specify the correct key. + specify the correct key. <command>named</command> will clean out any signatures generated by the old key after the update completes.</para> - <sect2> - <title>Automatic key rollovers</title> - </sect2> + <section><info><title>Automatic key rollovers</title></info> + + </section> <para>When a new key reaches its activation date (as set by <command>dnssec-keygen</command> or <command>dnssec-settime</command>), - if the <command>auto-dnssec</command> zone option is set to + if the <command>auto-dnssec</command> zone option is set to <constant>maintain</constant>, <command>named</command> will automatically carry out the key rollover. If the key's algorithm has not previously been used to sign the zone, then the zone will @@ -231,64 +231,64 @@ signature validity periods expire. By default, this rollover completes in 30 days, after which it will be safe to remove the old key from the DNSKEY RRset.</para> - <sect2> - <title>NSEC3PARAM rollovers via UPDATE</title> - </sect2> + <section><info><title>NSEC3PARAM rollovers via UPDATE</title></info> + + </section> <para>Add the new NSEC3PARAM record via dynamic update. When the new NSEC3 chain has been generated, the NSEC3PARAM flag field will be zero. At this point you can remove the old NSEC3PARAM record. The old chain will be removed after the update request completes.</para> - <sect2> - <title>Converting from NSEC to NSEC3</title> - </sect2> + <section><info><title>Converting from NSEC to NSEC3</title></info> + + </section> <para>To do this, you just need to add an NSEC3PARAM record. When the conversion is complete, the NSEC chain will have been removed and the NSEC3PARAM record will have a zero flag field. The NSEC3 chain will be generated before the NSEC chain is destroyed.</para> - <sect2> - <title>Converting from NSEC3 to NSEC</title> - </sect2> + <section><info><title>Converting from NSEC3 to NSEC</title></info> + + </section> <para>To do this, use <command>nsupdate</command> to remove all NSEC3PARAM records with a zero flag field. The NSEC chain will be generated before the NSEC3 chain is removed.</para> - <sect2> - <title>Converting from secure to insecure</title> - </sect2> + <section><info><title>Converting from secure to insecure</title></info> + + </section> <para>To convert a signed zone to unsigned using dynamic DNS, delete all the DNSKEY records from the zone apex using <command>nsupdate</command>. All signatures, NSEC or NSEC3 chains, and associated NSEC3PARAM records will be removed automatically. This will take place after the update request completes.</para> - <para> This requires the - <command>dnssec-secure-to-insecure</command> option to be set to - <userinput>yes</userinput> in + <para> This requires the + <command>dnssec-secure-to-insecure</command> option to be set to + <userinput>yes</userinput> in <filename>named.conf</filename>.</para> <para>In addition, if the <command>auto-dnssec maintain</command> zone statement is used, it should be removed or changed to <command>allow</command> instead (or it will re-sign). </para> - <sect2> - <title>Periodic re-signing</title> - </sect2> + <section><info><title>Periodic re-signing</title></info> + + </section> <para>In any secure zone which supports dynamic updates, named will periodically re-sign RRsets which have not been re-signed as a result of some update action. The signature lifetimes will be adjusted so as to spread the re-sign load over time rather than all at once.</para> - <sect2> - <title>NSEC3 and OPTOUT</title> - </sect2> + <section><info><title>NSEC3 and OPTOUT</title></info> + + </section> <para> <command>named</command> only supports creating new NSEC3 chains where all the NSEC3 records in the zone have the same OPTOUT - state. + state. <command>named</command> supports UPDATES to zones where the NSEC3 - records in the chain have mixed OPTOUT state. + records in the chain have mixed OPTOUT state. <command>named</command> does not support changing the OPTOUT state of an individual NSEC3 record, the entire chain needs to be changed if the OPTOUT state of an individual NSEC3 needs to be changed.</para> -</sect1> +</section> |