man.dnssec-keyfromlabel.html revision 1700442a7751c2bbdafe2d039cebbd8316496957
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<!--
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC")
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd - Copyright (C) 2000-2003 Internet Software Consortium.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd -
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd - Permission to use, copy, modify, and/or distribute this software for any
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd - purpose with or without fee is hereby granted, provided that the above
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd - copyright notice and this permission notice appear in all copies.
96ad5d81ee4a2cc66a4ae19893efc8aa6d06fae7jailletc -
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
2e545ce2450a9953665f701bb05350f0d3f26275nd - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd - PERFORMANCE OF THIS SOFTWARE.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd-->
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<html>
af33a4994ae2ff15bc67d19ff1a7feb906745bf8rbowen<head>
3f08db06526d6901aa08c110b5bc7dde6bc39905nd<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<title>dnssec-keyfromlabel</title>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
3f08db06526d6901aa08c110b5bc7dde6bc39905nd<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<link rel="prev" href="man.dnssec-importkey.html" title="dnssec-importkey">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<link rel="next" href="man.dnssec-keygen.html" title="dnssec-keygen">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd</head>
ad74a0524a06bfe11b7de9e3b4ce7233ab3bd3f7nd<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
45d66a3a49ac14b7f18cd4d733c1947801b55172sf<div class="navheader">
f086b4b402fa9a2fefc7dda85de2a3cc1cd0a654rjung<table width="100%" summary="Navigation header">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<tr><th colspan="3" align="center"><span class="application">dnssec-keyfromlabel</span></th></tr>
c2ed7ae314df26c4cd9e3a7224dabc6baa3f4dceigalic<tr>
c2ed7ae314df26c4cd9e3a7224dabc6baa3f4dceigalic<td width="20%" align="left">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<a accesskey="p" href="man.dnssec-importkey.html">Prev</a>�</td>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<th width="60%" align="center">Manual pages</th>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-keygen.html">Next</a>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd</td>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd</tr>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd</table>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<hr>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd</div>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<div class="refentry">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<a name="man.dnssec-keyfromlabel"></a><div class="titlepage"></div>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<div class="refnamediv">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<h2>Name</h2>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p><span class="application">dnssec-keyfromlabel</span> &#8212; DNSSEC key generation tool</p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd</div>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<div class="refsynopsisdiv">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<h2>Synopsis</h2>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<div class="cmdsynopsis"><p><code class="command">dnssec-keyfromlabel</code> {-l <em class="replaceable"><code>label</code></em>} [<code class="option">-3</code>] [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>] [<code class="option">-A <em class="replaceable"><code>date/offset</code></em></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">-D sync <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">-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</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">-n <em class="replaceable"><code>nametype</code></em></code>] [<code class="option">-P <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-P sync <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-p <em class="replaceable"><code>protocol</code></em></code>] [<code class="option">-R <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-S <em class="replaceable"><code>key</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">-y</code>] {name}</p></div>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd</div>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<div class="refsection">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<a name="id-1.14.9.7"></a><h2>DESCRIPTION</h2>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p><span class="command"><strong>dnssec-keyfromlabel</strong></span>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd generates a key pair of files that referencing a key object stored
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd in a cryptographic hardware service module (HSM). The private key
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd file can be used for DNSSEC signing of zone data as if it were a
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd conventional signing key created by <span class="command"><strong>dnssec-keygen</strong></span>,
30471a4650391f57975f60bbb6e4a90be7b284bfhumbedooh but the key material is stored within the HSM, and the actual signing
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd takes place there.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd </p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd The <code class="option">name</code> of the key is specified on the command
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd line. This must match the name of the zone for which the key is
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd being generated.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd </p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd</div>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<div class="refsection">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<a name="id-1.14.9.8"></a><h2>OPTIONS</h2>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<div class="variablelist"><dl class="variablelist">
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<dd>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd Selects the cryptographic algorithm. The value of
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd <code class="option">algorithm</code> must be one of RSAMD5, RSASHA1,
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd ECDSAP256SHA256 or ECDSAP384SHA384.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd These values are case insensitive.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd </p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd If no algorithm is specified, then RSASHA1 will be used by
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd default, unless the <code class="option">-3</code> option is specified,
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd in which case NSEC3RSASHA1 will be used instead. (If
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd <code class="option">-3</code> is used and an algorithm is specified,
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd that algorithm will be checked for compatibility with NSEC3.)
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd </p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd algorithm, and DSA is recommended.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd </p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd Note 2: DH automatically sets the -k flag.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd </p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd</dd>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<dt><span class="term">-3</span></dt>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<dd><p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd Use an NSEC3-capable algorithm to generate a DNSSEC key.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd If this option is used and no algorithm is explicitly
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd set on the command line, NSEC3RSASHA1 will be used by
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd default.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd </p></dd>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<dd>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd Specifies the cryptographic hardware to use.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd </p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd When BIND is built with OpenSSL PKCS#11 support, this defaults
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd to the string "pkcs11", which identifies an OpenSSL engine
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd that can drive a cryptographic accelerator or hardware service
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd module. When BIND is built with native PKCS#11 cryptography
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd (--enable-native-pkcs11), it defaults to the path of the PKCS#11
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd provider library specified via "--with-pkcs11".
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd </p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd</dd>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<dt><span class="term">-l <em class="replaceable"><code>label</code></em></span></dt>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<dd>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd Specifies the label for a key pair in the crypto hardware.
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd </p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd<p>
ad74a0524a06bfe11b7de9e3b4ce7233ab3bd3f7nd When <acronym class="acronym">BIND</acronym> 9 is built with OpenSSL-based
45d66a3a49ac14b7f18cd4d733c1947801b55172sf PKCS#11 support, the label is an arbitrary string that
f086b4b402fa9a2fefc7dda85de2a3cc1cd0a654rjung identifies a particular key. It may be preceded by an
727872d18412fc021f03969b8641810d8896820bhumbedooh optional OpenSSL engine name, followed by a colon, as in
0d0ba3a410038e179b695446bb149cce6264e0abnd "pkcs11:<em class="replaceable"><code>keylabel</code></em>".
727872d18412fc021f03969b8641810d8896820bhumbedooh </p>
cc7e1025de9ac63bd4db6fe7f71c158b2cf09fe4humbedooh<p>
0d0ba3a410038e179b695446bb149cce6264e0abnd When <acronym class="acronym">BIND</acronym> 9 is built with native PKCS#11
cc7e1025de9ac63bd4db6fe7f71c158b2cf09fe4humbedooh support, the label is a PKCS#11 URI string in the format
727872d18412fc021f03969b8641810d8896820bhumbedooh "pkcs11:<code class="option">keyword</code>=<em class="replaceable"><code>value</code></em>[<span class="optional">;<code class="option">keyword</code>=<em class="replaceable"><code>value</code></em>;...</span>]"
0d0ba3a410038e179b695446bb149cce6264e0abnd Keywords include "token", which identifies the HSM; "object", which
0d0ba3a410038e179b695446bb149cce6264e0abnd identifies the key; and "pin-source", which identifies a file from
0d0ba3a410038e179b695446bb149cce6264e0abnd which the HSM's PIN code can be obtained. The label will be
ac082aefa89416cbdc9a1836eaf3bed9698201c8humbedooh stored in the on-disk "private" file.
0d0ba3a410038e179b695446bb149cce6264e0abnd </p>
0d0ba3a410038e179b695446bb149cce6264e0abnd<p>
0d0ba3a410038e179b695446bb149cce6264e0abnd If the label contains a
727872d18412fc021f03969b8641810d8896820bhumbedooh <code class="option">pin-source</code> field, tools using the generated
0d0ba3a410038e179b695446bb149cce6264e0abnd key files will be able to use the HSM for signing and other
0d0ba3a410038e179b695446bb149cce6264e0abnd operations without any need for an operator to manually enter
30471a4650391f57975f60bbb6e4a90be7b284bfhumbedooh a PIN. Note: Making the HSM's PIN accessible in this manner
07dc96d063d49299da433f84b5c5681da9bbdf68rbowen may reduce the security advantage of using an HSM; be sure
af33a4994ae2ff15bc67d19ff1a7feb906745bf8rbowen this is what you want to do before making use of this feature.
0d0ba3a410038e179b695446bb149cce6264e0abnd </p>
7fec19672a491661b2fe4b29f685bc7f4efa64d4nd</dd>
7fec19672a491661b2fe4b29f685bc7f4efa64d4nd<dt><span class="term">-n <em class="replaceable"><code>nametype</code></em></span></dt>
7fec19672a491661b2fe4b29f685bc7f4efa64d4nd<dd><p>
0853e1e2522c1ac17f697221758bcbd4781a7ff9nd Specifies the owner type of the key. The value of
<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.
</p></dd>
<dt><span class="term">-C</span></dt>
<dd><p>
Compatibility mode: generates an old-style key, without
any metadata. By default, <span class="command"><strong>dnssec-keyfromlabel</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">-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">-h</span></dt>
<dd><p>
Prints a short summary of the options and arguments to
<span class="command"><strong>dnssec-keyfromlabel</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>
Generate KEY records rather than DNSKEY records.
</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 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">-S <em class="replaceable"><code>key</code></em></span></dt>
<dd><p>
Generate a key as an explicit successor to an existing key.
The name, algorithm, size, and type of the key will be set
to match the predecessor. 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">-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>
<dt><span class="term">-y</span></dt>
<dd><p>
Allows DNSSEC key files to be generated even if the key ID
would collide with that of an existing key, in the event of
either key being revoked. (This is only safe to use if you
are sure you won't be using RFC 5011 trust anchor maintenance
with either of the keys involved.)
</p></dd>
</dl></div>
</div>
<div class="refsection">
<a name="id-1.14.9.9"></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 class="variablelist">
<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">-P sync <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
Sets the date on which the CDS and CDNSKEY records which match
this key are to be published to the zone.
</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">-D sync <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
Sets the date on which the CDS and CDNSKEY records which match
this key are to be deleted.
</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="refsection">
<a name="id-1.14.9.10"></a><h2>GENERATED KEY FILES</h2>
<p>
When <span class="command"><strong>dnssec-keyfromlabel</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 files it has generated.
</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem"><p><code class="filename">nnnn</code> is the key name.
</p></li>
<li class="listitem"><p><code class="filename">aaa</code> is the numeric representation
of the algorithm.
</p></li>
<li class="listitem"><p><code class="filename">iiiii</code> is the key identifier (or
footprint).
</p></li>
</ul></div>
<p><span class="command"><strong>dnssec-keyfromlabel</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>
</div>
<div class="refsection">
<a name="id-1.14.9.11"></a><h2>SEE ALSO</h2>
<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
<span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 4034</em>,
<em class="citetitle">The PKCS#11 URI Scheme (draft-pechanec-pkcs11uri-13)</em>.
</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-importkey.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-keygen.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">dnssec-importkey</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-keygen</span>
</td>
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0b2</p>
</body>
</html>