man.dnssec-keygen.html revision 990d0e893f5b70e735cdf990af66e9ec6e91fa78
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<!--
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen - Copyright (C) 2004-2014 Internet Systems Consortium, Inc. ("ISC")
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen - Copyright (C) 2000-2003 Internet Software Consortium.
de62ce819d59a529530da4b57be1b8d6dad13d6bTimo Sirainen -
a8fe899601735459641edae975c0fa08be8482e2Timo Sirainen - Permission to use, copy, modify, and/or distribute this software for any
a8fe899601735459641edae975c0fa08be8482e2Timo Sirainen - purpose with or without fee is hereby granted, provided that the above
de0971aff3009fe6906c3631e8322908658a5e93Stephan Bosch - copyright notice and this permission notice appear in all copies.
dbffb9e8b87b771851700a1acc353aa62b5ab7d7Timo Sirainen -
629cb309f6f1bfce4ce0037c0ef089b66281f482Timo Sirainen - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
629cb309f6f1bfce4ce0037c0ef089b66281f482Timo Sirainen - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
3d7828efd92ecc0d08049f727d9be0154d1d681bStephan Bosch - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
44f3f472a49078312432b785fddcfe7b95928391Timo Sirainen - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen - PERFORMANCE OF THIS SOFTWARE.
44f3f472a49078312432b785fddcfe7b95928391Timo Sirainen-->
44f3f472a49078312432b785fddcfe7b95928391Timo Sirainen<!-- $Id$ -->
44f3f472a49078312432b785fddcfe7b95928391Timo Sirainen<html>
dbffb9e8b87b771851700a1acc353aa62b5ab7d7Timo Sirainen<head>
4ee00532a265bdfb38539d811fcd12d51210ac35Timo Sirainen<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
44f3f472a49078312432b785fddcfe7b95928391Timo Sirainen<title>dnssec-keygen</title>
44f3f472a49078312432b785fddcfe7b95928391Timo Sirainen<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<link rel="prev" href="man.dnssec-keyfromlabel.html" title="dnssec-keyfromlabel">
0f72f253d5a117dad2f28b2ce336190a5e6b79c8Stephan Bosch<link rel="next" href="man.dnssec-revoke.html" title="dnssec-revoke">
44f3f472a49078312432b785fddcfe7b95928391Timo Sirainen</head>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
6b6011c2242e470b41316f92512b282b5e306dacTimo Sirainen<div class="navheader">
6b6011c2242e470b41316f92512b282b5e306dacTimo Sirainen<table width="100%" summary="Navigation header">
6b6011c2242e470b41316f92512b282b5e306dacTimo Sirainen<tr><th colspan="3" align="center"><span class="application">dnssec-keygen</span></th></tr>
f41f6294f438bd16a35be64cef3bc90d2b66e0eaStephan Bosch<tr>
4afaedfcbd43896befbe1fd5c10eba42246f3fdeTimo Sirainen<td width="20%" align="left">
eed03830015b7138b9d4522e72bef650aa24b45fTimo Sirainen<a accesskey="p" href="man.dnssec-keyfromlabel.html">Prev</a>�</td>
eed03830015b7138b9d4522e72bef650aa24b45fTimo Sirainen<th width="60%" align="center">Manual pages</th>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-revoke.html">Next</a>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen</td>
a77f136d3603a36f6cdd2e3685a5b18dd3712d79Stephan Bosch</tr>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen</table>
3d7828efd92ecc0d08049f727d9be0154d1d681bStephan Bosch<hr>
de0971aff3009fe6906c3631e8322908658a5e93Stephan Bosch</div>
de0971aff3009fe6906c3631e8322908658a5e93Stephan Bosch<div class="refentry" lang="en">
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<a name="man.dnssec-keygen"></a><div class="titlepage"></div>
a77f136d3603a36f6cdd2e3685a5b18dd3712d79Stephan Bosch<div class="refnamediv">
3d7828efd92ecc0d08049f727d9be0154d1d681bStephan Bosch<h2>Name</h2>
de0971aff3009fe6906c3631e8322908658a5e93Stephan Bosch<p><span class="application">dnssec-keygen</span> &#8212; DNSSEC key generation tool</p>
de0971aff3009fe6906c3631e8322908658a5e93Stephan Bosch</div>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<div class="refsynopsisdiv">
a77f136d3603a36f6cdd2e3685a5b18dd3712d79Stephan Bosch<h2>Synopsis</h2>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<div class="cmdsynopsis"><p><code class="command">dnssec-keygen</code> [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>] [<code class="option">-b <em class="replaceable"><code>keysize</code></em></code>] [<code class="option">-n <em class="replaceable"><code>nametype</code></em></code>] [<code class="option">-3</code>] [<code class="option">-A <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-C</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] [<code class="option">-f <em class="replaceable"><code>flag</code></em></code>] [<code class="option">-G</code>] [<code class="option">-g <em class="replaceable"><code>generator</code></em></code>] [<code class="option">-h</code>] [<code class="option">-I <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>] [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-L <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-k</code>] [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-p <em class="replaceable"><code>protocol</code></em></code>] [<code class="option">-q</code>] [<code class="option">-R <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-r <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-S <em class="replaceable"><code>key</code></em></code>] [<code class="option">-s <em class="replaceable"><code>strength</code></em></code>] [<code class="option">-t <em class="replaceable"><code>type</code></em></code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-z</code>] {name}</p></div>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen</div>
a77f136d3603a36f6cdd2e3685a5b18dd3712d79Stephan Bosch<div class="refsect1" lang="en">
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<a name="id2619364"></a><h2>DESCRIPTION</h2>
2ef5254ab6b446b93ce7733bc96eeefa6f731ee4Timo Sirainen<p><span><strong class="command">dnssec-keygen</strong></span>
2ef5254ab6b446b93ce7733bc96eeefa6f731ee4Timo Sirainen generates keys for DNSSEC (Secure DNS), as defined in RFC 2535
2ef5254ab6b446b93ce7733bc96eeefa6f731ee4Timo Sirainen and RFC 4034. It can also generate keys for use with
2ef5254ab6b446b93ce7733bc96eeefa6f731ee4Timo Sirainen TSIG (Transaction Signatures) as defined in RFC 2845, or TKEY
2ef5254ab6b446b93ce7733bc96eeefa6f731ee4Timo Sirainen (Transaction Key) as defined in RFC 2930.
12e28ffc2655b6d0efce628eb7d93fa74fbd345bTimo Sirainen </p>
12e28ffc2655b6d0efce628eb7d93fa74fbd345bTimo Sirainen<p>
291f1e54dcb8c7f38e5b78afc1eaf518e3756692Timo Sirainen The <code class="option">name</code> of the key is specified on the command
b9dce659b9135c87c7708b2bb0f14e8742db7e15Timo Sirainen line. For DNSSEC keys, this must match the name of the zone for
b9dce659b9135c87c7708b2bb0f14e8742db7e15Timo Sirainen which the key is being generated.
b9dce659b9135c87c7708b2bb0f14e8742db7e15Timo Sirainen </p>
b9dce659b9135c87c7708b2bb0f14e8742db7e15Timo Sirainen</div>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<div class="refsect1" lang="en">
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<a name="id2619384"></a><h2>OPTIONS</h2>
2ef5254ab6b446b93ce7733bc96eeefa6f731ee4Timo Sirainen<div class="variablelist"><dl>
6682872f15fc74c1aa8898d4dc5745ff6a5dc51eTimo Sirainen<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
6682872f15fc74c1aa8898d4dc5745ff6a5dc51eTimo Sirainen<dd>
6cc815e209fa75989ad2a309119d4f286a6ea00fTimo Sirainen<p>
6cc815e209fa75989ad2a309119d4f286a6ea00fTimo Sirainen Selects the cryptographic algorithm. For DNSSEC keys, the value
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen of <code class="option">algorithm</code> must be one of RSAMD5, RSASHA1,
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen ECDSAP256SHA256 or ECDSAP384SHA384.
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen For TSIG/TKEY, the value must
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen be DH (Diffie Hellman), HMAC-MD5, HMAC-SHA1, HMAC-SHA224,
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen HMAC-SHA256, HMAC-SHA384, or HMAC-SHA512. These values are
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen case insensitive.
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen </p>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen<p>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen If no algorithm is specified, then RSASHA1 will be used by
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen default, unless the <code class="option">-3</code> option is specified,
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen in which case NSEC3RSASHA1 will be used instead. (If
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen <code class="option">-3</code> is used and an algorithm is specified,
6b6011c2242e470b41316f92512b282b5e306dacTimo Sirainen that algorithm will be checked for compatibility with NSEC3.)
6b6011c2242e470b41316f92512b282b5e306dacTimo Sirainen </p>
6b6011c2242e470b41316f92512b282b5e306dacTimo Sirainen<p>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen algorithm, and DSA is recommended. For TSIG, HMAC-MD5 is
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen mandatory.
3d7828efd92ecc0d08049f727d9be0154d1d681bStephan Bosch </p>
3d7828efd92ecc0d08049f727d9be0154d1d681bStephan Bosch<p>
3d7828efd92ecc0d08049f727d9be0154d1d681bStephan Bosch Note 2: DH, HMAC-MD5, and HMAC-SHA1 through HMAC-SHA512
3d7828efd92ecc0d08049f727d9be0154d1d681bStephan Bosch automatically set the -T KEY option.
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen </p>
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen</dd>
44f3f472a49078312432b785fddcfe7b95928391Timo Sirainen<dt><span class="term">-b <em class="replaceable"><code>keysize</code></em></span></dt>
44f3f472a49078312432b785fddcfe7b95928391Timo Sirainen<dd>
44f3f472a49078312432b785fddcfe7b95928391Timo Sirainen<p>
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen Specifies the number of bits in the key. The choice of key
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen size depends on the algorithm used. RSA keys must be
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen between 512 and 2048 bits. Diffie Hellman keys must be between
f9db221d0793f05c4631885e71f98145428a7e1bTimo Sirainen 128 and 4096 bits. DSA keys must be between 512 and 1024
258adfa09081ea8600a39759d486e678b5aa5f60Timo Sirainen bits and an exact multiple of 64. HMAC keys must be
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen between 1 and 512 bits. Elliptic curve algorithms don't need
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen this parameter.
a10ed8c47534b4c6b6bf2711ccfe577e720a47b4Timo Sirainen </p>
21fdf5394fbc307673b6c4b33f2497751a9ca1feTimo Sirainen<p>
21fdf5394fbc307673b6c4b33f2497751a9ca1feTimo Sirainen The key size does not need to be specified if using a default
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen algorithm. The default key size is 1024 bits for zone signing
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen keys (ZSK's) and 2048 bits for key signing keys (KSK's,
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen generated with <code class="option">-f KSK</code>). However, if an
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen algorithm is explicitly specified with the <code class="option">-a</code>,
92e6bb6497f8c9d57bff334a5c9f31bc2f040394Timo Sirainen then there is no default key size, and the <code class="option">-b</code>
92e6bb6497f8c9d57bff334a5c9f31bc2f040394Timo Sirainen must be used.
92e6bb6497f8c9d57bff334a5c9f31bc2f040394Timo Sirainen </p>
92e6bb6497f8c9d57bff334a5c9f31bc2f040394Timo Sirainen</dd>
eed56fe22f1fc61f2003d5e66373d03dacbc9aaaTimo Sirainen<dt><span class="term">-n <em class="replaceable"><code>nametype</code></em></span></dt>
eed56fe22f1fc61f2003d5e66373d03dacbc9aaaTimo Sirainen<dd><p>
eed56fe22f1fc61f2003d5e66373d03dacbc9aaaTimo Sirainen Specifies the owner type of the key. The value of
58c61ac5650583d21c891e61e051c614290d31fbTimo Sirainen <code class="option">nametype</code> must either be ZONE (for a DNSSEC
zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
a host (KEY)),
USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
These values are case insensitive. Defaults to ZONE for DNSKEY
generation.
</p></dd>
<dt><span class="term">-3</span></dt>
<dd><p>
Use an NSEC3-capable algorithm to generate a DNSSEC key.
If this option is used and no algorithm is explicitly
set on the command line, NSEC3RSASHA1 will be used by
default. Note that RSASHA256, RSASHA512, ECCGOST,
ECDSAP256SHA256 and ECDSAP384SHA384 algorithms
are NSEC3-capable.
</p></dd>
<dt><span class="term">-C</span></dt>
<dd><p>
Compatibility mode: generates an old-style key, without
any metadata. By default, <span><strong class="command">dnssec-keygen</strong></span>
will include the key's creation date in the metadata stored
with the private key, and other dates may be set there as well
(publication date, activation date, etc). Keys that include
this data may be incompatible with older versions of BIND; the
<code class="option">-C</code> option suppresses them.
</p></dd>
<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
<dd><p>
Indicates that the DNS record containing the key should have
the specified class. If not specified, class IN is used.
</p></dd>
<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
<dd><p>
Uses a crypto hardware (OpenSSL engine) for random number
and, when supported, key generation. When compiled with PKCS#11
support it defaults to pkcs11; the empty name resets it to
no engine.
</p></dd>
<dt><span class="term">-f <em class="replaceable"><code>flag</code></em></span></dt>
<dd><p>
Set the specified flag in the flag field of the KEY/DNSKEY record.
The only recognized flags are KSK (Key Signing Key) and REVOKE.
</p></dd>
<dt><span class="term">-G</span></dt>
<dd><p>
Generate a key, but do not publish it or sign with it. This
option is incompatible with -P and -A.
</p></dd>
<dt><span class="term">-g <em class="replaceable"><code>generator</code></em></span></dt>
<dd><p>
If generating a Diffie Hellman key, use this generator.
Allowed values are 2 and 5. If no generator
is specified, a known prime from RFC 2539 will be used
if possible; otherwise the default is 2.
</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-keygen</strong></span>.
</p></dd>
<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
<dd><p>
Sets the directory in which the key files are to be written.
</p></dd>
<dt><span class="term">-k</span></dt>
<dd><p>
Deprecated in favor of -T KEY.
</p></dd>
<dt><span class="term">-L <em class="replaceable"><code>ttl</code></em></span></dt>
<dd><p>
Sets the default TTL to use for this key when it is converted
into a DNSKEY RR. If the key is imported into a zone,
this is the TTL that will be used for it, unless there was
already a DNSKEY RRset in place, in which case the existing TTL
would take precedence. Setting the default TTL to
<code class="literal">0</code> or <code class="literal">none</code> removes it.
</p></dd>
<dt><span class="term">-p <em class="replaceable"><code>protocol</code></em></span></dt>
<dd><p>
Sets the protocol value for the generated key. The protocol
is a number between 0 and 255. The default is 3 (DNSSEC).
Other possible values for this argument are listed in
RFC 2535 and its successors.
</p></dd>
<dt><span class="term">-q</span></dt>
<dd><p>
Quiet mode: Suppresses unnecessary output, including
progress indication. Without this option, when
<span><strong class="command">dnssec-keygen</strong></span> is run interactively
to generate an RSA or DSA key pair, it will print a string
of symbols to <code class="filename">stderr</code> indicating the
progress of the key generation. A '.' indicates that a
random number has been found which passed an initial
sieve test; '+' means a number has passed a single
round of the Miller-Rabin primality test; a space
means that the number has passed all the tests and is
a satisfactory key.
</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 <em class="replaceable"><code>key</code></em></span></dt>
<dd><p>
Create a new key which is an explicit successor to an
existing key. The name, algorithm, size, and type of the
key will be set to match the existing key. The activation
date of the new key will be set to the inactivation date of
the existing one. The publication date will be set to the
activation date minus the prepublication interval, which
defaults to 30 days.
</p></dd>
<dt><span class="term">-s <em class="replaceable"><code>strength</code></em></span></dt>
<dd><p>
Specifies the strength value of the key. The strength is
a number between 0 and 15, and currently has no defined
purpose in DNSSEC.
</p></dd>
<dt><span class="term">-T <em class="replaceable"><code>rrtype</code></em></span></dt>
<dd>
<p>
Specifies the resource record type to use for the key.
<code class="option">rrtype</code> must be either DNSKEY or KEY. The
default is DNSKEY when using a DNSSEC algorithm, but it can be
overridden to KEY for use with SIG(0).
</p>
<p>
</p>
<p>
Using any TSIG algorithm (HMAC-* or DH) forces this option
to KEY.
</p>
</dd>
<dt><span class="term">-t <em class="replaceable"><code>type</code></em></span></dt>
<dd><p>
Indicates the use of the key. <code class="option">type</code> must be
one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF. The default
is AUTHCONF. AUTH refers to the ability to authenticate
data, and CONF the ability to encrypt data.
</p></dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
<dd><p>
Sets the debugging level.
</p></dd>
</dl></div>
</div>
<div class="refsect1" lang="en">
<a name="id2671319"></a><h2>TIMING OPTIONS</h2>
<p>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
an offset from the present time. For convenience, if such an offset
is followed by one of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi',
then the offset is computed in years (defined as 365 24-hour days,
ignoring leap years), months (defined as 30 24-hour days), weeks,
days, hours, or minutes, respectively. Without a suffix, the offset
is computed in seconds.
</p>
<div class="variablelist"><dl>
<dt><span class="term">-P <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
Sets the date on which a key is to be published to the zone.
After that date, the key will be included in the zone but will
not be used to sign it. If not set, and if the -G option has
not been used, the default is "now".
</p></dd>
<dt><span class="term">-A <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
Sets the date on which the key is to be activated. After that
date, the key will be included in the zone and used to sign
it. If not set, and if the -G option has not been used, the
default is "now".
</p></dd>
<dt><span class="term">-R <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
Sets the date on which the key is to be revoked. After that
date, the key will be flagged as revoked. It will be included
in the zone and will be used to sign it.
</p></dd>
<dt><span class="term">-I <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
Sets the date on which the key is to be retired. After that
date, the key will still be included in the zone, but it
will not be used to sign it.
</p></dd>
<dt><span class="term">-D <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
Sets the date on which the key is to be deleted. After that
date, the key will no longer be included in the zone. (It
may remain in the key repository, however.)
</p></dd>
<dt><span class="term">-i <em class="replaceable"><code>interval</code></em></span></dt>
<dd>
<p>
Sets the prepublication interval for a key. If set, then
the publication and activation dates must be separated by at least
this much time. If the activation date is specified but the
publication date isn't, then the publication date will default
to this much time before the activation date; conversely, if
the publication date is specified but activation date isn't,
then activation will be set to this much time after publication.
</p>
<p>
If the key is being created as an explicit successor to another
key, then the default prepublication interval is 30 days;
otherwise it is zero.
</p>
<p>
As with date offsets, if the argument is followed by one of
the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the
interval is measured in years, months, weeks, days, hours,
or minutes, respectively. Without a suffix, the interval is
measured in seconds.
</p>
</dd>
</dl></div>
</div>
<div class="refsect1" lang="en">
<a name="id2671509"></a><h2>GENERATED KEYS</h2>
<p>
When <span><strong class="command">dnssec-keygen</strong></span> completes
successfully,
it prints a string of the form <code class="filename">Knnnn.+aaa+iiiii</code>
to the standard output. This is an identification string for
the key it has generated.
</p>
<div class="itemizedlist"><ul type="disc">
<li><p><code class="filename">nnnn</code> is the key name.
</p></li>
<li><p><code class="filename">aaa</code> is the numeric representation
of the
algorithm.
</p></li>
<li><p><code class="filename">iiiii</code> is the key identifier (or
footprint).
</p></li>
</ul></div>
<p><span><strong class="command">dnssec-keygen</strong></span>
creates two files, with names based
on the printed string. <code class="filename">Knnnn.+aaa+iiiii.key</code>
contains the public key, and
<code class="filename">Knnnn.+aaa+iiiii.private</code> contains the
private
key.
</p>
<p>
The <code class="filename">.key</code> file contains a DNS KEY record
that
can be inserted into a zone file (directly or with a $INCLUDE
statement).
</p>
<p>
The <code class="filename">.private</code> file contains
algorithm-specific
fields. For obvious security reasons, this file does not have
general read permission.
</p>
<p>
Both <code class="filename">.key</code> and <code class="filename">.private</code>
files are generated for symmetric encryption algorithms such as
HMAC-MD5, even though the public and private key are equivalent.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2671685"></a><h2>EXAMPLE</h2>
<p>
To generate a 768-bit DSA key for the domain
<strong class="userinput"><code>example.com</code></strong>, the following command would be
issued:
</p>
<p><strong class="userinput"><code>dnssec-keygen -a DSA -b 768 -n ZONE example.com</code></strong>
</p>
<p>
The command would print a string of the form:
</p>
<p><strong class="userinput"><code>Kexample.com.+003+26160</code></strong>
</p>
<p>
In this example, <span><strong class="command">dnssec-keygen</strong></span> creates
the files <code class="filename">Kexample.com.+003+26160.key</code>
and
<code class="filename">Kexample.com.+003+26160.private</code>.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2671741"></a><h2>SEE ALSO</h2>
<p><span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 2539</em>,
<em class="citetitle">RFC 2845</em>,
<em class="citetitle">RFC 4034</em>.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2671772"></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-keyfromlabel.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-revoke.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">dnssec-keyfromlabel</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-revoke</span>
</td>
</tr>
</table>
</div>
</body>
</html>