1N/A - Copyright (C) 2004-2011 Internet Systems Consortium, Inc. ("ISC") 1N/A - Copyright (C) 2000-2003 Internet Software Consortium. 1N/A - Permission to use, copy, modify, and/or distribute this software for any 1N/A - purpose with or without fee is hereby granted, provided that the above 1N/A - copyright notice and this permission notice appear in all copies. 1N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 1N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 1N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 1N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 1N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 1N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 1N/A - PERFORMANCE OF THIS SOFTWARE. 1N/A<
meta http-
equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1N/A<
title>dnssec-signzone</
title>
1N/A<
meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
1N/A<
link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
1N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
1N/A<
div class="navheader">
1N/A<
table width="100%" summary="Navigation header">
1N/A<
tr><
th colspan="3" align="center"><
span class="application">dnssec-signzone</
span></
th></
tr>
1N/A<
td width="20%" align="left">
1N/A<
th width="60%" align="center">Manual pages</
th>
1N/A<
div class="refentry" lang="en">
1N/A<
div class="refnamediv">
1N/A<
p><
span class="application">dnssec-signzone</
span> — DNSSEC zone signing tool</
p>
1N/A<
div class="refsynopsisdiv">
1N/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">-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 <
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</
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>
1N/A<
div class="refsect1" lang="en">
1N/A<
a name="id2617202"></
a><
h2>DESCRIPTION</
h2>
1N/A<
p><
span><
strong class="command">dnssec-signzone</
strong></
span>
1N/A signs a zone. It generates
1N/A NSEC and RRSIG records and produces a signed version of the
1N/A zone. The security status of delegations from the signed zone
1N/A (that is, whether the child zones are secure or not) is
1N/A determined by the presence or absence of a
1N/A <
code class="filename">keyset</
code> file for each child zone.
1N/A<
div class="refsect1" lang="en">
1N/A<
a name="id2617221"></
a><
h2>OPTIONS</
h2>
1N/A<
div class="variablelist"><
dl>
1N/A<
dt><
span class="term">-a</
span></
dt>
1N/A Verify all generated signatures.
1N/A<
dt><
span class="term">-c <
em class="replaceable"><
code>class</
code></
em></
span></
dt>
1N/A Specifies the DNS class of the zone.
1N/A<
dt><
span class="term">-C</
span></
dt>
1N/A Compatibility mode: Generate a
1N/A <
code class="filename">keyset-<
em class="replaceable"><
code>zonename</
code></
em></
code>
1N/A <
code class="filename">dsset-<
em class="replaceable"><
code>zonename</
code></
em></
code>
1N/A when signing a zone, for use by older versions of
1N/A <
span><
strong class="command">dnssec-signzone</
strong></
span>.
1N/A<
dt><
span class="term">-d <
em class="replaceable"><
code>directory</
code></
em></
span></
dt>
1N/A Look for <
code class="filename">dsset-</
code> or
1N/A <
code class="filename">keyset-</
code> files in <
code class="option">directory</
code>.
1N/A<
dt><
span class="term">-E <
em class="replaceable"><
code>engine</
code></
em></
span></
dt>
1N/A Uses a crypto hardware (OpenSSL engine) for the crypto operations
1N/A it supports, for instance signing with private keys from
1N/A a secure key store. When compiled with PKCS#11 support
1N/A it defaults to pkcs11; the empty name resets it to no engine.
1N/A<
dt><
span class="term">-g</
span></
dt>
1N/A Generate DS records for child zones from
1N/A <
code class="filename">dsset-</
code> or <
code class="filename">keyset-</
code>
1N/A file. Existing DS records will be removed.
1N/A<
dt><
span class="term">-K <
em class="replaceable"><
code>directory</
code></
em></
span></
dt>
1N/A Key repository: Specify a directory to search for DNSSEC keys.
1N/A If not specified, defaults to the current directory.
1N/A<
dt><
span class="term">-k <
em class="replaceable"><
code>key</
code></
em></
span></
dt>
1N/A Treat specified key as a key signing key ignoring any
1N/A key flags. This option may be specified multiple times.
1N/A<
dt><
span class="term">-l <
em class="replaceable"><
code>domain</
code></
em></
span></
dt>
1N/A Generate a DLV set in addition to the key (DNSKEY) and DS sets.
1N/A The domain is appended to the name of the records.
1N/A<
dt><
span class="term">-s <
em class="replaceable"><
code>start-time</
code></
em></
span></
dt>
1N/A Specify the date and time when the generated RRSIG records
1N/A become valid. This can be either an absolute or relative
1N/A time. An absolute start time is indicated by a number
1N/A in YYYYMMDDHHMMSS notation; 20000530144500 denotes
1N/A 14:45:00 UTC on May 30th, 2000. A relative start time is
1N/A indicated by +N, which is N seconds from the current time.
1N/A If no <
code class="option">start-time</
code> is specified, the current
1N/A time minus 1 hour (to allow for clock skew) is used.
1N/A<
dt><
span class="term">-e <
em class="replaceable"><
code>end-time</
code></
em></
span></
dt>
1N/A Specify the date and time when the generated RRSIG records
1N/A expire. As with <
code class="option">start-time</
code>, an absolute
1N/A time is indicated in YYYYMMDDHHMMSS notation. A time relative
1N/A to the start time is indicated with +N, which is N seconds from
1N/A the start time. A time relative to the current time is
1N/A indicated with now+N. If no <
code class="option">end-time</
code> is
1N/A specified, 30 days from the start time is used as a default.
1N/A <
code class="option">end-time</
code> must be later than
1N/A <
code class="option">start-time</
code>.
1N/A<
dt><
span class="term">-f <
em class="replaceable"><
code>output-file</
code></
em></
span></
dt>
1N/A The name of the output file containing the signed zone. The
1N/A default is to append <
code class="filename">.signed</
code> to
1N/A<
dt><
span class="term">-h</
span></
dt>
1N/A Prints a short summary of the options and arguments to
1N/A <
span><
strong class="command">dnssec-signzone</
strong></
span>.
1N/A<
dt><
span class="term">-i <
em class="replaceable"><
code>interval</
code></
em></
span></
dt>
1N/A When a previously-signed zone is passed as input, records
1N/A may be resigned. The <
code class="option">interval</
code> option
1N/A specifies the cycle interval as an offset from the current
1N/A time (in seconds). If a RRSIG record expires after the
1N/A cycle interval, it is retained. Otherwise, it is considered
1N/A to be expiring soon, and it will be replaced.
1N/A The default cycle interval is one quarter of the difference
1N/A between the signature end and start times. So if neither
1N/A <
code class="option">end-time</
code> or <
code class="option">start-time</
code>
1N/A are specified, <
span><
strong class="command">dnssec-signzone</
strong></
span>
1N/A signatures that are valid for 30 days, with a cycle
1N/A interval of 7.5 days. Therefore, if any existing RRSIG records
1N/A are due to expire in less than 7.5 days, they would be
1N/A<
dt><
span class="term">-I <
em class="replaceable"><
code>input-format</
code></
em></
span></
dt>
1N/A The format of the input zone file.
1N/A Possible formats are <
span><
strong class="command">"text"</
strong></
span> (default)
1N/A and <
span><
strong class="command">"raw"</
strong></
span>.
1N/A This option is primarily intended to be used for dynamic
1N/A signed zones so that the dumped zone file in a non-text
1N/A format containing updates can be signed directly.
1N/A The use of this option does not make much sense for
1N/A<
dt><
span class="term">-j <
em class="replaceable"><
code>jitter</
code></
em></
span></
dt>
1N/A When signing a zone with a fixed signature lifetime, all
1N/A RRSIG records issued at the time of signing expires
1N/A simultaneously. If the zone is incrementally signed,
i.e. 1N/A a previously-signed zone is passed as input to the signer,
1N/A all expired signatures have to be regenerated at about the
1N/A same time. The <
code class="option">jitter</
code> option specifies a
1N/A jitter window that will be used to randomize the signature
1N/A expire time, thus spreading incremental signature
1N/A regeneration over time.
1N/A Signature lifetime jitter also to some extent benefits
1N/A validators and servers by spreading out cache expiration,
1N/A i.e. if large numbers of RRSIGs don't expire at the same time
1N/A from all caches there will be less congestion than if all
1N/A validators need to refetch at mostly the same time.
1N/A<
dt><
span class="term">-n <
em class="replaceable"><
code>ncpus</
code></
em></
span></
dt>
1N/A Specifies the number of threads to use. By default, one
1N/A thread is started for each detected CPU.
1N/A<
dt><
span class="term">-N <
em class="replaceable"><
code>soa-serial-format</
code></
em></
span></
dt>
1N/A The SOA serial number format of the signed zone.
1N/A Possible formats are <
span><
strong class="command">"keep"</
strong></
span> (default),
1N/A <
span><
strong class="command">"increment"</
strong></
span> and
1N/A <
span><
strong class="command">"unixtime"</
strong></
span>.
1N/A<
div class="variablelist"><
dl>
1N/A<
dt><
span class="term"><
span><
strong class="command">"keep"</
strong></
span></
span></
dt>
1N/A<
dd><
p>Do not modify the SOA serial number.</
p></
dd>
1N/A<
dt><
span class="term"><
span><
strong class="command">"increment"</
strong></
span></
span></
dt>
1N/A<
dd><
p>Increment the SOA serial number using RFC 1982
1N/A arithmetics.</
p></
dd>
1N/A<
dt><
span class="term"><
span><
strong class="command">"unixtime"</
strong></
span></
span></
dt>
1N/A<
dd><
p>Set the SOA serial number to the number of seconds
1N/A since epoch.</
p></
dd>
1N/A<
dt><
span class="term">-o <
em class="replaceable"><
code>origin</
code></
em></
span></
dt>
1N/A The zone origin. If not specified, the name of the zone file
1N/A is assumed to be the origin.
1N/A<
dt><
span class="term">-O <
em class="replaceable"><
code>output-format</
code></
em></
span></
dt>
1N/A The format of the output file containing the signed zone.
1N/A Possible formats are <
span><
strong class="command">"text"</
strong></
span> (default)
1N/A and <
span><
strong class="command">"raw"</
strong></
span>.
1N/A<
dt><
span class="term">-p</
span></
dt>
1N/A Use pseudo-random data when signing the zone. This is faster,
1N/A but less secure, than using real random data. This option
1N/A may be useful when signing large zones or when the entropy
1N/A<
dt><
span class="term">-P</
span></
dt>
1N/A Disable post sign verification tests.
1N/A The post sign verification test ensures that for each algorithm
1N/A in use there is at least one non revoked self signed KSK key,
1N/A that all revoked KSK keys are self signed, and that all records
1N/A in the zone are signed by the algorithm.
1N/A This option skips these tests.
1N/A<
dt><
span class="term">-r <
em class="replaceable"><
code>randomdev</
code></
em></
span></
dt>
1N/A Specifies the source of randomness. If the operating
1N/A system does not provide a <
code class="filename">/
dev/
random</
code>
1N/A or equivalent device, the default source of randomness
1N/A is keyboard input. <
code class="filename">randomdev</
code>
1N/A the name of a character device or file containing random
1N/A data to be used instead of the default. The special value
1N/A <
code class="filename">keyboard</
code> indicates that keyboard
1N/A input should be used.
1N/A<
dt><
span class="term">-S</
span></
dt>
1N/A Smart signing: Instructs <
span><
strong class="command">dnssec-signzone</
strong></
span> to
1N/A search the key repository for keys that match the zone being
1N/A signed, and to include them in the zone if appropriate.
1N/A When a key is found, its timing metadata is examined to
1N/A determine how it should be used, according to the following
1N/A rules. Each successive rule takes priority over the prior
1N/A<
div class="variablelist"><
dl>
1N/A If no timing metadata has been set for the key, the key is
1N/A published in the zone and used to sign the zone.
1N/A If the key's publication date is set and is in the past, the
1N/A key is published in the zone.
1N/A If the key's activation date is set and in the past, the
1N/A key is published (regardless of publication date) and
1N/A used to sign the zone.
1N/A If the key's revocation date is set and in the past, and the
1N/A key is published, then the key is revoked, and the revoked key
1N/A is used to sign the zone.
1N/A If either of the key's unpublication or deletion dates are set
1N/A and in the past, the key is NOT published or used to sign the
1N/A zone, regardless of any other metadata.
1N/A<
dt><
span class="term">-T <
em class="replaceable"><
code>ttl</
code></
em></
span></
dt>
1N/A Specifies the TTL to be used for new DNSKEY records imported
1N/A into the zone from the key repository. If not specified,
1N/A the default is the minimum TTL value from the zone's SOA
1N/A record. This option is ignored when signing without
1N/A <
code class="option">-S</
code>, since DNSKEY records are not imported
1N/A from the key repository in that case. It is also ignored if
1N/A there are any pre-existing DNSKEY records at the zone apex,
1N/A in which case new records' TTL values will be set to match
1N/A<
dt><
span class="term">-t</
span></
dt>
1N/A Print statistics at completion.
1N/A<
dt><
span class="term">-u</
span></
dt>
1N/A zone. With this option, a zone signed with NSEC can be
1N/A switched to NSEC3, or a zone signed with NSEC3 can
1N/A be switch to NSEC or to NSEC3 with different parameters.
1N/A Without this option, <
span><
strong class="command">dnssec-signzone</
strong></
span> will
1N/A retain the existing chain when re-signing.
1N/A<
dt><
span class="term">-v <
em class="replaceable"><
code>level</
code></
em></
span></
dt>
1N/A Sets the debugging level.
1N/A<
dt><
span class="term">-x</
span></
dt>
1N/A Only sign the DNSKEY RRset with key-signing keys, and omit
1N/A signatures from zone-signing keys. (This is similar to the
1N/A <
span><
strong class="command">dnssec-dnskey-kskonly yes;</
strong></
span> zone option in
1N/A <
span><
strong class="command">named</
strong></
span>.)
1N/A<
dt><
span class="term">-z</
span></
dt>
1N/A Ignore KSK flag on key when determining what to sign. This
1N/A causes KSK-flagged keys to sign all records, not just the
1N/A DNSKEY RRset. (This is similar to the
1N/A <
span><
strong class="command">update-check-ksk no;</
strong></
span> zone option in
1N/A <
span><
strong class="command">named</
strong></
span>.)
1N/A<
dt><
span class="term">-3 <
em class="replaceable"><
code>salt</
code></
em></
span></
dt>
1N/A Generate an NSEC3 chain with the given hex encoded salt.
1N/A A dash (<
em class="replaceable"><
code>salt</
code></
em>) can
1N/A be used to indicate that no salt is to be used when generating the NSEC3 chain.
1N/A<
dt><
span class="term">-H <
em class="replaceable"><
code>iterations</
code></
em></
span></
dt>
1N/A When generating an NSEC3 chain, use this many interations. The
1N/A<
dt><
span class="term">-A</
span></
dt>
1N/A When generating an NSEC3 chain set the OPTOUT flag on all
1N/A NSEC3 records and do not generate NSEC3 records for insecure
1N/A Using this option twice (
i.e., <
code class="option">-AA</
code>)
1N/A turns the OPTOUT flag off for all records. This is useful
1N/A when using the <
code class="option">-u</
code> option to modify an NSEC3
1N/A chain which previously had OPTOUT set.
1N/A<
dt><
span class="term">zonefile</
span></
dt>
1N/A The file containing the zone to be signed.
1N/A<
dt><
span class="term">key</
span></
dt>
1N/A Specify which keys should be used to sign the zone. If
1N/A no keys are specified, then the zone will be examined
1N/A for DNSKEY records at the zone apex. If these are found and
1N/A there are matching private keys, in the current directory,
1N/A then these will be used for signing.
1N/A<
div class="refsect1" lang="en">
1N/A<
a name="id2671269"></
a><
h2>EXAMPLE</
h2>
1N/A The following command signs the <
strong class="userinput"><
code>
example.com</
code></
strong>
1N/A zone with the DSA key generated by <
span><
strong class="command">dnssec-keygen</
strong></
span>
1N/A (
Kexample.com.+003+17247). Because the <
span><
strong class="command">-S</
strong></
span> option
1N/A is not being used, the zone's keys must be in the master file
1N/A for <
code class="filename">dsset</
code> files, in the current directory,
1N/A so that DS records can be imported from them (<
span><
strong class="command">-g</
strong></
span>).
1N/A In the above example, <
span><
strong class="command">dnssec-signzone</
strong></
span> creates
1N/A file should be referenced in a zone statement in a
1N/A This example re-signs a previously signed zone with default parameters.
1N/A The private keys are assumed to be in the current directory.
1N/A<
div class="refsect1" lang="en">
1N/A<
a name="id2671348"></
a><
h2>SEE ALSO</
h2>
1N/A<
p><
span class="citerefentry"><
span class="refentrytitle">dnssec-keygen</
span>(8)</
span>,
1N/A <
em class="citetitle">BIND 9 Administrator Reference Manual</
em>,
1N/A <
em class="citetitle">RFC 4033</
em>.
1N/A<
div class="refsect1" lang="en">
1N/A<
a name="id2671372"></
a><
h2>AUTHOR</
h2>
1N/A<
p><
span class="corpauthor">Internet Systems Consortium</
span>
1N/A<
div class="navfooter">
1N/A<
table width="100%" summary="Navigation footer">
1N/A<
td width="40%" align="left">
1N/A<
td width="40%" align="left" valign="top">
1N/A<
span class="application">dnssec-settime</
span>�</
td>
1N/A<
td width="20%" align="center"><
a accesskey="h" href="Bv9ARM.html">Home</
a></
td>
1N/A<
td width="40%" align="right" valign="top">�<
span class="application">named-checkconf</
span>