dnssec-signzone.html revision c52dde922980a55e22f6f9f9f97544922a9d67f8
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<!--
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux - Copyright (C) 2000-2009, 2011-2017 Internet Systems Consortium, Inc. ("ISC")
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux -
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux - This Source Code Form is subject to the terms of the Mozilla Public
1a71e5db977570fb40ad8689ee7a31ecc7540f11mental - License, v. 2.0. If a copy of the MPL was not distributed with this
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz - file, You can obtain one at http://mozilla.org/MPL/2.0/.
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz-->
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<html lang="en">
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<head>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<title>dnssec-signzone</title>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux</head>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<a name="man.dnssec-signzone"></a><div class="titlepage"></div>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux
7e2d535c37ea0830491ca84263aa3793a07904e0joncruz
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux
d1bde559850436556ebee2e70e10f1cfc8aff636Krzysztof Kosiński <div class="refnamediv">
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<h2>Name</h2>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<p>
1a71e5db977570fb40ad8689ee7a31ecc7540f11mental <span class="application">dnssec-signzone</span>
1a71e5db977570fb40ad8689ee7a31ecc7540f11mental &#8212; DNSSEC zone signing tool
1a71e5db977570fb40ad8689ee7a31ecc7540f11mental </p>
a2e796b608034e2c62290378d713058b8b58ef8fMarkus Engel</div>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux
6d0cbc6b5cf5f942c8ee7fa5c7eeb2a82eb617d5Alex Valavanis
6d0cbc6b5cf5f942c8ee7fa5c7eeb2a82eb617d5Alex Valavanis <div class="refsynopsisdiv">
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<h2>Synopsis</h2>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <div class="cmdsynopsis"><p>
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel <code class="command">dnssec-signzone</code>
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-a</code>]
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux [<code class="option">-d <em class="replaceable"><code>directory</code></em></code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-D</code>]
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>]
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux [<code class="option">-e <em class="replaceable"><code>end-time</code></em></code>]
a2e796b608034e2c62290378d713058b8b58ef8fMarkus Engel [<code class="option">-f <em class="replaceable"><code>output-file</code></em></code>]
a2e796b608034e2c62290378d713058b8b58ef8fMarkus Engel [<code class="option">-g</code>]
a2e796b608034e2c62290378d713058b8b58ef8fMarkus Engel [<code class="option">-h</code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>]
54ad9fc9cd6da88557d0dcd6c17eb47c7bbb5551Markus Engel [<code class="option">-I <em class="replaceable"><code>input-format</code></em></code>]
7ab987fc3c5f568cfe40eccfe8a4f4ecc8c0006cMarkus Engel [<code class="option">-j <em class="replaceable"><code>jitter</code></em></code>]
7ab987fc3c5f568cfe40eccfe8a4f4ecc8c0006cMarkus Engel [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-k <em class="replaceable"><code>key</code></em></code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-L <em class="replaceable"><code>serial</code></em></code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-M <em class="replaceable"><code>maxttl</code></em></code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-N <em class="replaceable"><code>soa-serial-format</code></em></code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>]
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux [<code class="option">-O <em class="replaceable"><code>output-format</code></em></code>]
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux [<code class="option">-P</code>]
a2e796b608034e2c62290378d713058b8b58ef8fMarkus Engel [<code class="option">-p</code>]
a2e796b608034e2c62290378d713058b8b58ef8fMarkus Engel [<code class="option">-Q</code>]
a2e796b608034e2c62290378d713058b8b58ef8fMarkus Engel [<code class="option">-R</code>]
a2e796b608034e2c62290378d713058b8b58ef8fMarkus Engel [<code class="option">-r <em class="replaceable"><code>randomdev</code></em></code>]
a2e796b608034e2c62290378d713058b8b58ef8fMarkus Engel [<code class="option">-S</code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-s <em class="replaceable"><code>start-time</code></em></code>]
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz [<code class="option">-T <em class="replaceable"><code>ttl</code></em></code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-t</code>]
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz [<code class="option">-u</code>]
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz [<code class="option">-V</code>]
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux [<code class="option">-X <em class="replaceable"><code>extended end-time</code></em></code>]
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz [<code class="option">-x</code>]
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux [<code class="option">-z</code>]
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux [<code class="option">-3 <em class="replaceable"><code>salt</code></em></code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel [<code class="option">-H <em class="replaceable"><code>iterations</code></em></code>]
5c85d657aed31c86ec1d89f03f56960bdb4d6df6bryce [<code class="option">-A</code>]
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel {zonefile}
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux [key...]
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </p></div>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </div>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <div class="refsection">
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<a name="id-1.7"></a><h2>DESCRIPTION</h2>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <p><span class="command"><strong>dnssec-signzone</strong></span>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux signs a zone. It generates
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux NSEC and RRSIG records and produces a signed version of the
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux zone. The security status of delegations from the signed zone
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux (that is, whether the child zones are secure or not) is
51dc158adbe2c9d1df3c941cbf78b90944d1afc2Markus Engel determined by the presence or absence of a
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel <code class="filename">keyset</code> file for each child zone.
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </div>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <div class="refsection">
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<a name="id-1.8"></a><h2>OPTIONS</h2>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux
51dc158adbe2c9d1df3c941cbf78b90944d1afc2Markus Engel
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel <div class="variablelist"><dl class="variablelist">
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dt><span class="term">-a</span></dt>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dd>
51dc158adbe2c9d1df3c941cbf78b90944d1afc2Markus Engel <p>
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel Verify all generated signatures.
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </dd>
51dc158adbe2c9d1df3c941cbf78b90944d1afc2Markus Engel<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dd>
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel <p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux Specifies the DNS class of the zone.
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </p>
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel </dd>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dt><span class="term">-C</span></dt>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dd>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux Compatibility mode: Generate a
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <code class="filename">keyset-<em class="replaceable"><code>zonename</code></em></code>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux file in addition to
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <code class="filename">dsset-<em class="replaceable"><code>zonename</code></em></code>
5c85d657aed31c86ec1d89f03f56960bdb4d6df6bryce when signing a zone, for use by older versions of
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <span class="command"><strong>dnssec-signzone</strong></span>.
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </dd>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dt><span class="term">-d <em class="replaceable"><code>directory</code></em></span></dt>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dd>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux Look for <code class="filename">dsset-</code> or
8a0a34615f080ecd1c09986d8963d6afe5937a25Jon A. Cruz <code class="filename">keyset-</code> files in <code class="option">directory</code>.
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </dd>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dt><span class="term">-D</span></dt>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dd>
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel <p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux Output only those record types automatically managed by
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel <span class="command"><strong>dnssec-signzone</strong></span>, i.e. RRSIG, NSEC,
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux NSEC3 and NSEC3PARAM records. If smart signing
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux (<code class="option">-S</code>) is used, DNSKEY records are also
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel included. The resulting file can be included in the original
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux zone file with <span class="command"><strong>$INCLUDE</strong></span>. This option
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux cannot be combined with <code class="option">-O raw</code>,
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <code class="option">-O map</code>, or serial number updating.
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </p>
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel </dd>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel<dd>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux When applicable, specifies the hardware to use for
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel cryptographic operations, such as a secure key store used
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel for signing.
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <p>
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel When BIND is built with OpenSSL PKCS#11 support, this defaults
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel to the string "pkcs11", which identifies an OpenSSL engine
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux that can drive a cryptographic accelerator or hardware service
470cc275d97606f1c400867ef00fd79fbf349b66Markus Engel module. When BIND is built with native PKCS#11 cryptography
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux (--enable-native-pkcs11), it defaults to the path of the PKCS#11
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux provider library specified via "--with-pkcs11".
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </p>
8a0a34615f080ecd1c09986d8963d6afe5937a25Jon A. Cruz </dd>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dt><span class="term">-g</span></dt>
3a3365c39fe3932d005ae1aa4324ef48606f5e18Krzysztof Kosiński<dd>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <p>
d1bde559850436556ebee2e70e10f1cfc8aff636Krzysztof Kosiński Generate DS records for child zones from
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux <code class="filename">dsset-</code> or <code class="filename">keyset-</code>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux file. Existing DS records will be removed.
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </p>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux </dd>
35e0418c921e7057987f57ba30ba95ec5e03c9e5knutux<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz<dd>
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz <p>
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz Key repository: Specify a directory to search for DNSSEC keys.
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz If not specified, defaults to the current directory.
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz </p>
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz </dd>
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz<dt><span class="term">-k <em class="replaceable"><code>key</code></em></span></dt>
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz<dd>
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz <p>
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz Treat specified key as a key signing key ignoring any
9dc68827cbd515262ecb8d5ae8547d9e82c72e00Jon A. Cruz key flags. This option may be specified multiple times.
</p>
</dd>
<dt><span class="term">-l <em class="replaceable"><code>domain</code></em></span></dt>
<dd>
<p>
Generate a DLV set in addition to the key (DNSKEY) and DS sets.
The domain is appended to the name of the records.
</p>
</dd>
<dt><span class="term">-M <em class="replaceable"><code>maxttl</code></em></span></dt>
<dd>
<p>
Sets the maximum TTL for the signed zone.
Any TTL higher than <em class="replaceable"><code>maxttl</code></em> in the
input zone will be reduced to <em class="replaceable"><code>maxttl</code></em>
in the output. This provides certainty as to the largest
possible TTL in the signed zone, which is useful to know when
rolling keys because it is the longest possible time before
signatures that have been retrieved by resolvers will expire
from resolver caches. Zones that are signed with this
option should be configured to use a matching
<code class="option">max-zone-ttl</code> in <code class="filename">named.conf</code>.
(Note: This option is incompatible with <code class="option">-D</code>,
because it modifies non-DNSSEC data in the output zone.)
</p>
</dd>
<dt><span class="term">-s <em class="replaceable"><code>start-time</code></em></span></dt>
<dd>
<p>
Specify the date and time when the generated RRSIG records
become valid. This can be either an absolute or relative
time. An absolute start time is indicated by a number
in YYYYMMDDHHMMSS notation; 20000530144500 denotes
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 <code class="option">start-time</code> is specified, the current
time minus 1 hour (to allow for clock skew) is used.
</p>
</dd>
<dt><span class="term">-e <em class="replaceable"><code>end-time</code></em></span></dt>
<dd>
<p>
Specify the date and time when the generated RRSIG records
expire. As with <code class="option">start-time</code>, 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 <code class="option">end-time</code> is
specified, 30 days from the start time is used as a default.
<code class="option">end-time</code> must be later than
<code class="option">start-time</code>.
</p>
</dd>
<dt><span class="term">-X <em class="replaceable"><code>extended end-time</code></em></span></dt>
<dd>
<p>
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.
</p>
<p>
As with <code class="option">start-time</code>, 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 <code class="option">extended end-time</code> is
specified, the value of <code class="option">end-time</code> is used as
the default. (<code class="option">end-time</code>, in turn, defaults to
30 days from the start time.) <code class="option">extended end-time</code>
must be later than <code class="option">start-time</code>.
</p>
</dd>
<dt><span class="term">-f <em class="replaceable"><code>output-file</code></em></span></dt>
<dd>
<p>
The name of the output file containing the signed zone. The
default is to append <code class="filename">.signed</code> to
the input filename. If <code class="option">output-file</code> is
set to <code class="literal">"-"</code>, then the signed zone is
written to the standard output, with a default output
format of "full".
</p>
</dd>
<dt><span class="term">-h</span></dt>
<dd>
<p>
Prints a short summary of the options and arguments to
<span class="command"><strong>dnssec-signzone</strong></span>.
</p>
</dd>
<dt><span class="term">-V</span></dt>
<dd>
<p>
Prints version information.
</p>
</dd>
<dt><span class="term">-i <em class="replaceable"><code>interval</code></em></span></dt>
<dd>
<p>
When a previously-signed zone is passed as input, records
may be resigned. The <code class="option">interval</code> 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.
</p>
<p>
The default cycle interval is one quarter of the difference
between the signature end and start times. So if neither
<code class="option">end-time</code> or <code class="option">start-time</code>
are specified, <span class="command"><strong>dnssec-signzone</strong></span>
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.
</p>
</dd>
<dt><span class="term">-I <em class="replaceable"><code>input-format</code></em></span></dt>
<dd>
<p>
The format of the input zone file.
Possible formats are <span class="command"><strong>"text"</strong></span> (default),
<span class="command"><strong>"raw"</strong></span>, and <span class="command"><strong>"map"</strong></span>.
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.
</p>
</dd>
<dt><span class="term">-j <em class="replaceable"><code>jitter</code></em></span></dt>
<dd>
<p>
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 <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 class="command"><strong>"keep"</strong></span> (default),
<span class="command"><strong>"increment"</strong></span>, <span class="command"><strong>"unixtime"</strong></span>,
and <span class="command"><strong>"date"</strong></span>.
</p>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><span class="command"><strong>"keep"</strong></span></span></dt>
<dd>
<p>Do not modify the SOA serial number.</p>
</dd>
<dt><span class="term"><span class="command"><strong>"increment"</strong></span></span></dt>
<dd>
<p>Increment the SOA serial number using RFC 1982
arithmetics.</p>
</dd>
<dt><span class="term"><span class="command"><strong>"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 class="command"><strong>"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 class="command"><strong>"text"</strong></span> (default),
which is the standard textual representation of the zone;
<span class="command"><strong>"full"</strong></span>, which is text output in a
format suitable for processing by external scripts;
and <span class="command"><strong>"map"</strong></span>, <span class="command"><strong>"raw"</strong></span>,
and <span class="command"><strong>"raw=N"</strong></span>, which store the zone in
binary formats for rapid loading by <span class="command"><strong>named</strong></span>.
<span class="command"><strong>"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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="variablelist">
<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 class="command"><strong>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 class="command"><strong>dnssec-dnskey-kskonly yes;</strong></span> zone option in
<span class="command"><strong>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 class="command"><strong>update-check-ksk no;</strong></span> zone option in
<span class="command"><strong>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="refsection">
<a name="id-1.9"></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 class="command"><strong>dnssec-keygen</strong></span>
(Kexample.com.+003+17247). Because the <span class="command"><strong>-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 class="command"><strong>-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 class="command"><strong>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="refsection">
<a name="id-1.10"></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></body>
</html>