man.dnssec-keygen.html revision 603de7394f5a466ea39a33a6eea2022885ec3f87
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<!--
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC")
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm - Copyright (C) 2000-2003 Internet Software Consortium.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm -
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm - Permission to use, copy, modify, and/or distribute this software for any
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm - purpose with or without fee is hereby granted, provided that the above
5c45bb188ab729e501e48732842cb9de6a9813beAlex Valavanis - copyright notice and this permission notice appear in all copies.
eb4caa8f4cdc2955b58dcd2de06fe770533414c8Jon A. Cruz -
eb4caa8f4cdc2955b58dcd2de06fe770533414c8Jon A. Cruz - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
d431763a9ec8059aa4962688de8144319969fb0fjohanengelen - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm - PERFORMANCE OF THIS SOFTWARE.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm-->
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<!-- $Id$ -->
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<html>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<head>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<title>dnssec-keygen</title>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<link rel="prev" href="man.dnssec-keyfromlabel.html" title="dnssec-keyfromlabel">
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<link rel="next" href="man.dnssec-revoke.html" title="dnssec-revoke">
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm</head>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen<div class="navheader">
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen<table width="100%" summary="Navigation header">
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen<tr><th colspan="3" align="center"><span class="application">dnssec-keygen</span></th></tr>
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen<tr>
cc618cb0faf84b6f5ab2cc9802b29d03f6a22f97Jon A. Cruz<td width="20%" align="left">
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen<a accesskey="p" href="man.dnssec-keyfromlabel.html">Prev</a>�</td>
cc618cb0faf84b6f5ab2cc9802b29d03f6a22f97Jon A. Cruz<th width="60%" align="center">Manual pages</th>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-revoke.html">Next</a>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm</td>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm</tr>
0903335a0099bd7ee779925f43a15a2216a0e863johanengelen</table>
0903335a0099bd7ee779925f43a15a2216a0e863johanengelen<hr>
0903335a0099bd7ee779925f43a15a2216a0e863johanengelen</div>
0903335a0099bd7ee779925f43a15a2216a0e863johanengelen<div class="refentry" lang="en">
0903335a0099bd7ee779925f43a15a2216a0e863johanengelen<a name="man.dnssec-keygen"></a><div class="titlepage"></div>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<div class="refnamediv">
cef9e2c431b417aea98429860c6021849f099fcfKris De Gussem<h2>Name</h2>
cef9e2c431b417aea98429860c6021849f099fcfKris De Gussem<p><span class="application">dnssec-keygen</span> &#8212; DNSSEC key generation tool</p>
cef9e2c431b417aea98429860c6021849f099fcfKris De Gussem</div>
cef9e2c431b417aea98429860c6021849f099fcfKris De Gussem<div class="refsynopsisdiv">
cef9e2c431b417aea98429860c6021849f099fcfKris De Gussem<h2>Synopsis</h2>
cef9e2c431b417aea98429860c6021849f099fcfKris De Gussem<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">-V</code>] [<code class="option">-z</code>] {name}</p></div>
c11199b2b0b6b7fbfe61f562566e0cd15604cc43Liam P. White</div>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<div class="refsect1" lang="en">
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<a name="id2624453"></a><h2>DESCRIPTION</h2>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<p><span><strong class="command">dnssec-keygen</strong></span>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm generates keys for DNSSEC (Secure DNS), as defined in RFC 2535
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm and RFC 4034. It can also generate keys for use with
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof TSIG (Transaction Signatures) as defined in RFC 2845, or TKEY
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen (Transaction Key) as defined in RFC 2930.
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen </p>
c11199b2b0b6b7fbfe61f562566e0cd15604cc43Liam P. White<p>
c11199b2b0b6b7fbfe61f562566e0cd15604cc43Liam P. White The <code class="option">name</code> of the key is specified on the command
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen line. For DNSSEC keys, this must match the name of the zone for
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen which the key is being generated.
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen </p>
b5a129ca7cf5c8e074b39ea5dbc2cc978187078bjohanengelen</div>
ea3e4fdbdbf0a48ae887b096d301549da77d5707Johan Engelen<div class="refsect1" lang="en">
a7b98b4dadda9f675e57ee1b78a9e1d2a5b3844fjtx<a name="id2624473"></a><h2>OPTIONS</h2>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof<div class="variablelist"><dl>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dd>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Selects the cryptographic algorithm. For DNSSEC keys, the value
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm of <code class="option">algorithm</code> must be one of RSAMD5, RSASHA1,
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm ECDSAP256SHA256 or ECDSAP384SHA384.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm For TSIG/TKEY, the value must
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm be DH (Diffie Hellman), HMAC-MD5, HMAC-SHA1, HMAC-SHA224,
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm HMAC-SHA256, HMAC-SHA384, or HMAC-SHA512. These values are
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm case insensitive.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm If no algorithm is specified, then RSASHA1 will be used by
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm default, unless the <code class="option">-3</code> option is specified,
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm in which case NSEC3RSASHA1 will be used instead. (If
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm <code class="option">-3</code> is used and an algorithm is specified,
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm that algorithm will be checked for compatibility with NSEC3.)
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
79291918d036d77d586b6eba265d8d2ac0a7fee5cilix algorithm, and DSA is recommended. For TSIG, HMAC-MD5 is
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm mandatory.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Note 2: DH, HMAC-MD5, and HMAC-SHA1 through HMAC-SHA512
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm automatically set the -T KEY option.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm</dd>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dt><span class="term">-b <em class="replaceable"><code>keysize</code></em></span></dt>
eaa9bdc7bf7b73397e536edd47490d84e4420bd8bryce<dd>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Specifies the number of bits in the key. The choice of key
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm size depends on the algorithm used. RSA keys must be
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm between 512 and 2048 bits. Diffie Hellman keys must be between
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm 128 and 4096 bits. DSA keys must be between 512 and 1024
eaa9bdc7bf7b73397e536edd47490d84e4420bd8bryce bits and an exact multiple of 64. HMAC keys must be
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm between 1 and 512 bits. Elliptic curve algorithms don't need
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm this parameter.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm The key size does not need to be specified if using a default
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm algorithm. The default key size is 1024 bits for zone signing
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm keys (ZSKs) and 2048 bits for key signing keys (KSKs,
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm generated with <code class="option">-f KSK</code>). However, if an
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm algorithm is explicitly specified with the <code class="option">-a</code>,
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm then there is no default key size, and the <code class="option">-b</code>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm must be used.
eaa9bdc7bf7b73397e536edd47490d84e4420bd8bryce </p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm</dd>
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White<dt><span class="term">-n <em class="replaceable"><code>nametype</code></em></span></dt>
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White<dd><p>
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White Specifies the owner type of the key. The value of
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White <code class="option">nametype</code> must either be ZONE (for a DNSSEC
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White a host (KEY)),
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White These values are case insensitive. Defaults to ZONE for DNSKEY
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White generation.
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White </p></dd>
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White<dt><span class="term">-3</span></dt>
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White<dd><p>
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White Use an NSEC3-capable algorithm to generate a DNSSEC key.
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White If this option is used and no algorithm is explicitly
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White set on the command line, NSEC3RSASHA1 will be used by
f83dd38ed9c631b7644b7c82c821fa9fbbb82352Liam P. White default. Note that RSASHA256, RSASHA512, ECCGOST,
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm ECDSAP256SHA256 and ECDSAP384SHA384 algorithms
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm are NSEC3-capable.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p></dd>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dt><span class="term">-C</span></dt>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dd><p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Compatibility mode: generates an old-style key, without
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm any metadata. By default, <span><strong class="command">dnssec-keygen</strong></span>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm will include the key's creation date in the metadata stored
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm with the private key, and other dates may be set there as well
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm (publication date, activation date, etc). Keys that include
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm this data may be incompatible with older versions of BIND; the
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm <code class="option">-C</code> option suppresses them.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p></dd>
106bf69f0520ef3b349214008cc1f91c68e69daaJabiertxof<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
a7b98b4dadda9f675e57ee1b78a9e1d2a5b3844fjtx<dd><p>
106bf69f0520ef3b349214008cc1f91c68e69daaJabiertxof Indicates that the DNS record containing the key should have
a7b98b4dadda9f675e57ee1b78a9e1d2a5b3844fjtx the specified class. If not specified, class IN is used.
106bf69f0520ef3b349214008cc1f91c68e69daaJabiertxof </p></dd>
106bf69f0520ef3b349214008cc1f91c68e69daaJabiertxof<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dd>
5cf332777b4c27336d64c273ac63bce3ee27a53dAlex Valavanis<p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Specifies the cryptographic hardware to use, when applicable.
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof </p>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof<p>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof When BIND is built with OpenSSL PKCS#11 support, this defaults
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof to the string "pkcs11", which identifies an OpenSSL engine
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof that can drive a cryptographic accelerator or hardware service
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof module. When BIND is built with native PKCS#11 cryptography
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof (--enable-native-pkcs11), it defaults to the path of the PKCS#11
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof provider library specified via "--with-pkcs11".
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof </p>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof</dd>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof<dt><span class="term">-f <em class="replaceable"><code>flag</code></em></span></dt>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof<dd><p>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof Set the specified flag in the flag field of the KEY/DNSKEY record.
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof The only recognized flags are KSK (Key Signing Key) and REVOKE.
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof </p></dd>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof<dt><span class="term">-G</span></dt>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof<dd><p>
3ab4e87511c6a42f29370bf22a9afcf759ca1d0dJabiertxof Generate a key, but do not publish it or sign with it. This
a7b98b4dadda9f675e57ee1b78a9e1d2a5b3844fjtx option is incompatible with -P and -A.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p></dd>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dt><span class="term">-g <em class="replaceable"><code>generator</code></em></span></dt>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dd><p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm If generating a Diffie Hellman key, use this generator.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Allowed values are 2 and 5. If no generator
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm is specified, a known prime from RFC 2539 will be used
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm if possible; otherwise the default is 2.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p></dd>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dt><span class="term">-h</span></dt>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dd><p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Prints a short summary of the options and arguments to
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm <span><strong class="command">dnssec-keygen</strong></span>.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p></dd>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dd><p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Sets the directory in which the key files are to be written.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p></dd>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dt><span class="term">-k</span></dt>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dd><p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Deprecated in favor of -T KEY.
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm </p></dd>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dt><span class="term">-L <em class="replaceable"><code>ttl</code></em></span></dt>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm<dd><p>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm Sets the default TTL to use for this key when it is converted
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm into a DNSKEY RR. If the key is imported into a zone,
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm this is the TTL that will be used for it, unless there was
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm already a DNSKEY RRset in place, in which case the existing TTL
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm would take precedence. If this value is not set and there
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm is no existing DNSKEY RRset, the TTL will default to the
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm SOA TTL. Setting the default TTL to <code class="literal">0</code>
f07bfd5a05d43a6d11f7cd442f085149092dea88pjrm or <code class="literal">none</code> is the same as leaving it unset.
</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>
<dt><span class="term">-V</span></dt>
<dd><p>
Prints version information.
</p></dd>
</dl></div>
</div>
<div class="refsect1" lang="en">
<a name="id2675197"></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. To explicitly prevent a date from being
set, use 'none' or 'never'.
</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". If set, if and -P is not set, then
the publication date will be set to the activation date
minus the prepublication interval.
</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="id2675319"></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="id2675495"></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="id2675620"></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="id2675651"></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.ch13.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>
<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>