98N/A - Copyright (C) 2004-2011 Internet Systems Consortium, Inc. ("ISC") 98N/A - Copyright (C) 2000-2003 Internet Software Consortium. 1088N/A - Permission to use, copy, modify, and/or distribute this software for any 98N/A - purpose with or without fee is hereby granted, provided that the above 98N/A - copyright notice and this permission notice appear in all copies. 919N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 919N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 919N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 919N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 919N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 919N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 919N/A - PERFORMANCE OF THIS SOFTWARE. 919N/A<
meta http-
equiv="Content-Type" content="text/html; charset=ISO-8859-1">
919N/A<
title>dnssec-signzone</
title>
919N/A<
meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
919N/A<
link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
98N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
98N/A<
div class="navheader">
98N/A<
table width="100%" summary="Navigation header">
493N/A<
tr><
th colspan="3" align="center"><
span class="application">dnssec-signzone</
span></
th></
tr>
98N/A<
td width="20%" align="left">
1179N/A<
th width="60%" align="center">Manual pages</
th>
98N/A<
div class="refentry" lang="en">
916N/A<
div class="refnamediv">
916N/A<
p><
span class="application">dnssec-signzone</
span> — DNSSEC zone signing tool</
p>
970N/A<
div class="refsynopsisdiv">
970N/A<
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>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">-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">-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>
970N/A<
div class="refsect1" lang="en">
970N/A<
a name="id2617966"></
a><
h2>DESCRIPTION</
h2>
970N/A<
p><
span><
strong class="command">dnssec-signzone</
strong></
span>
970N/A signs a zone. It generates
970N/A NSEC and RRSIG records and produces a signed version of the
970N/A zone. The security status of delegations from the signed zone
970N/A (that is, whether the child zones are secure or not) is
970N/A determined by the presence or absence of a
970N/A <
code class="filename">keyset</
code> file for each child zone.
970N/A<
div class="refsect1" lang="en">
970N/A<
a name="id2617986"></
a><
h2>OPTIONS</
h2>
970N/A<
div class="variablelist"><
dl>
970N/A<
dt><
span class="term">-a</
span></
dt>
970N/A Verify all generated signatures.
970N/A<
dt><
span class="term">-c <
em class="replaceable"><
code>class</
code></
em></
span></
dt>
1029N/A Specifies the DNS class of the zone.
1124N/A<
dt><
span class="term">-C</
span></
dt>
1124N/A Compatibility mode: Generate a
1124N/A <
code class="filename">keyset-<
em class="replaceable"><
code>zonename</
code></
em></
code>
1124N/A <
code class="filename">dsset-<
em class="replaceable"><
code>zonename</
code></
em></
code>
970N/A when signing a zone, for use by older versions of
98N/A <
span><
strong class="command">dnssec-signzone</
strong></
span>.
1124N/A<
dt><
span class="term">-d <
em class="replaceable"><
code>directory</
code></
em></
span></
dt>
1124N/A Look for <
code class="filename">dsset-</
code> or
1124N/A <
code class="filename">keyset-</
code> files in <
code class="option">directory</
code>.
1124N/A<
dt><
span class="term">-D</
span></
dt>
1124N/A Output only those record types automatically managed by
98N/A <
span><
strong class="command">dnssec-signzone</
strong></
span>,
i.e. RRSIG, NSEC,
493N/A NSEC3 and NSEC3PARAM records. If smart signing
98N/A (<
code class="option">-S</
code>) is used, DNSKEY records are also
970N/A included. The resulting file can be included in the original
970N/A zone file with <
span><
strong class="command">$INCLUDE</
strong></
span>. This option
970N/A cannot be combined with <
code class="option">-O raw</
code> or serial
970N/A<
dt><
span class="term">-E <
em class="replaceable"><
code>engine</
code></
em></
span></
dt>
1124N/A Uses a crypto hardware (OpenSSL engine) for the crypto operations
1003N/A it supports, for instance signing with private keys from
98N/A a secure key store. When compiled with PKCS#11 support
98N/A it defaults to pkcs11; the empty name resets it to no engine.
908N/A<
dt><
span class="term">-g</
span></
dt>
493N/A Generate DS records for child zones from
493N/A <
code class="filename">dsset-</
code> or <
code class="filename">keyset-</
code>
493N/A file. Existing DS records will be removed.
493N/A<
dt><
span class="term">-K <
em class="replaceable"><
code>directory</
code></
em></
span></
dt>
493N/A Key repository: Specify a directory to search for DNSSEC keys.
493N/A If not specified, defaults to the current directory.
705N/A<
dt><
span class="term">-k <
em class="replaceable"><
code>key</
code></
em></
span></
dt>
557N/A Treat specified key as a key signing key ignoring any
1176N/A key flags. This option may be specified multiple times.
965N/A<
dt><
span class="term">-l <
em class="replaceable"><
code>domain</
code></
em></
span></
dt>
965N/A Generate a DLV set in addition to the key (DNSKEY) and DS sets.
606N/A The domain is appended to the name of the records.
851N/A<
dt><
span class="term">-s <
em class="replaceable"><
code>start-time</
code></
em></
span></
dt>
851N/A Specify the date and time when the generated RRSIG records
851N/A become valid. This can be either an absolute or relative
851N/A time. An absolute start time is indicated by a number
851N/A in YYYYMMDDHHMMSS notation; 20000530144500 denotes
851N/A 14:45:00 UTC on May 30th, 2000. A relative start time is
98N/A indicated by +N, which is N seconds from the current time.
591N/A If no <
code class="option">start-time</
code> is specified, the current
963N/A time minus 1 hour (to allow for clock skew) is used.
910N/A<
dt><
span class="term">-e <
em class="replaceable"><
code>end-time</
code></
em></
span></
dt>
910N/A Specify the date and time when the generated RRSIG records
1097N/A expire. As with <
code class="option">start-time</
code>, an absolute
910N/A time is indicated in YYYYMMDDHHMMSS notation. A time relative
98N/A to the start time is indicated with +N, which is N seconds from
98N/A the start time. A time relative to the current time is
910N/A indicated with now+N. If no <
code class="option">end-time</
code> is
910N/A specified, 30 days from the start time is used as a default.
970N/A <
code class="option">end-time</
code> must be later than
1030N/A <
code class="option">start-time</
code>.
970N/A<
dt><
span class="term">-X <
em class="replaceable"><
code>extended end-time</
code></
em></
span></
dt>
1097N/A Specify the date and time when the generated RRSIG records
1097N/A for the DNSKEY RRset will expire. This is to be used in cases
1030N/A when the DNSKEY signatures need to persist longer than
1030N/A signatures on other records;
e.g., when the private component
910N/A of the KSK is kept offline and the KSK signature is to be
98N/A refreshed manually.
606N/A As with <
code class="option">start-time</
code>, an absolute
98N/A time is indicated in YYYYMMDDHHMMSS notation. A time relative
591N/A to the start time is indicated with +N, which is N seconds from
851N/A the start time. A time relative to the current time is
111N/A indicated with now+N. If no <
code class="option">extended end-time</
code> is
606N/A specified, the value of <
code class="option">end-time</
code> is used as
1088N/A the default. (<
code class="option">end-time</
code>, in turn, defaults to
1088N/A 30 days from the start time.) <
code class="option">extended end-time</
code>
1088N/A must be later than <
code class="option">start-time</
code>.
733N/A<
dt><
span class="term">-f <
em class="replaceable"><
code>output-file</
code></
em></
span></
dt>
963N/A The name of the output file containing the signed zone. The
851N/A default is to append <
code class="filename">.signed</
code> to
1088N/A<
dt><
span class="term">-h</
span></
dt>
98N/A Prints a short summary of the options and arguments to
851N/A <
span><
strong class="command">dnssec-signzone</
strong></
span>.
1097N/A<
dt><
span class="term">-i <
em class="replaceable"><
code>interval</
code></
em></
span></
dt>
851N/A When a previously-signed zone is passed as input, records
851N/A may be resigned. The <
code class="option">interval</
code> option
935N/A specifies the cycle interval as an offset from the current
606N/A time (in seconds). If a RRSIG record expires after the
935N/A cycle interval, it is retained. Otherwise, it is considered
935N/A to be expiring soon, and it will be replaced.
212N/A The default cycle interval is one quarter of the difference
98N/A between the signature end and start times. So if neither
98N/A <
code class="option">end-time</
code> or <
code class="option">start-time</
code>
98N/A are specified, <
span><
strong class="command">dnssec-signzone</
strong></
span>
182N/A signatures that are valid for 30 days, with a cycle
98N/A interval of 7.5 days. Therefore, if any existing RRSIG records
908N/A are due to expire in less than 7.5 days, they would be
963N/A<
dt><
span class="term">-I <
em class="replaceable"><
code>input-format</
code></
em></
span></
dt>
963N/A The format of the input zone file.
1030N/A Possible formats are <
span><
strong class="command">"text"</
strong></
span> (default)
970N/A and <
span><
strong class="command">"raw"</
strong></
span>.
1097N/A This option is primarily intended to be used for dynamic
1097N/A signed zones so that the dumped zone file in a non-text
970N/A format containing updates can be signed directly.
970N/A The use of this option does not make much sense for
970N/A<
dt><
span class="term">-j <
em class="replaceable"><
code>jitter</
code></
em></
span></
dt>
970N/A When signing a zone with a fixed signature lifetime, all
970N/A RRSIG records issued at the time of signing expires
970N/A simultaneously. If the zone is incrementally signed,
i.e. 970N/A a previously-signed zone is passed as input to the signer,
1026N/A all expired signatures have to be regenerated at about the
974N/A same time. The <
code class="option">jitter</
code> option specifies a
970N/A jitter window that will be used to randomize the signature
970N/A expire time, thus spreading incremental signature
974N/A Signature lifetime jitter also to some extent benefits
974N/A validators and servers by spreading out cache expiration,
970N/A i.e. if large numbers of RRSIGs don't expire at the same time
1026N/A from all caches there will be less congestion than if all
970N/A validators need to refetch at mostly the same time.
970N/A<
dt><
span class="term">-n <
em class="replaceable"><
code>ncpus</
code></
em></
span></
dt>
970N/A Specifies the number of threads to use. By default, one
970N/A thread is started for each detected CPU.
970N/A<
dt><
span class="term">-N <
em class="replaceable"><
code>soa-serial-format</
code></
em></
span></
dt>
970N/A The SOA serial number format of the signed zone.
970N/A Possible formats are <
span><
strong class="command">"keep"</
strong></
span> (default),
970N/A <
span><
strong class="command">"increment"</
strong></
span> and
970N/A <
span><
strong class="command">"unixtime"</
strong></
span>.
1003N/A<
div class="variablelist"><
dl>
1003N/A<
dt><
span class="term"><
span><
strong class="command">"keep"</
strong></
span></
span></
dt>
1003N/A<
dd><
p>Do not modify the SOA serial number.</
p></
dd>
1003N/A<
dt><
span class="term"><
span><
strong class="command">"increment"</
strong></
span></
span></
dt>
1003N/A<
dd><
p>Increment the SOA serial number using RFC 1982
970N/A<
dt><
span class="term"><
span><
strong class="command">"unixtime"</
strong></
span></
span></
dt>
970N/A<
dd><
p>Set the SOA serial number to the number of seconds
970N/A<
dt><
span class="term">-o <
em class="replaceable"><
code>origin</
code></
em></
span></
dt>
970N/A The zone origin. If not specified, the name of the zone file
970N/A is assumed to be the origin.
970N/A<
dt><
span class="term">-O <
em class="replaceable"><
code>output-format</
code></
em></
span></
dt>
970N/A The format of the output file containing the signed zone.
1030N/A Possible formats are <
span><
strong class="command">"text"</
strong></
span> (default)
1030N/A and <
span><
strong class="command">"raw"</
strong></
span>.
1030N/A<
dt><
span class="term">-p</
span></
dt>
1030N/A Use pseudo-random data when signing the zone. This is faster,
1030N/A but less secure, than using real random data. This option
1030N/A may be useful when signing large zones or when the entropy
1030N/A<
dt><
span class="term">-P</
span></
dt>
1030N/A Disable post sign verification tests.
1030N/A The post sign verification test ensures that for each algorithm
1030N/A in use there is at least one non revoked self signed KSK key,
1030N/A that all revoked KSK keys are self signed, and that all records
1030N/A in the zone are signed by the algorithm.
1030N/A This option skips these tests.
1030N/A<
dt><
span class="term">-R</
span></
dt>
1030N/A Remove signatures from keys that no longer exist.
1030N/A Normally, when a previously-signed zone is passed as input
1030N/A to the signer, and a DNSKEY record has been removed and
1030N/A replaced with a new one, signatures from the old key
1030N/A that are still within their validity period are retained.
1030N/A This allows the zone to continue to validate with cached
1030N/A copies of the old DNSKEY RRset. The <
code class="option">-R</
code> forces
1030N/A <
span><
strong class="command">dnssec-signzone</
strong></
span> to remove all orphaned
1030N/A<
dt><
span class="term">-r <
em class="replaceable"><
code>randomdev</
code></
em></
span></
dt>
1030N/A Specifies the source of randomness. If the operating
1030N/A or equivalent device, the default source of randomness
1030N/A is keyboard input. <
code class="filename">randomdev</
code>
1030N/A the name of a character device or file containing random
1030N/A data to be used instead of the default. The special value
1030N/A <
code class="filename">keyboard</
code> indicates that keyboard
<
dt><
span class="term">-S</
span></
dt>
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.
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
<
div class="variablelist"><
dl>
If no timing metadata has been set for the key, the key is
published in the zone and used to sign the zone.
If the key's publication date is set and is in the past, the
key is published in the zone.
If the key's activation date is set and in the past, the
key is published (regardless of publication date) and
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.
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.
<
dt><
span class="term">-T <
em class="replaceable"><
code>ttl</
code></
em></
span></
dt>
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.
<
dt><
span class="term">-t</
span></
dt>
Print statistics at completion.
<
dt><
span class="term">-u</
span></
dt>
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.
<
dt><
span class="term">-v <
em class="replaceable"><
code>level</
code></
em></
span></
dt>
Sets the debugging level.
<
dt><
span class="term">-x</
span></
dt>
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>.)
<
dt><
span class="term">-z</
span></
dt>
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>.)
<
dt><
span class="term">-3 <
em class="replaceable"><
code>salt</
code></
em></
span></
dt>
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.
<
dt><
span class="term">-H <
em class="replaceable"><
code>iterations</
code></
em></
span></
dt>
When generating an NSEC3 chain, use this many interations. The
<
dt><
span class="term">-A</
span></
dt>
When generating an NSEC3 chain set the OPTOUT flag on all
NSEC3 records and do not generate NSEC3 records for insecure
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.
<
dt><
span class="term">zonefile</
span></
dt>
The file containing the zone to be signed.
<
dt><
span class="term">key</
span></
dt>
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.
<
div class="refsect1" lang="en">
<
a name="id2672270"></
a><
h2>EXAMPLE</
h2>
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
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>).
In the above example, <
span><
strong class="command">dnssec-signzone</
strong></
span> creates
file should be referenced in a zone statement in a
This example re-signs a previously signed zone with default parameters.
The private keys are assumed to be in the current directory.
<
div class="refsect1" lang="en">
<
a name="id2672349"></
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>.
<
div class="refsect1" lang="en">
<
a name="id2672374"></
a><
h2>AUTHOR</
h2>
<
p><
span class="corpauthor">Internet Systems Consortium</
span>
<
table width="100%" summary="Navigation footer">
<
td width="40%" align="left">
<
td width="20%" align="center"><
a accesskey="u" href="Bv9ARM.ch10.html">Up</
a></
td>
<
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">named-checkconf</
span>