dnssec-signzone.html revision d71e2e0c61df16ff37c9934c371a4a60c08974f7
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<!--
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC")
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - Copyright (C) 2000-2003 Internet Software Consortium.
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte -
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - Permission to use, copy, modify, and distribute this software for any
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - purpose with or without fee is hereby granted, provided that the above
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - copyright notice and this permission notice appear in all copies.
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte -
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte - PERFORMANCE OF THIS SOFTWARE.
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte-->
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<!-- $Id: dnssec-signzone.html,v 1.31 2007/05/09 03:33:50 marka Exp $ -->
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<html>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<head>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<title>dnssec-signzone</title>
24fe0b3bf671e123467ce1df0b67cadd3614c8e4jmcp<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte</head>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en">
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<a name="man.dnssec-signzone"></a><div class="titlepage"></div>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<div class="refnamediv">
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<h2>Name</h2>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<p><span class="application">dnssec-signzone</span> &#8212; DNSSEC zone signing tool</p>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte</div>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<div class="refsynopsisdiv">
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<h2>Synopsis</h2>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<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">-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>key</code></em></code>] [<code class="option">-l <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">-r <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-s <em class="replaceable"><code>start-time</code></em></code>] [<code class="option">-t</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-z</code>] {zonefile} [key...]</p></div>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte</div>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<div class="refsect1" lang="en">
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<a name="id2543526"></a><h2>DESCRIPTION</h2>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<p><span><strong class="command">dnssec-signzone</strong></span>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte signs a zone. It generates
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte NSEC and RRSIG records and produces a signed version of the
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte zone. The security status of delegations from the signed zone
7014882c6a3672fd0e5d60200af8643ae53c5928Richard Lowe (that is, whether the child zones are secure or not) is
7014882c6a3672fd0e5d60200af8643ae53c5928Richard Lowe determined by the presence or absence of a
7014882c6a3672fd0e5d60200af8643ae53c5928Richard Lowe <code class="filename">keyset</code> file for each child zone.
7014882c6a3672fd0e5d60200af8643ae53c5928Richard Lowe </p>
7014882c6a3672fd0e5d60200af8643ae53c5928Richard Lowe</div>
7014882c6a3672fd0e5d60200af8643ae53c5928Richard Lowe<div class="refsect1" lang="en">
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<a name="id2543541"></a><h2>OPTIONS</h2>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<div class="variablelist"><dl>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dt><span class="term">-a</span></dt>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dd><p>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte Verify all generated signatures.
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte </p></dd>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dd><p>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte Specifies the DNS class of the zone.
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte </p></dd>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dt><span class="term">-k <em class="replaceable"><code>key</code></em></span></dt>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dd><p>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte Treat specified key as a key signing key ignoring any
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte key flags. This option may be specified multiple times.
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte </p></dd>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dt><span class="term">-l <em class="replaceable"><code>domain</code></em></span></dt>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dd><p>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte Generate a DLV set in addition to the key (DNSKEY) and DS sets.
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte The domain is appended to the name of the records.
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte </p></dd>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dt><span class="term">-d <em class="replaceable"><code>directory</code></em></span></dt>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dd><p>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte Look for <code class="filename">keyset</code> files in
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte <code class="option">directory</code> as the directory
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte </p></dd>
fcf3ce441efd61da9bb2884968af01cb7c1452ccJohn Forte<dt><span class="term">-g</span></dt>
<dd><p>
Generate DS records for child zones from keyset files.
Existing DS records will be removed.
</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.
</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.
</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">-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)
and <span><strong class="command">"raw"</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">-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> and
<span><strong class="command">"unixtime"</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>
</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)
and <span><strong class="command">"raw"</strong></span>.
</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">-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">-t</span></dt>
<dd><p>
Print statistics at completion.
</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">-z</span></dt>
<dd><p>
Ignore KSK flag on key when determining what to sign.
</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="id2544327"></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). The zone's keys must be in the master
file (<code class="filename">db.example.com</code>). This invocation looks
for <code class="filename">keyset</code> files, in the current directory,
so that DS records can be generated 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="id2544378"></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 2535</em>.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2544403"></a><h2>AUTHOR</h2>
<p><span class="corpauthor">Internet Systems Consortium</span>
</p>
</div>
</div></body>
</html>