man.dnssec-signzone.html revision c60ee6edf129596fa04db86c6865d75b5a412598
1b5fa99638ad2d73f40b77d02e4bef798c2869b8Christian Maeder<!--
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - Copyright (C) 2004-2014 Internet Systems Consortium, Inc. ("ISC")
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - Copyright (C) 2000-2003 Internet Software Consortium.
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich -
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - Permission to use, copy, modify, and/or distribute this software for any
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - purpose with or without fee is hereby granted, provided that the above
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - copyright notice and this permission notice appear in all copies.
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich -
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich - PERFORMANCE OF THIS SOFTWARE.
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich-->
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<!-- $Id$ -->
105ef29861e750a27d2f3436e369491977af31f9Klaus Luettich<html>
91849a39b94abfecb7e854930ad280a68699d08cChristian Maeder<head>
48b05bf95b2c4d38161853f6288e4a646ce49e9bChristian Maeder<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
105ef29861e750a27d2f3436e369491977af31f9Klaus Luettich<title>dnssec-signzone</title>
caf9cbd08ac84499a343bbd0eac79e9bb47a40e5Christian Maeder<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
105ef29861e750a27d2f3436e369491977af31f9Klaus Luettich<link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
7baffffaf1d805902dc91704694271b2c39486abPascal Schmidt<link rel="prev" href="man.dnssec-settime.html" title="dnssec-settime">
a18474e0980d1a9a44b73abfe1c3eea89089fa39Pascal Schmidt<link rel="next" href="man.dnssec-verify.html" title="dnssec-verify">
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich</head>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<div class="navheader">
60ef7437c5c9462bc5287a001ea846a85da8cee5Christian Maeder<table width="100%" summary="Navigation header">
60ef7437c5c9462bc5287a001ea846a85da8cee5Christian Maeder<tr><th colspan="3" align="center"><span class="application">dnssec-signzone</span></th></tr>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<tr>
f7d16152baa03da85173e533b4c3f7d9df47ca3ePascal Schmidt<td width="20%" align="left">
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<a accesskey="p" href="man.dnssec-settime.html">Prev</a>�</td>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<th width="60%" align="center">Manual pages</th>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-verify.html">Next</a>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich</td>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich</tr>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich</table>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<hr>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich</div>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<div class="refentry" lang="en">
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<a name="man.dnssec-signzone"></a><div class="titlepage"></div>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<div class="refnamediv">
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<h2>Name</h2>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<p><span class="application">dnssec-signzone</span> &#8212; DNSSEC zone signing tool</p>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich</div>
2ce581897091465f0d602e2e36c4ea687230855fChristian Maeder<div class="refsynopsisdiv">
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<h2>Synopsis</h2>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<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>
b3e31d2c629f0f861483c1dcd5d81d2ce1434833Christian Maeder</div>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<div class="refsect1" lang="en">
2ce581897091465f0d602e2e36c4ea687230855fChristian Maeder<a name="id2644242"></a><h2>DESCRIPTION</h2>
b3e31d2c629f0f861483c1dcd5d81d2ce1434833Christian Maeder<p><span><strong class="command">dnssec-signzone</strong></span>
b3e31d2c629f0f861483c1dcd5d81d2ce1434833Christian Maeder signs a zone. It generates
b3e31d2c629f0f861483c1dcd5d81d2ce1434833Christian Maeder NSEC and RRSIG records and produces a signed version of the
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich zone. The security status of delegations from the signed zone
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich (that is, whether the child zones are secure or not) is
9266fe93ad7f61497b5816b33c65b73ca871b005Pascal Schmidt determined by the presence or absence of a
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich <code class="filename">keyset</code> file for each child zone.
9266fe93ad7f61497b5816b33c65b73ca871b005Pascal Schmidt </p>
9266fe93ad7f61497b5816b33c65b73ca871b005Pascal Schmidt</div>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<div class="refsect1" lang="en">
9266fe93ad7f61497b5816b33c65b73ca871b005Pascal Schmidt<a name="id2644261"></a><h2>OPTIONS</h2>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<div class="variablelist"><dl>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<dt><span class="term">-a</span></dt>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<dd><p>
caf9cbd08ac84499a343bbd0eac79e9bb47a40e5Christian Maeder Verify all generated signatures.
2ce581897091465f0d602e2e36c4ea687230855fChristian Maeder </p></dd>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
2ce581897091465f0d602e2e36c4ea687230855fChristian Maeder<dd><p>
2ce581897091465f0d602e2e36c4ea687230855fChristian Maeder Specifies the DNS class of the zone.
caf9cbd08ac84499a343bbd0eac79e9bb47a40e5Christian Maeder </p></dd>
f7d16152baa03da85173e533b4c3f7d9df47ca3ePascal Schmidt<dt><span class="term">-C</span></dt>
2ce581897091465f0d602e2e36c4ea687230855fChristian Maeder<dd><p>
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt Compatibility mode: Generate a
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt <code class="filename">keyset-<em class="replaceable"><code>zonename</code></em></code>
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt file in addition to
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt <code class="filename">dsset-<em class="replaceable"><code>zonename</code></em></code>
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt when signing a zone, for use by older versions of
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt <span><strong class="command">dnssec-signzone</strong></span>.
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt </p></dd>
00c9f41b95cb14c82995d2810ab908c2a10f9ad1Pascal Schmidt<dt><span class="term">-d <em class="replaceable"><code>directory</code></em></span></dt>
00c9f41b95cb14c82995d2810ab908c2a10f9ad1Pascal Schmidt<dd><p>
00c9f41b95cb14c82995d2810ab908c2a10f9ad1Pascal Schmidt Look for <code class="filename">dsset-</code> or
00c9f41b95cb14c82995d2810ab908c2a10f9ad1Pascal Schmidt <code class="filename">keyset-</code> files in <code class="option">directory</code>.
00c9f41b95cb14c82995d2810ab908c2a10f9ad1Pascal Schmidt </p></dd>
00c9f41b95cb14c82995d2810ab908c2a10f9ad1Pascal Schmidt<dt><span class="term">-D</span></dt>
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt<dd><p>
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt Output only those record types automatically managed by
a18474e0980d1a9a44b73abfe1c3eea89089fa39Pascal Schmidt <span><strong class="command">dnssec-signzone</strong></span>, i.e. RRSIG, NSEC,
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt NSEC3 and NSEC3PARAM records. If smart signing
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt (<code class="option">-S</code>) is used, DNSKEY records are also
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt included. The resulting file can be included in the original
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt zone file with <span><strong class="command">$INCLUDE</strong></span>. This option
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt cannot be combined with <code class="option">-O raw</code>,
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt <code class="option">-O map</code>, or serial number updating.
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt </p></dd>
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt<dd>
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt<p>
85ea4336c34014b69f8e5e0cd38956fbec048008Pascal Schmidt When applicable, specifies the hardware to use for
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich cryptographic operations, such as a secure key store used
60ef7437c5c9462bc5287a001ea846a85da8cee5Christian Maeder for signing.
2ce581897091465f0d602e2e36c4ea687230855fChristian Maeder </p>
caf9cbd08ac84499a343bbd0eac79e9bb47a40e5Christian Maeder<p>
f7d16152baa03da85173e533b4c3f7d9df47ca3ePascal Schmidt When BIND is built with OpenSSL PKCS#11 support, this defaults
60ef7437c5c9462bc5287a001ea846a85da8cee5Christian Maeder to the string "pkcs11", which identifies an OpenSSL engine
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt that can drive a cryptographic accelerator or hardware service
16b0f1519de5f935907521dc0b77aadcc8a787cbPascal Schmidt module. When BIND is built with native PKCS#11 cryptography
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt (--enable-native-pkcs11), it defaults to the path of the PKCS#11
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt provider library specified via "--with-pkcs11".
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt </p>
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt</dd>
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt<dt><span class="term">-g</span></dt>
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt<dd><p>
f7d16152baa03da85173e533b4c3f7d9df47ca3ePascal Schmidt Generate DS records for child zones from
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt <code class="filename">dsset-</code> or <code class="filename">keyset-</code>
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt file. Existing DS records will be removed.
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt </p></dd>
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt<dd><p>
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt Key repository: Specify a directory to search for DNSSEC keys.
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt If not specified, defaults to the current directory.
f7d16152baa03da85173e533b4c3f7d9df47ca3ePascal Schmidt </p></dd>
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt<dt><span class="term">-k <em class="replaceable"><code>key</code></em></span></dt>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<dd><p>
85e024e5c36674af1683731f68b83b090faba402Pascal Schmidt Treat specified key as a key signing key ignoring any
85e024e5c36674af1683731f68b83b090faba402Pascal Schmidt key flags. This option may be specified multiple times.
85e024e5c36674af1683731f68b83b090faba402Pascal Schmidt </p></dd>
85e024e5c36674af1683731f68b83b090faba402Pascal Schmidt<dt><span class="term">-l <em class="replaceable"><code>domain</code></em></span></dt>
f7d16152baa03da85173e533b4c3f7d9df47ca3ePascal Schmidt<dd><p>
f7d16152baa03da85173e533b4c3f7d9df47ca3ePascal Schmidt Generate a DLV set in addition to the key (DNSKEY) and DS sets.
85e024e5c36674af1683731f68b83b090faba402Pascal Schmidt The domain is appended to the name of the records.
85e024e5c36674af1683731f68b83b090faba402Pascal Schmidt </p></dd>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<dt><span class="term">-M <em class="replaceable"><code>maxttl</code></em></span></dt>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich<dd><p>
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich Sets the maximum TTL for the signed zone.
e3c3e8934edda5b2a7c0d11e44fcfb38094dc80bKlaus Luettich Any TTL higher than <em class="replaceable"><code>maxttl</code></em> in the
b4d22cd5c6767285bcdc9db6ec0a6a9546746e12Pascal Schmidt 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><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="id2676321"></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="id2676468"></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="id2676496"></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>