man.dnssec-signzone.html revision 30c0c7470d5bfabd8f43c563f4eca636d06cc484
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<!--
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor - Copyright (C) 2004-2014 Internet Systems Consortium, Inc. ("ISC")
fd9abdda70912b99b24e3bf1a38f26fde908a74cnd - Copyright (C) 2000-2003 Internet Software Consortium.
fd9abdda70912b99b24e3bf1a38f26fde908a74cnd -
fd9abdda70912b99b24e3bf1a38f26fde908a74cnd - Permission to use, copy, modify, and/or distribute this software for any
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor - purpose with or without fee is hereby granted, provided that the above
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor - copyright notice and this permission notice appear in all copies.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor -
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
96ad5d81ee4a2cc66a4ae19893efc8aa6d06fae7jailletc - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
2e545ce2450a9953665f701bb05350f0d3f26275nd - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen - PERFORMANCE OF THIS SOFTWARE.
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen-->
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<!-- $Id$ -->
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<html>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<head>
af33a4994ae2ff15bc67d19ff1a7feb906745bf8rbowen<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
3f08db06526d6901aa08c110b5bc7dde6bc39905nd<title>dnssec-signzone</title>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
3f08db06526d6901aa08c110b5bc7dde6bc39905nd<link rel="prev" href="man.dnssec-settime.html" title="dnssec-settime">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<link rel="next" href="man.dnssec-verify.html" title="dnssec-verify">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor</head>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<div class="navheader">
f086b4b402fa9a2fefc7dda85de2a3cc1cd0a654rjung<table width="100%" summary="Navigation header">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<tr><th colspan="3" align="center"><span class="application">dnssec-signzone</span></th></tr>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<tr>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<td width="20%" align="left">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<a accesskey="p" href="man.dnssec-settime.html">Prev</a>�</td>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<th width="60%" align="center">Manual pages</th>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-verify.html">Next</a>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor</td>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor</tr>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor</table>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<hr>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor</div>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<div class="refentry" lang="en">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<a name="man.dnssec-signzone"></a><div class="titlepage"></div>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<div class="refnamediv">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<h2>Name</h2>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<p><span class="application">dnssec-signzone</span> &#8212; DNSSEC zone signing tool</p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor</div>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<div class="refsynopsisdiv">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<h2>Synopsis</h2>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<div class="cmdsynopsis"><p><code class="command">dnssec-signzone</code> [<code class="option">-a</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-d <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-D</code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] [<code class="option">-e <em class="replaceable"><code>end-time</code></em></code>] [<code class="option">-f <em class="replaceable"><code>output-file</code></em></code>] [<code class="option">-g</code>] [<code class="option">-h</code>] [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-k <em class="replaceable"><code>key</code></em></code>] [<code class="option">-L <em class="replaceable"><code>serial</code></em></code>] [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-M <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>] [<code class="option">-I <em class="replaceable"><code>input-format</code></em></code>] [<code class="option">-j <em class="replaceable"><code>jitter</code></em></code>] [<code class="option">-N <em class="replaceable"><code>soa-serial-format</code></em></code>] [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>] [<code class="option">-O <em class="replaceable"><code>output-format</code></em></code>] [<code class="option">-P</code>] [<code class="option">-p</code>] [<code class="option">-Q</code>] [<code class="option">-R</code>] [<code class="option">-r <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-S</code>] [<code class="option">-s <em class="replaceable"><code>start-time</code></em></code>] [<code class="option">-T <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-t</code>] [<code class="option">-u</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] [<code class="option">-X <em class="replaceable"><code>extended end-time</code></em></code>] [<code class="option">-x</code>] [<code class="option">-z</code>] [<code class="option">-3 <em class="replaceable"><code>salt</code></em></code>] [<code class="option">-H <em class="replaceable"><code>iterations</code></em></code>] [<code class="option">-A</code>] {zonefile} [key...]</p></div>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor</div>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<div class="refsect1" lang="en">
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<a name="id2643317"></a><h2>DESCRIPTION</h2>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<p><span><strong class="command">dnssec-signzone</strong></span>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar signs a zone. It generates
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar NSEC and RRSIG records and produces a signed version of the
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar zone. The security status of delegations from the signed zone
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar (that is, whether the child zones are secure or not) is
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar determined by the presence or absence of a
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor <code class="filename">keyset</code> file for each child zone.
e40d2af13fd7ff120eda49cd327c68fbc16443e8sf </p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor</div>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<div class="refsect1" lang="en">
df135dbebadfdf65d0c45e181d6c19b84d17b7c6sf<a name="id2643336"></a><h2>OPTIONS</h2>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<div class="variablelist"><dl>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dt><span class="term">-a</span></dt>
7e9c796f2dc0dba993a817b3a58cfd56b4e511edwrowe<dd><p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor Verify all generated signatures.
ffb01336be79c64046b636e59fa8ddca8ec029edsf </p></dd>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dd><p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor Specifies the DNS class of the zone.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor </p></dd>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dt><span class="term">-C</span></dt>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dd><p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor Compatibility mode: Generate a
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor <code class="filename">keyset-<em class="replaceable"><code>zonename</code></em></code>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor file in addition to
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor <code class="filename">dsset-<em class="replaceable"><code>zonename</code></em></code>
df135dbebadfdf65d0c45e181d6c19b84d17b7c6sf when signing a zone, for use by older versions of
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor <span><strong class="command">dnssec-signzone</strong></span>.
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar </p></dd>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dt><span class="term">-d <em class="replaceable"><code>directory</code></em></span></dt>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dd><p>
30471a4650391f57975f60bbb6e4a90be7b284bfhumbedooh Look for <code class="filename">dsset-</code> or
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor <code class="filename">keyset-</code> files in <code class="option">directory</code>.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor </p></dd>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dt><span class="term">-D</span></dt>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dd><p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor Output only those record types automatically managed by
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor <span><strong class="command">dnssec-signzone</strong></span>, i.e. RRSIG, NSEC,
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor NSEC3 and NSEC3PARAM records. If smart signing
48c64aeceef385e19025b384bd719b2a9789592dnd (<code class="option">-S</code>) is used, DNSKEY records are also
48c64aeceef385e19025b384bd719b2a9789592dnd included. The resulting file can be included in the original
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor zone file with <span><strong class="command">$INCLUDE</strong></span>. This option
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor cannot be combined with <code class="option">-O raw</code>,
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor <code class="option">-O map</code>, or serial number updating.
1462ff536f1b939bb337766b2056109c29664c4erbowen </p></dd>
1462ff536f1b939bb337766b2056109c29664c4erbowen<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
1462ff536f1b939bb337766b2056109c29664c4erbowen<dd>
1462ff536f1b939bb337766b2056109c29664c4erbowen<p>
1462ff536f1b939bb337766b2056109c29664c4erbowen When applicable, specifies the hardware to use for
1462ff536f1b939bb337766b2056109c29664c4erbowen cryptographic operations, such as a secure key store used
1462ff536f1b939bb337766b2056109c29664c4erbowen for signing.
1462ff536f1b939bb337766b2056109c29664c4erbowen </p>
25f8d56998acb95d39c62c489d72b92d8d29b765humbedooh<p>
25f8d56998acb95d39c62c489d72b92d8d29b765humbedooh When BIND is built with OpenSSL PKCS#11 support, this defaults
25f8d56998acb95d39c62c489d72b92d8d29b765humbedooh to the string "pkcs11", which identifies an OpenSSL engine
25f8d56998acb95d39c62c489d72b92d8d29b765humbedooh that can drive a cryptographic accelerator or hardware service
25f8d56998acb95d39c62c489d72b92d8d29b765humbedooh module. When BIND is built with native PKCS#11 cryptography
25f8d56998acb95d39c62c489d72b92d8d29b765humbedooh (--enable-native-pkcs11), it defaults to the path of the PKCS#11
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor provider library specified via "--with-pkcs11".
65a611af7093423efb91e5794b8887a527d4cf63trawick </p>
65a611af7093423efb91e5794b8887a527d4cf63trawick</dd>
65a611af7093423efb91e5794b8887a527d4cf63trawick<dt><span class="term">-g</span></dt>
65a611af7093423efb91e5794b8887a527d4cf63trawick<dd><p>
65a611af7093423efb91e5794b8887a527d4cf63trawick Generate DS records for child zones from
65a611af7093423efb91e5794b8887a527d4cf63trawick <code class="filename">dsset-</code> or <code class="filename">keyset-</code>
65a611af7093423efb91e5794b8887a527d4cf63trawick file. Existing DS records will be removed.
65a611af7093423efb91e5794b8887a527d4cf63trawick </p></dd>
65a611af7093423efb91e5794b8887a527d4cf63trawick<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
65a611af7093423efb91e5794b8887a527d4cf63trawick<dd><p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor Key repository: Specify a directory to search for DNSSEC keys.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor If not specified, defaults to the current directory.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor </p></dd>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dt><span class="term">-k <em class="replaceable"><code>key</code></em></span></dt>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dd><p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor Treat specified key as a key signing key ignoring any
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor key flags. This option may be specified multiple times.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor </p></dd>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dt><span class="term">-l <em class="replaceable"><code>domain</code></em></span></dt>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dd><p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor Generate a DLV set in addition to the key (DNSKEY) and DS sets.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor The domain is appended to the name of the records.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor </p></dd>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dt><span class="term">-M <em class="replaceable"><code>maxttl</code></em></span></dt>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dd><p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor Sets the maximum TTL for the signed zone.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor Any TTL higher than <em class="replaceable"><code>maxttl</code></em> in the
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor input zone will be reduced to <em class="replaceable"><code>maxttl</code></em>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor in the output. This provides certainty as to the largest
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor possible TTL in the signed zone, which is useful to know when
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor rolling keys because it is the longest possible time before
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor signatures that have been retrieved by resolvers will expire
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor from resolver caches. Zones that are signed with this
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor option should be configured to use a matching
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor <code class="option">max-zone-ttl</code> in <code class="filename">named.conf</code>.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor (Note: This option is incompatible with <code class="option">-D</code>,
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor because it modifies non-DNSSEC data in the output zone.)
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor </p></dd>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dt><span class="term">-s <em class="replaceable"><code>start-time</code></em></span></dt>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dd><p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor Specify the date and time when the generated RRSIG records
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor become valid. This can be either an absolute or relative
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor time. An absolute start time is indicated by a number
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor in YYYYMMDDHHMMSS notation; 20000530144500 denotes
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor 14:45:00 UTC on May 30th, 2000. A relative start time is
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor indicated by +N, which is N seconds from the current time.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor If no <code class="option">start-time</code> is specified, the current
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor time minus 1 hour (to allow for clock skew) is used.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor </p></dd>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dt><span class="term">-e <em class="replaceable"><code>end-time</code></em></span></dt>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<dd><p>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar Specify the date and time when the generated RRSIG records
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar expire. As with <code class="option">start-time</code>, an absolute
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar time is indicated in YYYYMMDDHHMMSS notation. A time relative
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar to the start time is indicated with +N, which is N seconds from
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar the start time. A time relative to the current time is
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar indicated with now+N. If no <code class="option">end-time</code> is
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar specified, 30 days from the start time is used as a default.
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar <code class="option">end-time</code> must be later than
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar <code class="option">start-time</code>.
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar </p></dd>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<dt><span class="term">-X <em class="replaceable"><code>extended end-time</code></em></span></dt>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<dd>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<p>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar Specify the date and time when the generated RRSIG records
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar for the DNSKEY RRset will expire. This is to be used in cases
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar when the DNSKEY signatures need to persist longer than
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar signatures on other records; e.g., when the private component
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar of the KSK is kept offline and the KSK signature is to be
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar refreshed manually.
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar </p>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<p>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar As with <code class="option">start-time</code>, an absolute
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar time is indicated in YYYYMMDDHHMMSS notation. A time relative
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar to the start time is indicated with +N, which is N seconds from
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar the start time. A time relative to the current time is
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar indicated with now+N. If no <code class="option">extended end-time</code> is
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar specified, the value of <code class="option">end-time</code> is used as
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar the default. (<code class="option">end-time</code>, in turn, defaults to
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar 30 days from the start time.) <code class="option">extended end-time</code>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar must be later than <code class="option">start-time</code>.
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar </p>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar</dd>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<dt><span class="term">-f <em class="replaceable"><code>output-file</code></em></span></dt>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<dd><p>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar The name of the output file containing the signed zone. The
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar default is to append <code class="filename">.signed</code> to
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar the input filename. If <code class="option">output-file</code> is
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar set to <code class="literal">"-"</code>, then the signed zone is
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar written to the standard output, with a default output
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar format of "full".
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar </p></dd>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<dt><span class="term">-h</span></dt>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<dd><p>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar Prints a short summary of the options and arguments to
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar <span><strong class="command">dnssec-signzone</strong></span>.
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar </p></dd>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<dt><span class="term">-V</span></dt>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<dd><p>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar Prints version information.
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar </p></dd>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<dt><span class="term">-i <em class="replaceable"><code>interval</code></em></span></dt>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<dd>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar<p>
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar When a previously-signed zone is passed as input, records
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar may be resigned. The <code class="option">interval</code> option
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar specifies the cycle interval as an offset from the current
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar time (in seconds). If a RRSIG record expires after the
1f1b6bf13313fdd14a45e52e553d3ff28689b717coar cycle interval, it is retained. Otherwise, it is considered
1462ff536f1b939bb337766b2056109c29664c4erbowen to be expiring soon, and it will be replaced.
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor </p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor<p>
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor The default cycle interval is one quarter of the difference
f086b4b402fa9a2fefc7dda85de2a3cc1cd0a654rjung between the signature end and start times. So if neither
727872d18412fc021f03969b8641810d8896820bhumbedooh <code class="option">end-time</code> or <code class="option">start-time</code>
0d0ba3a410038e179b695446bb149cce6264e0abnd are specified, <span><strong class="command">dnssec-signzone</strong></span>
727872d18412fc021f03969b8641810d8896820bhumbedooh generates
cc7e1025de9ac63bd4db6fe7f71c158b2cf09fe4humbedooh signatures that are valid for 30 days, with a cycle
0d0ba3a410038e179b695446bb149cce6264e0abnd interval of 7.5 days. Therefore, if any existing RRSIG records
cc7e1025de9ac63bd4db6fe7f71c158b2cf09fe4humbedooh are due to expire in less than 7.5 days, they would be
727872d18412fc021f03969b8641810d8896820bhumbedooh replaced.
0d0ba3a410038e179b695446bb149cce6264e0abnd </p>
0d0ba3a410038e179b695446bb149cce6264e0abnd</dd>
0d0ba3a410038e179b695446bb149cce6264e0abnd<dt><span class="term">-I <em class="replaceable"><code>input-format</code></em></span></dt>
ac082aefa89416cbdc9a1836eaf3bed9698201c8humbedooh<dd><p>
0d0ba3a410038e179b695446bb149cce6264e0abnd The format of the input zone file.
0d0ba3a410038e179b695446bb149cce6264e0abnd Possible formats are <span><strong class="command">"text"</strong></span> (default),
0d0ba3a410038e179b695446bb149cce6264e0abnd <span><strong class="command">"raw"</strong></span>, and <span><strong class="command">"map"</strong></span>.
727872d18412fc021f03969b8641810d8896820bhumbedooh This option is primarily intended to be used for dynamic
0d0ba3a410038e179b695446bb149cce6264e0abnd signed zones so that the dumped zone file in a non-text
0d0ba3a410038e179b695446bb149cce6264e0abnd format containing updates can be signed directly.
30471a4650391f57975f60bbb6e4a90be7b284bfhumbedooh The use of this option does not make much sense for
205f749042ed530040a4f0080dbcb47ceae8a374rjung non-dynamic zones.
af33a4994ae2ff15bc67d19ff1a7feb906745bf8rbowen </p></dd>
0d0ba3a410038e179b695446bb149cce6264e0abnd<dt><span class="term">-j <em class="replaceable"><code>jitter</code></em></span></dt>
7fec19672a491661b2fe4b29f685bc7f4efa64d4nd<dd>
7fec19672a491661b2fe4b29f685bc7f4efa64d4nd<p>
7fec19672a491661b2fe4b29f685bc7f4efa64d4nd When signing a zone with a fixed signature lifetime, all
cc8190433d13f5e9de618c5d7f10c824c0c1919cgryzor 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 <code class="option">jitter</code> option specifies a
jitter window that will be used to randomize the signature
expire time, thus spreading incremental signature
regeneration over time.
</p>
<p>
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.
</p>
</dd>
<dt><span class="term">-L <em class="replaceable"><code>serial</code></em></span></dt>
<dd><p>
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.)
</p></dd>
<dt><span class="term">-n <em class="replaceable"><code>ncpus</code></em></span></dt>
<dd><p>
Specifies the number of threads to use. By default, one
thread is started for each detected CPU.
</p></dd>
<dt><span class="term">-N <em class="replaceable"><code>soa-serial-format</code></em></span></dt>
<dd>
<p>
The SOA serial number format of the signed zone.
Possible formats are <span><strong class="command">"keep"</strong></span> (default),
<span><strong class="command">"increment"</strong></span>, <span><strong class="command">"unixtime"</strong></span>,
and <span><strong class="command">"date"</strong></span>.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">"keep"</strong></span></span></dt>
<dd><p>Do not modify the SOA serial number.</p></dd>
<dt><span class="term"><span><strong class="command">"increment"</strong></span></span></dt>
<dd><p>Increment the SOA serial number using RFC 1982
arithmetics.</p></dd>
<dt><span class="term"><span><strong class="command">"unixtime"</strong></span></span></dt>
<dd><p>Set the SOA serial number to the number of seconds
since epoch.</p></dd>
<dt><span class="term"><span><strong class="command">"date"</strong></span></span></dt>
<dd><p>Set the SOA serial number to today's date in
YYYYMMDDNN format.</p></dd>
</dl></div>
</dd>
<dt><span class="term">-o <em class="replaceable"><code>origin</code></em></span></dt>
<dd><p>
The zone origin. If not specified, the name of the zone file
is assumed to be the origin.
</p></dd>
<dt><span class="term">-O <em class="replaceable"><code>output-format</code></em></span></dt>
<dd><p>
The format of the output file containing the signed zone.
Possible formats are <span><strong class="command">"text"</strong></span> (default),
which is the standard textual representation of the zone;
<span><strong class="command">"full"</strong></span>, which is text output in a
format suitable for processing by external scripts;
and <span><strong class="command">"map"</strong></span>, <span><strong class="command">"raw"</strong></span>,
and <span><strong class="command">"raw=N"</strong></span>, which store the zone in
binary formats for rapid loading by <span><strong class="command">named</strong></span>.
<span><strong class="command">"raw=N"</strong></span> specifies the format version of
the raw zone file: if N is 0, the raw file can be read by
any version of <span><strong class="command">named</strong></span>; if N is 1, the file
can be read by release 9.9.0 or higher; the default is 1.
</p></dd>
<dt><span class="term">-p</span></dt>
<dd><p>
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.
</p></dd>
<dt><span class="term">-P</span></dt>
<dd>
<p>
Disable post sign verification tests.
</p>
<p>
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.
</p>
</dd>
<dt><span class="term">-Q</span></dt>
<dd>
<p>
Remove signatures from keys that are no longer active.
</p>
<p>
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 <code class="option">-Q</code>
forces <span><strong class="command">dnssec-signzone</strong></span> 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").
</p>
</dd>
<dt><span class="term">-R</span></dt>
<dd>
<p>
Remove signatures from keys that are no longer published.
</p>
<p>
This option is similar to <code class="option">-Q</code>, except it
forces <span><strong class="command">dnssec-signzone</strong></span> 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").
</p>
</dd>
<dt><span class="term">-r <em class="replaceable"><code>randomdev</code></em></span></dt>
<dd><p>
Specifies the source of randomness. If the operating
system does not provide a <code class="filename">/dev/random</code>
or equivalent device, the default source of randomness
is keyboard input. <code class="filename">randomdev</code>
specifies
the name of a character device or file containing random
data to be used instead of the default. The special value
<code class="filename">keyboard</code> indicates that keyboard
input should be used.
</p></dd>
<dt><span class="term">-S</span></dt>
<dd>
<p>
Smart signing: Instructs <span><strong class="command">dnssec-signzone</strong></span> to
search the key repository for keys that match the zone being
signed, and to include them in the zone if appropriate.
</p>
<p>
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:
</p>
<div class="variablelist"><dl>
<dt></dt>
<dd><p>
If no timing metadata has been set for the key, the key is
published in the zone and used to sign the zone.
</p></dd>
<dt></dt>
<dd><p>
If the key's publication date is set and is in the past, the
key is published in the zone.
</p></dd>
<dt></dt>
<dd><p>
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.
</p></dd>
<dt></dt>
<dd><p>
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.
</p></dd>
<dt></dt>
<dd><p>
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.
</p></dd>
</dl></div>
</dd>
<dt><span class="term">-T <em class="replaceable"><code>ttl</code></em></span></dt>
<dd><p>
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
<code class="option">-S</code>, 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.
</p></dd>
<dt><span class="term">-t</span></dt>
<dd><p>
Print statistics at completion.
</p></dd>
<dt><span class="term">-u</span></dt>
<dd><p>
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, <span><strong class="command">dnssec-signzone</strong></span> will
retain the existing chain when re-signing.
</p></dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
<dd><p>
Sets the debugging level.
</p></dd>
<dt><span class="term">-x</span></dt>
<dd><p>
Only sign the DNSKEY RRset with key-signing keys, and omit
signatures from zone-signing keys. (This is similar to the
<span><strong class="command">dnssec-dnskey-kskonly yes;</strong></span> zone option in
<span><strong class="command">named</strong></span>.)
</p></dd>
<dt><span class="term">-z</span></dt>
<dd><p>
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
<span><strong class="command">update-check-ksk no;</strong></span> zone option in
<span><strong class="command">named</strong></span>.)
</p></dd>
<dt><span class="term">-3 <em class="replaceable"><code>salt</code></em></span></dt>
<dd><p>
Generate an NSEC3 chain with the given hex encoded salt.
A dash (<em class="replaceable"><code>salt</code></em>) can
be used to indicate that no salt is to be used when generating the NSEC3 chain.
</p></dd>
<dt><span class="term">-H <em class="replaceable"><code>iterations</code></em></span></dt>
<dd><p>
When generating an NSEC3 chain, use this many iterations. The
default is 10.
</p></dd>
<dt><span class="term">-A</span></dt>
<dd>
<p>
When generating an NSEC3 chain set the OPTOUT flag on all
NSEC3 records and do not generate NSEC3 records for insecure
delegations.
</p>
<p>
Using this option twice (i.e., <code class="option">-AA</code>)
turns the OPTOUT flag off for all records. This is useful
when using the <code class="option">-u</code> option to modify an NSEC3
chain which previously had OPTOUT set.
</p>
</dd>
<dt><span class="term">zonefile</span></dt>
<dd><p>
The file containing the zone to be signed.
</p></dd>
<dt><span class="term">key</span></dt>
<dd><p>
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.
</p></dd>
</dl></div>
</div>
<div class="refsect1" lang="en">
<a name="id2675601"></a><h2>EXAMPLE</h2>
<p>
The following command signs the <strong class="userinput"><code>example.com</code></strong>
zone with the DSA key generated by <span><strong class="command">dnssec-keygen</strong></span>
(Kexample.com.+003+17247). Because the <span><strong class="command">-S</strong></span> option
is not being used, the zone's keys must be in the master file
(<code class="filename">db.example.com</code>). This invocation looks
for <code class="filename">dsset</code> files, in the current directory,
so that DS records can be imported from them (<span><strong class="command">-g</strong></span>).
</p>
<pre class="programlisting">% dnssec-signzone -g -o example.com db.example.com \
Kexample.com.+003+17247
db.example.com.signed
%</pre>
<p>
In the above example, <span><strong class="command">dnssec-signzone</strong></span> creates
the file <code class="filename">db.example.com.signed</code>. This
file should be referenced in a zone statement in a
<code class="filename">named.conf</code> file.
</p>
<p>
This example re-signs a previously signed zone with default parameters.
The private keys are assumed to be in the current directory.
</p>
<pre class="programlisting">% cp db.example.com.signed db.example.com
% dnssec-signzone -o example.com db.example.com
db.example.com.signed
%</pre>
</div>
<div class="refsect1" lang="en">
<a name="id2675680"></a><h2>SEE ALSO</h2>
<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 4033</em>, <em class="citetitle">RFC 4641</em>.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2675707"></a><h2>AUTHOR</h2>
<p><span class="corpauthor">Internet Systems Consortium</span>
</p>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="man.dnssec-settime.html">Prev</a>�</td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch10.html">Up</a></td>
<td width="40%" align="right">�<a accesskey="n" href="man.dnssec-verify.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">dnssec-settime</span>�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�<span class="application">dnssec-verify</span>
</td>
</tr>
</table>
</div>
<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>