man.dnssec-signzone.html revision 233da446071f469f0f2fc175a460b2f1f8ef36cc
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<!--
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC")
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - Copyright (C) 2000-2003 Internet Software Consortium.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User -
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - Permission to use, copy, modify, and/or distribute this software for any
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - purpose with or without fee is hereby granted, provided that the above
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - copyright notice and this permission notice appear in all copies.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User -
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User - PERFORMANCE OF THIS SOFTWARE.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User-->
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<!-- $Id$ -->
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<html>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<head>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt<title>dnssec-signzone</title>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<link rel="prev" href="man.dnssec-settime.html" title="dnssec-settime">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<link rel="next" href="man.dnssec-verify.html" title="dnssec-verify">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User</head>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<div class="navheader">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<table width="100%" summary="Navigation header">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<tr><th colspan="3" align="center"><span class="application">dnssec-signzone</span></th></tr>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<tr>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<td width="20%" align="left">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<a accesskey="p" href="man.dnssec-settime.html">Prev</a>�</td>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<th width="60%" align="center">Manual pages</th>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-verify.html">Next</a>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User</td>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User</tr>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User</table>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<hr>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt</div>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<div class="refentry" lang="en">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<a name="man.dnssec-signzone"></a><div class="titlepage"></div>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<div class="refnamediv">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<h2>Name</h2>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<p><span class="application">dnssec-signzone</span> &#8212; DNSSEC zone signing tool</p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User</div>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<div class="refsynopsisdiv">
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt<h2>Synopsis</h2>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<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>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User</div>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<div class="refsect1" lang="en">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<a name="id2646604"></a><h2>DESCRIPTION</h2>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<p><span><strong class="command">dnssec-signzone</strong></span>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User signs a zone. It generates
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User NSEC and RRSIG records and produces a signed version of the
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User zone. The security status of delegations from the signed zone
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User (that is, whether the child zones are secure or not) is
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User determined by the presence or absence of a
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User <code class="filename">keyset</code> file for each child zone.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User</div>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<div class="refsect1" lang="en">
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<a name="id2646624"></a><h2>OPTIONS</h2>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<div class="variablelist"><dl>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dt><span class="term">-a</span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd><p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Verify all generated signatures.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p></dd>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd><p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Specifies the DNS class of the zone.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p></dd>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dt><span class="term">-C</span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd><p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Compatibility mode: Generate a
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User <code class="filename">keyset-<em class="replaceable"><code>zonename</code></em></code>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User file in addition to
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User <code class="filename">dsset-<em class="replaceable"><code>zonename</code></em></code>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User when signing a zone, for use by older versions of
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User <span><strong class="command">dnssec-signzone</strong></span>.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p></dd>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dt><span class="term">-d <em class="replaceable"><code>directory</code></em></span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd><p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Look for <code class="filename">dsset-</code> or
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User <code class="filename">keyset-</code> files in <code class="option">directory</code>.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p></dd>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dt><span class="term">-D</span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd><p>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt Output only those record types automatically managed by
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User <span><strong class="command">dnssec-signzone</strong></span>, i.e. RRSIG, NSEC,
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User NSEC3 and NSEC3PARAM records. If smart signing
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt (<code class="option">-S</code>) is used, DNSKEY records are also
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User included. The resulting file can be included in the original
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User zone file with <span><strong class="command">$INCLUDE</strong></span>. This option
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt cannot be combined with <code class="option">-O raw</code>,
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User <code class="option">-O map</code>, or serial number updating.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p></dd>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
ad8f23aed6c75f94f238c1f23f4e17515d28eb55Tinderbox User<dd>
ad8f23aed6c75f94f238c1f23f4e17515d28eb55Tinderbox User<p>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt When applicable, specifies the hardware to use for
ad8f23aed6c75f94f238c1f23f4e17515d28eb55Tinderbox User cryptographic operations, such as a secure key store used
ad8f23aed6c75f94f238c1f23f4e17515d28eb55Tinderbox User for signing.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User When BIND is built with OpenSSL PKCS#11 support, this defaults
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User to the string "pkcs11", which identifies an OpenSSL engine
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User that can drive a cryptographic accelerator or hardware service
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User module. When BIND is built with native PKCS#11 cryptography
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User (--enable-native-pkcs11), it defaults to the path of the PKCS#11
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User provider library specified via "--with-pkcs11".
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User</dd>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dt><span class="term">-g</span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd><p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Generate DS records for child zones from
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User <code class="filename">dsset-</code> or <code class="filename">keyset-</code>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User file. Existing DS records will be removed.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p></dd>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd><p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Key repository: Specify a directory to search for DNSSEC keys.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User If not specified, defaults to the current directory.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p></dd>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dt><span class="term">-k <em class="replaceable"><code>key</code></em></span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd><p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Treat specified key as a key signing key ignoring any
10b865e9187fc77cae02f106ddcc9e03eecdfe06Tinderbox User key flags. This option may be specified multiple times.
10b865e9187fc77cae02f106ddcc9e03eecdfe06Tinderbox User </p></dd>
10b865e9187fc77cae02f106ddcc9e03eecdfe06Tinderbox User<dt><span class="term">-l <em class="replaceable"><code>domain</code></em></span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd><p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Generate a DLV set in addition to the key (DNSKEY) and DS sets.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User The domain is appended to the name of the records.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p></dd>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dt><span class="term">-M <em class="replaceable"><code>maxttl</code></em></span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd><p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Sets the maximum TTL for the signed zone.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Any TTL higher than <em class="replaceable"><code>maxttl</code></em> in the
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User input zone will be reduced to <em class="replaceable"><code>maxttl</code></em>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User in the output. This provides certainty as to the largest
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt possible TTL in the signed zone, which is useful to know when
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt rolling keys because it is the longest possible time before
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt signatures that have been retrieved by resolvers will expire
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt from resolver caches. Zones that are signed with this
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt option should be configured to use a matching
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt <code class="option">max-zone-ttl</code> in <code class="filename">named.conf</code>.
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt (Note: This option is incompatible with <code class="option">-D</code>,
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt because it modifies non-DNSSEC data in the output zone.)
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt </p></dd>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt<dt><span class="term">-s <em class="replaceable"><code>start-time</code></em></span></dt>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt<dd><p>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt Specify the date and time when the generated RRSIG records
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt become valid. This can be either an absolute or relative
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt time. An absolute start time is indicated by a number
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt in YYYYMMDDHHMMSS notation; 20000530144500 denotes
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt 14:45:00 UTC on May 30th, 2000. A relative start time is
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt indicated by +N, which is N seconds from the current time.
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt If no <code class="option">start-time</code> is specified, the current
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt time minus 1 hour (to allow for clock skew) is used.
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt </p></dd>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt<dt><span class="term">-e <em class="replaceable"><code>end-time</code></em></span></dt>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt<dd><p>
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt Specify the date and time when the generated RRSIG records
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt expire. As with <code class="option">start-time</code>, an absolute
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt time is indicated in YYYYMMDDHHMMSS notation. A time relative
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt to the start time is indicated with +N, which is N seconds from
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt the start time. A time relative to the current time is
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt indicated with now+N. If no <code class="option">end-time</code> is
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt specified, 30 days from the start time is used as a default.
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt <code class="option">end-time</code> must be later than
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt <code class="option">start-time</code>.
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt </p></dd>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dt><span class="term">-X <em class="replaceable"><code>extended end-time</code></em></span></dt>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<dd>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User Specify the date and time when the generated RRSIG records
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User for the DNSKEY RRset will expire. This is to be used in cases
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User when the DNSKEY signatures need to persist longer than
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User signatures on other records; e.g., when the private component
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User of the KSK is kept offline and the KSK signature is to be
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User refreshed manually.
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User </p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User<p>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User As with <code class="option">start-time</code>, an absolute
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User time is indicated in YYYYMMDDHHMMSS notation. A time relative
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User to the start time is indicated with +N, which is N seconds from
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User the start time. A time relative to the current time is
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User indicated with now+N. If no <code class="option">extended end-time</code> is
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User specified, the value of <code class="option">end-time</code> is used as
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Hunt the default. (<code class="option">end-time</code>, in turn, defaults to
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User 30 days from the start time.) <code class="option">extended end-time</code>
fae13836a33b474a6aa2c147df8334f5b1ffae45Tinderbox User 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><strong class="command">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><strong class="command">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><strong class="command">"text"</strong></span> (default),
<span><strong class="command">"raw"</strong></span>, and <span><strong class="command">"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><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="id2678274"></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="id2678353"></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="id2678380"></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.ch13.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>