man.dnssec-keygen.html revision 64affc54f96a2c71cbd10ed71e246ce0746259aa
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<!--
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - Copyright (C) 2004-2009 Internet Systems Consortium, Inc. ("ISC")
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen - Copyright (C) 2000-2003 Internet Software Consortium.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen -
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - Permission to use, copy, modify, and/or distribute this software for any
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - purpose with or without fee is hereby granted, provided that the above
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - copyright notice and this permission notice appear in all copies.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen -
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen - PERFORMANCE OF THIS SOFTWARE.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen-->
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<!-- $Id: man.dnssec-keygen.html,v 1.144 2009/11/03 21:58:30 tbox Exp $ -->
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<html>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<head>
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<title>dnssec-keygen</title>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<link rel="prev" href="man.dnssec-keyfromlabel.html" title="dnssec-keyfromlabel">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<link rel="next" href="man.dnssec-revoke.html" title="dnssec-revoke">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen</head>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<div class="navheader">
a0fc93054e8c588871e8b351074aaf528bd4a89eKris<table width="100%" summary="Navigation header">
e5e0e89fd171e5d78721aac368322d3ca26ca883Kris<tr><th colspan="3" align="center"><span class="application">dnssec-keygen</span></th></tr>
e5e0e89fd171e5d78721aac368322d3ca26ca883Kris<tr>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<td width="20%" align="left">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<a accesskey="p" href="man.dnssec-keyfromlabel.html">Prev</a>�</td>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<th width="60%" align="center">Manual pages</th>
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-revoke.html">Next</a>
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen</td>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen</tr>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen</table>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<hr>
cd8e8082c747cc529d5bf595b4102e88224a1811Krzysztof Kosiński</div>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<div class="refentry" lang="en">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<a name="man.dnssec-keygen"></a><div class="titlepage"></div>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<div class="refnamediv">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<h2>Name</h2>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<p><span class="application">dnssec-keygen</span> &#8212; DNSSEC key generation tool</p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen</div>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<div class="refsynopsisdiv">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<h2>Synopsis</h2>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<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">-e</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">-K <em class="replaceable"><code>directory</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>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>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen</div>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<div class="refsect1" lang="en">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<a name="id2608272"></a><h2>DESCRIPTION</h2>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<p><span><strong class="command">dnssec-keygen</strong></span>
307c164a7b61c5bfd08eaf25236383f070801bb1scislac generates keys for DNSSEC (Secure DNS), as defined in RFC 2535
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen and RFC 4034. It can also generate keys for use with
307c164a7b61c5bfd08eaf25236383f070801bb1scislac TSIG (Transaction Signatures) as defined in RFC 2845, or TKEY
307c164a7b61c5bfd08eaf25236383f070801bb1scislac (Transaction Key) as defined in RFC 2930.
307c164a7b61c5bfd08eaf25236383f070801bb1scislac </p>
307c164a7b61c5bfd08eaf25236383f070801bb1scislac<p>
307c164a7b61c5bfd08eaf25236383f070801bb1scislac The <code class="option">name</code> of the key is specified on the command
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen line. For DNSSEC keys, this must match the name of the zone for
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen which the key is being generated.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen </p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen</div>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<div class="refsect1" lang="en">
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<a name="id2608292"></a><h2>OPTIONS</h2>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<div class="variablelist"><dl>
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould<dd>
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould<p>
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould Selects the cryptographic algorithm. For DNSSEC keys, the value
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould of <code class="option">algorithm</code> must be one of RSAMD5, RSASHA1,
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256 or RSASHA512.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen For TSIG/TKEY, the value must
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen be DH (Diffie Hellman), HMAC-MD5, HMAC-SHA1, HMAC-SHA224,
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen HMAC-SHA256, HMAC-SHA384, or HMAC-SHA512. These values are
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen case insensitive.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen </p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<p>
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen If no algorithm is specified, then RSASHA1 will be used by
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen default, unless the <code class="option">-3</code> option is specified,
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen in which case NSEC3RSASHA1 will be used instead. (If
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen <code class="option">-3</code> is used and an algorithm is specified,
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen that algorithm will be checked for compatibility with NSEC3.)
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen </p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen algorithm, and DSA is recommended. For TSIG, HMAC-MD5 is
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen mandatory.
b632ab726ddcf5acea122f867fef25decfb6dbe9johanengelen </p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen Note 2: DH, HMAC-MD5, and HMAC-SHA1 through HMAC-SHA512
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen automatically set the -T KEY option.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen </p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen</dd>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<dt><span class="term">-b <em class="replaceable"><code>keysize</code></em></span></dt>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<dd>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen Specifies the number of bits in the key. The choice of key
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen size depends on the algorithm used. RSA keys must be
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen between 512 and 2048 bits. Diffie Hellman keys must be between
a69e3ca5fcc8acacf862c577620d75f472d58cecjohanengelen 128 and 4096 bits. DSA keys must be between 512 and 1024
a69e3ca5fcc8acacf862c577620d75f472d58cecjohanengelen bits and an exact multiple of 64. HMAC keys must be
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen between 1 and 512 bits.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen </p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<p>
b1f68f459a210575936c2450f578f79189fc3817Johan Engelen The key size does not need to be specified if using a default
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen algorithm. The default key size is 1024 bits for zone signing
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen keys (ZSK's) and 2048 bits for key signing keys (KSK's,
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen generated with <code class="option">-f KSK</code>). However, if an
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen algorithm is explicitly specified with the <code class="option">-a</code>,
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould then there is no default key size, and the <code class="option">-b</code>
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould must be used.
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould </p>
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould</dd>
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould<dt><span class="term">-n <em class="replaceable"><code>nametype</code></em></span></dt>
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould<dd><p>
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould Specifies the owner type of the key. The value of
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould <code class="option">nametype</code> must either be ZONE (for a DNSSEC
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould a host (KEY)),
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
6c3e745a94ef6b25a4ef9f018d350a7535aa45afTed Gould These values are case insensitive. Defaults to ZONE for DNSKEY
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen generation.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen </p></dd>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<dt><span class="term">-3</span></dt>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<dd><p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen Use an NSEC3-capable algorithm to generate a DNSSEC key.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen If this option is used and no algorithm is explicitly
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen set on the command line, NSEC3RSASHA1 will be used by
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen default. Note that RSASHA256 and RSASHA512 algorithms
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen are NSEC3-capable.
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen </p></dd>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<dt><span class="term">-C</span></dt>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen<dd><p>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen Compatibility mode: generates an old-style key, without
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen any metadata. By default, <span><strong class="command">dnssec-keygen</strong></span>
0a75b58e47d3de42550c4f7960e253ea3befc09ajohanengelen 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">-e</span></dt>
<dd><p>
If generating an RSAMD5/RSASHA1 key, use a large exponent.
</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">-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>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="id2655962"></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>
</dl></div>
</div>
<div class="refsect1" lang="en">
<a name="id2656060"></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="id2656236"></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="id2656361"></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="id2656392"></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>