dnssec-signzone.docbook revision 42782931073786f98d3d0a617351db40066949a4
f743002678eb67b99bbc29fee116b65d9530fec0wrowe<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
80833bb9a1bf25dcf19e814438a4b311d2e1f4cffuankg "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
cc5a4a08dc9783fcbc52ce86f11e01c281a43810minfrin [<!ENTITY mdash "&#8212;">]>
249d09d51808cb7981af99762c3b3736ca126cd5jkaluza<!--
249d09d51808cb7981af99762c3b3736ca126cd5jkaluza - Copyright (C) 2004-2009, 2011-2014 Internet Systems Consortium, Inc. ("ISC")
249d09d51808cb7981af99762c3b3736ca126cd5jkaluza - Copyright (C) 2000-2003 Internet Software Consortium.
249d09d51808cb7981af99762c3b3736ca126cd5jkaluza -
56589be3d7a3e9343370df240010c6928cc78b39jkaluza - Permission to use, copy, modify, and/or distribute this software for any
56589be3d7a3e9343370df240010c6928cc78b39jkaluza - purpose with or without fee is hereby granted, provided that the above
56589be3d7a3e9343370df240010c6928cc78b39jkaluza - copyright notice and this permission notice appear in all copies.
8c4967445b49a1612b3f98c1dada65e597ecfe26trawick -
8c4967445b49a1612b3f98c1dada65e597ecfe26trawick - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
8c4967445b49a1612b3f98c1dada65e597ecfe26trawick - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
61fefed8ce5211c31b44f3a38a6e76ca055e5780trawick - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
61fefed8ce5211c31b44f3a38a6e76ca055e5780trawick - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
61fefed8ce5211c31b44f3a38a6e76ca055e5780trawick - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
61fefed8ce5211c31b44f3a38a6e76ca055e5780trawick - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
6001d914962deabb83a46251001612e969bdf67ajim - PERFORMANCE OF THIS SOFTWARE.
6001d914962deabb83a46251001612e969bdf67ajim-->
6001d914962deabb83a46251001612e969bdf67ajim
c4e8006db0cf457c68876d7d4c30dcc451d8cba7jkaluza<refentry id="man.dnssec-signzone">
c4e8006db0cf457c68876d7d4c30dcc451d8cba7jkaluza <refentryinfo>
c4e8006db0cf457c68876d7d4c30dcc451d8cba7jkaluza <date>February 18, 2014</date>
652bacc79dd7f980249784cc8c4838e8f1de7e8acovener </refentryinfo>
652bacc79dd7f980249784cc8c4838e8f1de7e8acovener
652bacc79dd7f980249784cc8c4838e8f1de7e8acovener <refmeta>
652bacc79dd7f980249784cc8c4838e8f1de7e8acovener <refentrytitle><application>dnssec-signzone</application></refentrytitle>
f4db898517ccc6ef1a403630de56918286d3a47eminfrin <manvolnum>8</manvolnum>
f4db898517ccc6ef1a403630de56918286d3a47eminfrin <refmiscinfo>BIND9</refmiscinfo>
f4db898517ccc6ef1a403630de56918286d3a47eminfrin </refmeta>
28a723b775c7666281298eab813c63ac42270f95humbedooh
28a723b775c7666281298eab813c63ac42270f95humbedooh <refnamediv>
28a723b775c7666281298eab813c63ac42270f95humbedooh <refname><application>dnssec-signzone</application></refname>
067698ad30941e38ef5d7f95f1c2736c2ebc5cb9humbedooh <refpurpose>DNSSEC zone signing tool</refpurpose>
067698ad30941e38ef5d7f95f1c2736c2ebc5cb9humbedooh </refnamediv>
067698ad30941e38ef5d7f95f1c2736c2ebc5cb9humbedooh
7a437ce535a5fac890296402ba483c2f41bb6500trawick <docinfo>
7a437ce535a5fac890296402ba483c2f41bb6500trawick <copyright>
7a437ce535a5fac890296402ba483c2f41bb6500trawick <year>2004</year>
d8a6de5eec06d4136839c8f7a56a6ab5acd2d3behumbedooh <year>2005</year>
6e1e45624d6f32110383bb0bd06c254c1dba8123humbedooh <year>2006</year>
77ca16c5676da23155311e13cee61e7eaba9fa3ejailletc <year>2007</year>
77ca16c5676da23155311e13cee61e7eaba9fa3ejailletc <year>2008</year>
77ca16c5676da23155311e13cee61e7eaba9fa3ejailletc <year>2009</year>
77ca16c5676da23155311e13cee61e7eaba9fa3ejailletc <year>2011</year>
921d32d80d8271da08f12fc374a69cb36d1d63b3covener <year>2012</year>
921d32d80d8271da08f12fc374a69cb36d1d63b3covener <year>2013</year>
921d32d80d8271da08f12fc374a69cb36d1d63b3covener <year>2014</year>
3e097af23e40c45aa32602545155f0964ab5c69dcovener <holder>Internet Systems Consortium, Inc. ("ISC")</holder>
3e097af23e40c45aa32602545155f0964ab5c69dcovener </copyright>
3e097af23e40c45aa32602545155f0964ab5c69dcovener <copyright>
faea99bb676ec50ece38da6b1879aa37546483a2covener <year>2000</year>
faea99bb676ec50ece38da6b1879aa37546483a2covener <year>2001</year>
faea99bb676ec50ece38da6b1879aa37546483a2covener <year>2002</year>
86a5604df726638a2b8085e993b4b79c4b3a5262covener <year>2003</year>
faea99bb676ec50ece38da6b1879aa37546483a2covener <holder>Internet Software Consortium.</holder>
344f755169e100ea8ce51e847a0bf30a13b46917covener </copyright>
344f755169e100ea8ce51e847a0bf30a13b46917covener </docinfo>
344f755169e100ea8ce51e847a0bf30a13b46917covener
fcd5c4e9e126e867eb270ed2d4138348cb1e46e5trawick <refsynopsisdiv>
fcd5c4e9e126e867eb270ed2d4138348cb1e46e5trawick <cmdsynopsis>
fcd5c4e9e126e867eb270ed2d4138348cb1e46e5trawick <command>dnssec-signzone</command>
50cfe8bbbaf4279375802531268e2bf0155215fetrawick <arg><option>-a</option></arg>
50cfe8bbbaf4279375802531268e2bf0155215fetrawick <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
50cfe8bbbaf4279375802531268e2bf0155215fetrawick <arg><option>-d <replaceable class="parameter">directory</replaceable></option></arg>
50cfe8bbbaf4279375802531268e2bf0155215fetrawick <arg><option>-D</option></arg>
5cb0075c38fc868730c4981e346845dad6c7ea58chrisd <arg><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
5cb0075c38fc868730c4981e346845dad6c7ea58chrisd <arg><option>-e <replaceable class="parameter">end-time</replaceable></option></arg>
5cb0075c38fc868730c4981e346845dad6c7ea58chrisd <arg><option>-f <replaceable class="parameter">output-file</replaceable></option></arg>
5cb0075c38fc868730c4981e346845dad6c7ea58chrisd <arg><option>-g</option></arg>
ffaa9771884a8664f0e6267efbe9d26b40000461trawick <arg><option>-h</option></arg>
ffaa9771884a8664f0e6267efbe9d26b40000461trawick <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
ffaa9771884a8664f0e6267efbe9d26b40000461trawick <arg><option>-k <replaceable class="parameter">key</replaceable></option></arg>
ffaa9771884a8664f0e6267efbe9d26b40000461trawick <arg><option>-L <replaceable class="parameter">serial</replaceable></option></arg>
f87299dab99bc04b51a6b8cad51b6795db862c0atrawick <arg><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
f87299dab99bc04b51a6b8cad51b6795db862c0atrawick <arg><option>-M <replaceable class="parameter">domain</replaceable></option></arg>
f87299dab99bc04b51a6b8cad51b6795db862c0atrawick <arg><option>-i <replaceable class="parameter">interval</replaceable></option></arg>
4d12805e6c18253040223ea637acd6b3b3c18f60jorton <arg><option>-I <replaceable class="parameter">input-format</replaceable></option></arg>
4d12805e6c18253040223ea637acd6b3b3c18f60jorton <arg><option>-j <replaceable class="parameter">jitter</replaceable></option></arg>
4d12805e6c18253040223ea637acd6b3b3c18f60jorton <arg><option>-N <replaceable class="parameter">soa-serial-format</replaceable></option></arg>
4d12805e6c18253040223ea637acd6b3b3c18f60jorton <arg><option>-o <replaceable class="parameter">origin</replaceable></option></arg>
4d12805e6c18253040223ea637acd6b3b3c18f60jorton <arg><option>-O <replaceable class="parameter">output-format</replaceable></option></arg>
e5d909f2b06bd880fb3675cd49363df981caa631trawick <arg><option>-P</option></arg>
a4df2cd1e1391575a327c2a90ba4315f805a0a78covener <arg><option>-p</option></arg>
a4df2cd1e1391575a327c2a90ba4315f805a0a78covener <arg><option>-R</option></arg>
a4df2cd1e1391575a327c2a90ba4315f805a0a78covener <arg><option>-r <replaceable class="parameter">randomdev</replaceable></option></arg>
cb666b29f81df1d11d65002250153353568021fccovener <arg><option>-S</option></arg>
cb666b29f81df1d11d65002250153353568021fccovener <arg><option>-s <replaceable class="parameter">start-time</replaceable></option></arg>
cb666b29f81df1d11d65002250153353568021fccovener <arg><option>-T <replaceable class="parameter">ttl</replaceable></option></arg>
6a80c3c6f4b8ea7ba5e89402b8b779b09ce020e0covener <arg><option>-t</option></arg>
1c2cab00d988fc48cbe59032cf76cc0bab20d6f7covener <arg><option>-u</option></arg>
6a80c3c6f4b8ea7ba5e89402b8b779b09ce020e0covener <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
75a230a728338d84dcfe81edd375352f34de22d0covener <arg><option>-V</option></arg>
75a230a728338d84dcfe81edd375352f34de22d0covener <arg><option>-X <replaceable class="parameter">extended end-time</replaceable></option></arg>
75a230a728338d84dcfe81edd375352f34de22d0covener <arg><option>-x</option></arg>
1f50dc34ae069adeed20b2986e5ffdefa5c410e0covener <arg><option>-z</option></arg>
1f50dc34ae069adeed20b2986e5ffdefa5c410e0covener <arg><option>-3 <replaceable class="parameter">salt</replaceable></option></arg>
1f50dc34ae069adeed20b2986e5ffdefa5c410e0covener <arg><option>-H <replaceable class="parameter">iterations</replaceable></option></arg>
63a5ea80bddcc84a462e40f402b4f330e0e05411covener <arg><option>-A</option></arg>
63a5ea80bddcc84a462e40f402b4f330e0e05411covener <arg choice="req">zonefile</arg>
63a5ea80bddcc84a462e40f402b4f330e0e05411covener <arg rep="repeat">key</arg>
63a5ea80bddcc84a462e40f402b4f330e0e05411covener </cmdsynopsis>
986f3ea2c314d4d4b3b937149853a0f23f6119aaminfrin </refsynopsisdiv>
986f3ea2c314d4d4b3b937149853a0f23f6119aaminfrin
986f3ea2c314d4d4b3b937149853a0f23f6119aaminfrin <refsect1>
65a4e663b82f8bce28ac22ab2edfd7502de36998sf <title>DESCRIPTION</title>
65a4e663b82f8bce28ac22ab2edfd7502de36998sf <para><command>dnssec-signzone</command>
65a4e663b82f8bce28ac22ab2edfd7502de36998sf signs a zone. It generates
65a4e663b82f8bce28ac22ab2edfd7502de36998sf NSEC and RRSIG records and produces a signed version of the
c7de1955eb0eaeabf7042902476397692672d549sf zone. The security status of delegations from the signed zone
509622419be000045d461ef38fb97df778fdf81djailletc (that is, whether the child zones are secure or not) is
509622419be000045d461ef38fb97df778fdf81djailletc determined by the presence or absence of a
509622419be000045d461ef38fb97df778fdf81djailletc <filename>keyset</filename> file for each child zone.
509622419be000045d461ef38fb97df778fdf81djailletc </para>
0b9de55d178312ec929dbe417dd61199b269991djailletc </refsect1>
0b9de55d178312ec929dbe417dd61199b269991djailletc
0b9de55d178312ec929dbe417dd61199b269991djailletc <refsect1>
0b9de55d178312ec929dbe417dd61199b269991djailletc <title>OPTIONS</title>
74e7f6c55fd67b10cb400b3f6d1dc718a303d944minfrin
74e7f6c55fd67b10cb400b3f6d1dc718a303d944minfrin <variablelist>
74e7f6c55fd67b10cb400b3f6d1dc718a303d944minfrin <varlistentry>
74e7f6c55fd67b10cb400b3f6d1dc718a303d944minfrin <term>-a</term>
a511a29faf2ff7ead3b67680154a624effb31aafminfrin <listitem>
a511a29faf2ff7ead3b67680154a624effb31aafminfrin <para>
a511a29faf2ff7ead3b67680154a624effb31aafminfrin Verify all generated signatures.
a511a29faf2ff7ead3b67680154a624effb31aafminfrin </para>
a511a29faf2ff7ead3b67680154a624effb31aafminfrin </listitem>
63921358ef93fcb41bc71d9894221ba3d7fbb87bminfrin </varlistentry>
63921358ef93fcb41bc71d9894221ba3d7fbb87bminfrin
63921358ef93fcb41bc71d9894221ba3d7fbb87bminfrin <varlistentry>
deec48c67d4786bc77112ffbf3a4e70b931097edminfrin <term>-c <replaceable class="parameter">class</replaceable></term>
6d601599d3d65df0410eae6e573e75b2dbfb1fb4minfrin <listitem>
6d601599d3d65df0410eae6e573e75b2dbfb1fb4minfrin <para>
6d601599d3d65df0410eae6e573e75b2dbfb1fb4minfrin Specifies the DNS class of the zone.
6d601599d3d65df0410eae6e573e75b2dbfb1fb4minfrin </para>
4c02bab56a528a180bbe394d8b6e6fd9c1a3ac1esf </listitem>
4c02bab56a528a180bbe394d8b6e6fd9c1a3ac1esf </varlistentry>
4c02bab56a528a180bbe394d8b6e6fd9c1a3ac1esf
4c02bab56a528a180bbe394d8b6e6fd9c1a3ac1esf <varlistentry>
2c487ac43b583db869e743772a7a10b278aa2bcfminfrin <term>-C</term>
684e0cfc200f66287a93bbd1708d1dd8a92a7eefcovener <listitem>
684e0cfc200f66287a93bbd1708d1dd8a92a7eefcovener <para>
5c43d2fb853f84497b5ece2d414ef9484aa87e5fsf Compatibility mode: Generate a
05a5a9c3e16f21566e1b61f4bd68025ce1b741ccjoes <filename>keyset-<replaceable>zonename</replaceable></filename>
05a5a9c3e16f21566e1b61f4bd68025ce1b741ccjoes file in addition to
ef82e8fa164e0a1f8b813f7deb6b7ead96018c94niq <filename>dsset-<replaceable>zonename</replaceable></filename>
26c5829347f6a355c00f1ba0301d575056b69536niq when signing a zone, for use by older versions of
ef82e8fa164e0a1f8b813f7deb6b7ead96018c94niq <command>dnssec-signzone</command>.
ef82e8fa164e0a1f8b813f7deb6b7ead96018c94niq </para>
ef82e8fa164e0a1f8b813f7deb6b7ead96018c94niq </listitem>
ef82e8fa164e0a1f8b813f7deb6b7ead96018c94niq </varlistentry>
ef82e8fa164e0a1f8b813f7deb6b7ead96018c94niq
ef82e8fa164e0a1f8b813f7deb6b7ead96018c94niq <varlistentry>
413ee814748f37be168ff12407fa6dba0ceeabe6trawick <term>-d <replaceable class="parameter">directory</replaceable></term>
c12917da693bae4028a1d5a5e8224bceed8c739dsf <listitem>
c12917da693bae4028a1d5a5e8224bceed8c739dsf <para>
eafcc0ebf263d0ba69855b6e10958c4c1a2361bdsf Look for <filename>dsset-</filename> or
eafcc0ebf263d0ba69855b6e10958c4c1a2361bdsf <filename>keyset-</filename> files in <option>directory</option>.
eafcc0ebf263d0ba69855b6e10958c4c1a2361bdsf </para>
eafcc0ebf263d0ba69855b6e10958c4c1a2361bdsf </listitem>
eafcc0ebf263d0ba69855b6e10958c4c1a2361bdsf </varlistentry>
d7ffd2da16d58b1a0de212e4d56f7aebb72bef26sf
d7ffd2da16d58b1a0de212e4d56f7aebb72bef26sf <varlistentry>
d7ffd2da16d58b1a0de212e4d56f7aebb72bef26sf <term>-D</term>
4576c1a9ef54cd1e5555ee07d016a7f559f80338sf <listitem>
4576c1a9ef54cd1e5555ee07d016a7f559f80338sf <para>
4576c1a9ef54cd1e5555ee07d016a7f559f80338sf Output only those record types automatically managed by
9811aed12bbc71783d2e544ccb5fecd193843eadsf <command>dnssec-signzone</command>, i.e. RRSIG, NSEC,
9811aed12bbc71783d2e544ccb5fecd193843eadsf NSEC3 and NSEC3PARAM records. If smart signing
9811aed12bbc71783d2e544ccb5fecd193843eadsf (<option>-S</option>) is used, DNSKEY records are also
1366443dc565c33e7b449ae428bbfc4c86f33935drh included. The resulting file can be included in the original
1366443dc565c33e7b449ae428bbfc4c86f33935drh zone file with <command>$INCLUDE</command>. This option
88fac54d9d64f85bbdab5d7010816f4377f95bd7rjung cannot be combined with <option>-O raw</option>,
88fac54d9d64f85bbdab5d7010816f4377f95bd7rjung <option>-O map</option>, or serial number updating.
bd3f5647b96d378d9c75c954e3f13582af32c643sf </para>
bd3f5647b96d378d9c75c954e3f13582af32c643sf </listitem>
bd3f5647b96d378d9c75c954e3f13582af32c643sf </varlistentry>
bd3f5647b96d378d9c75c954e3f13582af32c643sf
bd3f5647b96d378d9c75c954e3f13582af32c643sf <varlistentry>
2a7beea91d46beb41f043a84eaad060047ee04aafabien <term>-E <replaceable class="parameter">engine</replaceable></term>
2a7beea91d46beb41f043a84eaad060047ee04aafabien <listitem>
2a7beea91d46beb41f043a84eaad060047ee04aafabien <para>
2a7beea91d46beb41f043a84eaad060047ee04aafabien When applicable, specifies the hardware to use for
584a85dd4047e38d3ed3a29b6662fcc9d100ae4csf cryptographic operations, such as a secure key store used
584a85dd4047e38d3ed3a29b6662fcc9d100ae4csf for signing.
584a85dd4047e38d3ed3a29b6662fcc9d100ae4csf </para>
f21e9e3d0bfb7a507ecc5bc963f2159d693503d1sf <para>
f21e9e3d0bfb7a507ecc5bc963f2159d693503d1sf When BIND is built with OpenSSL PKCS#11 support, this defaults
f21e9e3d0bfb7a507ecc5bc963f2159d693503d1sf to the string "pkcs11", which identifies an OpenSSL engine
f6b9c755a0b793e8a3a3aebd327ca20a86478117sf that can drive a cryptographic accelerator or hardware service
f6b9c755a0b793e8a3a3aebd327ca20a86478117sf module. When BIND is built with native PKCS#11 cryptography
f6b9c755a0b793e8a3a3aebd327ca20a86478117sf (--enable-native-pkcs11), it defaults to the path of the PKCS#11
132ee6ac1c26d6e8953836316ba50734eefab47bsf provider library specified via "--with-pkcs11".
132ee6ac1c26d6e8953836316ba50734eefab47bsf </para>
132ee6ac1c26d6e8953836316ba50734eefab47bsf </listitem>
85eacfc96a04547ef25aabbc06440039715084c2jorton </varlistentry>
85eacfc96a04547ef25aabbc06440039715084c2jorton
85eacfc96a04547ef25aabbc06440039715084c2jorton <varlistentry>
536d2e7cd1fdec1255b8c3bdf41fdc714c506a54trawick <term>-g</term>
536d2e7cd1fdec1255b8c3bdf41fdc714c506a54trawick <listitem>
536d2e7cd1fdec1255b8c3bdf41fdc714c506a54trawick <para>
536d2e7cd1fdec1255b8c3bdf41fdc714c506a54trawick Generate DS records for child zones from
70caa242e6b90e0d6f0fabb56b8c5c2fb51717b3jorton <filename>dsset-</filename> or <filename>keyset-</filename>
985a4368b93c3e9171a57897ad9454c8dbf4cdf6jorton file. Existing DS records will be removed.
70caa242e6b90e0d6f0fabb56b8c5c2fb51717b3jorton </para>
70caa242e6b90e0d6f0fabb56b8c5c2fb51717b3jorton </listitem>
79c5787b92ac5f0e1cc82393816c77a006399316trawick </varlistentry>
79c5787b92ac5f0e1cc82393816c77a006399316trawick
79c5787b92ac5f0e1cc82393816c77a006399316trawick <varlistentry>
79c5787b92ac5f0e1cc82393816c77a006399316trawick <term>-K <replaceable class="parameter">directory</replaceable></term>
c967bf3bc89e8aa60dbd30d9da388e448ddc1cc4trawick <listitem>
79c5787b92ac5f0e1cc82393816c77a006399316trawick <para>
79c5787b92ac5f0e1cc82393816c77a006399316trawick Key repository: Specify a directory to search for DNSSEC keys.
79c5787b92ac5f0e1cc82393816c77a006399316trawick If not specified, defaults to the current directory.
79c5787b92ac5f0e1cc82393816c77a006399316trawick </para>
79c5787b92ac5f0e1cc82393816c77a006399316trawick </listitem>
7b395e4e878c28a4784919cfd2e704ddd14a3390jorton </varlistentry>
7b395e4e878c28a4784919cfd2e704ddd14a3390jorton
7b395e4e878c28a4784919cfd2e704ddd14a3390jorton <varlistentry>
7b395e4e878c28a4784919cfd2e704ddd14a3390jorton <term>-k <replaceable class="parameter">key</replaceable></term>
536e48c08d674acac5d44929318f2ad928edc361jorton <listitem>
536e48c08d674acac5d44929318f2ad928edc361jorton <para>
e81785da447b469da66f218b3f0244aab507958djorton Treat specified key as a key signing key ignoring any
e81785da447b469da66f218b3f0244aab507958djorton key flags. This option may be specified multiple times.
3e4e54d4e3fc0123c63d57aa84ac7ad7a8c73ff8jorton </para>
3e4e54d4e3fc0123c63d57aa84ac7ad7a8c73ff8jorton </listitem>
3e4e54d4e3fc0123c63d57aa84ac7ad7a8c73ff8jorton </varlistentry>
53e9b27aba029b18be814df40bcf6f0428771d1efuankg
53e9b27aba029b18be814df40bcf6f0428771d1efuankg <varlistentry>
53e9b27aba029b18be814df40bcf6f0428771d1efuankg <term>-l <replaceable class="parameter">domain</replaceable></term>
53e9b27aba029b18be814df40bcf6f0428771d1efuankg <listitem>
53e9b27aba029b18be814df40bcf6f0428771d1efuankg <para>
6bb524f1895f30265a1431afc460977d391cb36bsf Generate a DLV set in addition to the key (DNSKEY) and DS sets.
6bb524f1895f30265a1431afc460977d391cb36bsf The domain is appended to the name of the records.
ca61ccd0c306c2c72df153688ba1b49f3eceed80sf </para>
6bb524f1895f30265a1431afc460977d391cb36bsf </listitem>
e6dd71992459d05a676b98b7963423dc5dc1e24aminfrin </varlistentry>
e6dd71992459d05a676b98b7963423dc5dc1e24aminfrin
e6dd71992459d05a676b98b7963423dc5dc1e24aminfrin <varlistentry>
e6dd71992459d05a676b98b7963423dc5dc1e24aminfrin <term>-M <replaceable class="parameter">maxttl</replaceable></term>
23f1535d6a60817d2846bac0aea230ea475d7dccminfrin <listitem>
23f1535d6a60817d2846bac0aea230ea475d7dccminfrin <para>
23f1535d6a60817d2846bac0aea230ea475d7dccminfrin Sets the maximum TTL for the signed zone.
23f1535d6a60817d2846bac0aea230ea475d7dccminfrin Any TTL higher than <replaceable>maxttl</replaceable> in the
ec7520b24cd80d34d82bbcaca153cbb23cc04bc0rjung input zone will be reduced to <replaceable>maxttl</replaceable>
ec7520b24cd80d34d82bbcaca153cbb23cc04bc0rjung in the output. This provides certainty as to the largest
ec7520b24cd80d34d82bbcaca153cbb23cc04bc0rjung possible TTL in the signed zone, which is useful to know when
ec7520b24cd80d34d82bbcaca153cbb23cc04bc0rjung rolling keys because it is the longest possible time before
ec7520b24cd80d34d82bbcaca153cbb23cc04bc0rjung signatures that have been retrieved by resolvers will expire
ec7520b24cd80d34d82bbcaca153cbb23cc04bc0rjung from resolver caches. Zones that are signed with this
ec7520b24cd80d34d82bbcaca153cbb23cc04bc0rjung option should be configured to use a matching
ec7520b24cd80d34d82bbcaca153cbb23cc04bc0rjung <option>max-zone-ttl</option> in <filename>named.conf</filename>.
6249dfa569d3b4f1f539665b979a80c6e335d93etrawick (Note: This option is incompatible with <option>-D</option>,
6249dfa569d3b4f1f539665b979a80c6e335d93etrawick because it modifies non-DNSSEC data in the output zone.)
0827cb14e550f6f65018431c22c2c913631c8f25kbrand </para>
6249dfa569d3b4f1f539665b979a80c6e335d93etrawick </listitem>
ae600ca541efc686b34f8b1f21bd3d0741d37674covener </varlistentry>
6249dfa569d3b4f1f539665b979a80c6e335d93etrawick
cfa64348224b66dd1c9979b809406c4d15b1c137fielding <varlistentry>
74499a117b3b2cd9666715a14f90c0e5d1a4ee8ajim <term>-s <replaceable class="parameter">start-time</replaceable></term>
cfa64348224b66dd1c9979b809406c4d15b1c137fielding <listitem>
74499a117b3b2cd9666715a14f90c0e5d1a4ee8ajim <para>
cfa64348224b66dd1c9979b809406c4d15b1c137fielding Specify the date and time when the generated RRSIG records
74499a117b3b2cd9666715a14f90c0e5d1a4ee8ajim become valid. This can be either an absolute or relative
cfa64348224b66dd1c9979b809406c4d15b1c137fielding time. An absolute start time is indicated by a number
74499a117b3b2cd9666715a14f90c0e5d1a4ee8ajim in YYYYMMDDHHMMSS notation; 20000530144500 denotes
cfa64348224b66dd1c9979b809406c4d15b1c137fielding 14:45:00 UTC on May 30th, 2000. A relative start time is
indicated by +N, which is N seconds from the current time.
If no <option>start-time</option> is specified, the current
time minus 1 hour (to allow for clock skew) is used.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-e <replaceable class="parameter">end-time</replaceable></term>
<listitem>
<para>
Specify the date and time when the generated RRSIG records
expire. As with <option>start-time</option>, an absolute
time is indicated in YYYYMMDDHHMMSS notation. A time relative
to the start time is indicated with +N, which is N seconds from
the start time. A time relative to the current time is
indicated with now+N. If no <option>end-time</option> is
specified, 30 days from the start time is used as a default.
<option>end-time</option> must be later than
<option>start-time</option>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-X <replaceable class="parameter">extended end-time</replaceable></term>
<listitem>
<para>
Specify the date and time when the generated RRSIG records
for the DNSKEY RRset will expire. This is to be used in cases
when the DNSKEY signatures need to persist longer than
signatures on other records; e.g., when the private component
of the KSK is kept offline and the KSK signature is to be
refreshed manually.
</para>
<para>
As with <option>start-time</option>, an absolute
time is indicated in YYYYMMDDHHMMSS notation. A time relative
to the start time is indicated with +N, which is N seconds from
the start time. A time relative to the current time is
indicated with now+N. If no <option>extended end-time</option> is
specified, the value of <option>end-time</option> is used as
the default. (<option>end-time</option>, in turn, defaults to
30 days from the start time.) <option>extended end-time</option>
must be later than <option>start-time</option>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-f <replaceable class="parameter">output-file</replaceable></term>
<listitem>
<para>
The name of the output file containing the signed zone. The
default is to append <filename>.signed</filename> to
the input filename. If <option>output-file</option> is
set to <literal>"-"</literal>, then the signed zone is
written to the standard output, with a default output
format of "full".
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-h</term>
<listitem>
<para>
Prints a short summary of the options and arguments to
<command>dnssec-signzone</command>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-V</term>
<listitem>
<para>
Prints version information.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-i <replaceable class="parameter">interval</replaceable></term>
<listitem>
<para>
When a previously-signed zone is passed as input, records
may be resigned. The <option>interval</option> option
specifies the cycle interval as an offset from the current
time (in seconds). If a RRSIG record expires after the
cycle interval, it is retained. Otherwise, it is considered
to be expiring soon, and it will be replaced.
</para>
<para>
The default cycle interval is one quarter of the difference
between the signature end and start times. So if neither
<option>end-time</option> or <option>start-time</option>
are specified, <command>dnssec-signzone</command>
generates
signatures that are valid for 30 days, with a cycle
interval of 7.5 days. Therefore, if any existing RRSIG records
are due to expire in less than 7.5 days, they would be
replaced.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-I <replaceable class="parameter">input-format</replaceable></term>
<listitem>
<para>
The format of the input zone file.
Possible formats are <command>"text"</command> (default),
<command>"raw"</command>, and <command>"map"</command>.
This option is primarily intended to be used for dynamic
signed zones so that the dumped zone file in a non-text
format containing updates can be signed directly.
The use of this option does not make much sense for
non-dynamic zones.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-j <replaceable class="parameter">jitter</replaceable></term>
<listitem>
<para>
When signing a zone with a fixed signature lifetime, all
RRSIG records issued at the time of signing expires
simultaneously. If the zone is incrementally signed, i.e.
a previously-signed zone is passed as input to the signer,
all expired signatures have to be regenerated at about the
same time. The <option>jitter</option> option specifies a
jitter window that will be used to randomize the signature
expire time, thus spreading incremental signature
regeneration over time.
</para>
<para>
Signature lifetime jitter also to some extent benefits
validators and servers by spreading out cache expiration,
i.e. if large numbers of RRSIGs don't expire at the same time
from all caches there will be less congestion than if all
validators need to refetch at mostly the same time.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-L <replaceable class="parameter">serial</replaceable></term>
<listitem>
<para>
When writing a signed zone to "raw" or "map" format, set the
"source serial" value in the header to the specified serial
number. (This is expected to be used primarily for testing
purposes.)
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-n <replaceable class="parameter">ncpus</replaceable></term>
<listitem>
<para>
Specifies the number of threads to use. By default, one
thread is started for each detected CPU.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-N <replaceable class="parameter">soa-serial-format</replaceable></term>
<listitem>
<para>
The SOA serial number format of the signed zone.
Possible formats are <command>"keep"</command> (default),
<command>"increment"</command>, <command>"unixtime"</command>,
and <command>"date"</command>.
</para>
<variablelist>
<varlistentry>
<term><command>"keep"</command></term>
<listitem>
<para>Do not modify the SOA serial number.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>"increment"</command></term>
<listitem>
<para>Increment the SOA serial number using RFC 1982
arithmetics.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>"unixtime"</command></term>
<listitem>
<para>Set the SOA serial number to the number of seconds
since epoch.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>"date"</command></term>
<listitem>
<para>Set the SOA serial number to today's date in
YYYYMMDDNN format.</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term>-o <replaceable class="parameter">origin</replaceable></term>
<listitem>
<para>
The zone origin. If not specified, the name of the zone file
is assumed to be the origin.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-O <replaceable class="parameter">output-format</replaceable></term>
<listitem>
<para>
The format of the output file containing the signed zone.
Possible formats are <command>"text"</command> (default),
which is the standard textual representation of the zone;
<command>"full"</command>, which is text output in a
format suitable for processing by external scripts;
and <command>"map"</command>, <command>"raw"</command>,
and <command>"raw=N"</command>, which store the zone in
binary formats for rapid loading by <command>named</command>.
<command>"raw=N"</command> specifies the format version of
the raw zone file: if N is 0, the raw file can be read by
any version of <command>named</command>; if N is 1, the file
can be read by release 9.9.0 or higher; the default is 1.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-p</term>
<listitem>
<para>
Use pseudo-random data when signing the zone. This is faster,
but less secure, than using real random data. This option
may be useful when signing large zones or when the entropy
source is limited.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-P</term>
<listitem>
<para>
Disable post sign verification tests.
</para>
<para>
The post sign verification test ensures that for each algorithm
in use there is at least one non revoked self signed KSK key,
that all revoked KSK keys are self signed, and that all records
in the zone are signed by the algorithm.
This option skips these tests.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-Q</term>
<listitem>
<para>
Remove signatures from keys that are no longer active.
</para>
<para>
Normally, when a previously-signed zone is passed as input
to the signer, and a DNSKEY record has been removed and
replaced with a new one, signatures from the old key
that are still within their validity period are retained.
This allows the zone to continue to validate with cached
copies of the old DNSKEY RRset. The <option>-Q</option>
forces <command>dnssec-signzone</command> to remove
signatures from keys that are no longer active. This
enables ZSK rollover using the procedure described in
RFC 4641, section 4.2.1.1 ("Pre-Publish Key Rollover").
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-R</term>
<listitem>
<para>
Remove signatures from keys that are no longer published.
</para>
<para>
This option is similar to <option>-Q</option>, except it
forces <command>dnssec-signzone</command> to signatures from
keys that are no longer published. This enables ZSK rollover
using the procedure described in RFC 4641, section 4.2.1.2
("Double Signature Zone Signing Key Rollover").
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-r <replaceable class="parameter">randomdev</replaceable></term>
<listitem>
<para>
Specifies the source of randomness. If the operating
system does not provide a <filename>/dev/random</filename>
or equivalent device, the default source of randomness
is keyboard input. <filename>randomdev</filename>
specifies
the name of a character device or file containing random
data to be used instead of the default. The special value
<filename>keyboard</filename> indicates that keyboard
input should be used.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-S</term>
<listitem>
<para>
Smart signing: Instructs <command>dnssec-signzone</command> to
search the key repository for keys that match the zone being
signed, and to include them in the zone if appropriate.
</para>
<para>
When a key is found, its timing metadata is examined to
determine how it should be used, according to the following
rules. Each successive rule takes priority over the prior
ones:
</para>
<variablelist>
<varlistentry>
<listitem>
<para>
If no timing metadata has been set for the key, the key is
published in the zone and used to sign the zone.
</para>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>
If the key's publication date is set and is in the past, the
key is published in the zone.
</para>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>
If the key's activation date is set and in the past, the
key is published (regardless of publication date) and
used to sign the zone.
</para>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>
If the key's revocation date is set and in the past, and the
key is published, then the key is revoked, and the revoked key
is used to sign the zone.
</para>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>
If either of the key's unpublication or deletion dates are set
and in the past, the key is NOT published or used to sign the
zone, regardless of any other metadata.
</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term>-T <replaceable class="parameter">ttl</replaceable></term>
<listitem>
<para>
Specifies a TTL to be used for new DNSKEY records imported
into the zone from the key repository. If not
specified, the default is the TTL value from the zone's SOA
record. This option is ignored when signing without
<option>-S</option>, since DNSKEY records are not imported
from the key repository in that case. It is also ignored if
there are any pre-existing DNSKEY records at the zone apex,
in which case new records' TTL values will be set to match
them, or if any of the imported DNSKEY records had a default
TTL value. In the event of a a conflict between TTL values in
imported keys, the shortest one is used.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-t</term>
<listitem>
<para>
Print statistics at completion.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-u</term>
<listitem>
<para>
Update NSEC/NSEC3 chain when re-signing a previously signed
zone. With this option, a zone signed with NSEC can be
switched to NSEC3, or a zone signed with NSEC3 can
be switch to NSEC or to NSEC3 with different parameters.
Without this option, <command>dnssec-signzone</command> will
retain the existing chain when re-signing.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-v <replaceable class="parameter">level</replaceable></term>
<listitem>
<para>
Sets the debugging level.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-x</term>
<listitem>
<para>
Only sign the DNSKEY RRset with key-signing keys, and omit
signatures from zone-signing keys. (This is similar to the
<command>dnssec-dnskey-kskonly yes;</command> zone option in
<command>named</command>.)
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-z</term>
<listitem>
<para>
Ignore KSK flag on key when determining what to sign. This
causes KSK-flagged keys to sign all records, not just the
DNSKEY RRset. (This is similar to the
<command>update-check-ksk no;</command> zone option in
<command>named</command>.)
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-3 <replaceable class="parameter">salt</replaceable></term>
<listitem>
<para>
Generate an NSEC3 chain with the given hex encoded salt.
A dash (<replaceable class="parameter">salt</replaceable>) can
be used to indicate that no salt is to be used when generating the NSEC3 chain.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-H <replaceable class="parameter">iterations</replaceable></term>
<listitem>
<para>
When generating an NSEC3 chain, use this many iterations. The
default is 10.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-A</term>
<listitem>
<para>
When generating an NSEC3 chain set the OPTOUT flag on all
NSEC3 records and do not generate NSEC3 records for insecure
delegations.
</para>
<para>
Using this option twice (i.e., <option>-AA</option>)
turns the OPTOUT flag off for all records. This is useful
when using the <option>-u</option> option to modify an NSEC3
chain which previously had OPTOUT set.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>zonefile</term>
<listitem>
<para>
The file containing the zone to be signed.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>key</term>
<listitem>
<para>
Specify which keys should be used to sign the zone. If
no keys are specified, then the zone will be examined
for DNSKEY records at the zone apex. If these are found and
there are matching private keys, in the current directory,
then these will be used for signing.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>EXAMPLE</title>
<para>
The following command signs the <userinput>example.com</userinput>
zone with the DSA key generated by <command>dnssec-keygen</command>
(Kexample.com.+003+17247). Because the <command>-S</command> option
is not being used, the zone's keys must be in the master file
(<filename>db.example.com</filename>). This invocation looks
for <filename>dsset</filename> files, in the current directory,
so that DS records can be imported from them (<command>-g</command>).
</para>
<programlisting>% dnssec-signzone -g -o example.com db.example.com \
Kexample.com.+003+17247
db.example.com.signed
%</programlisting>
<para>
In the above example, <command>dnssec-signzone</command> creates
the file <filename>db.example.com.signed</filename>. This
file should be referenced in a zone statement in a
<filename>named.conf</filename> file.
</para>
<para>
This example re-signs a previously signed zone with default parameters.
The private keys are assumed to be in the current directory.
</para>
<programlisting>% cp db.example.com.signed db.example.com
% dnssec-signzone -o example.com db.example.com
db.example.com.signed
%</programlisting>
</refsect1>
<refsect1>
<title>SEE ALSO</title>
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>,
<citetitle>RFC 4033</citetitle>, <citetitle>RFC 4641</citetitle>.
</para>
</refsect1>
<refsect1>
<title>AUTHOR</title>
<para><corpauthor>Internet Systems Consortium</corpauthor>
</para>
</refsect1>
</refentry><!--
- Local variables:
- mode: sgml
- End:
-->