<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<
table width="100%" summary="Navigation header">
<
tr><
th colspan="3" align="center"><
span class="application">dnssec-keyfromlabel</
span></
th></
tr>
<
td width="20%" align="left">
<
th width="60%" align="center">Manual pages</
th>
<
div class="refentry" lang="en">
<
p><
span class="application">dnssec-keyfromlabel</
span> — DNSSEC key generation tool</
p>
<
div class="refsynopsisdiv">
<
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">-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">-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 <
em class="replaceable"><
code>protocol</
code></
em></
code>] [<
code class="option">-R <
em class="replaceable"><
code>
date/
offset</
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">-y</
code>] {name}</
p></
div>
<
div class="refsect1" lang="en">
<
a name="id2617249"></
a><
h2>DESCRIPTION</
h2>
<
p><
span><
strong class="command">dnssec-keyfromlabel</
strong></
span>
gets keys with the given label from a crypto hardware and builds
key files for DNSSEC (Secure DNS), as defined in RFC 2535
The <
code class="option">name</
code> of the key is specified on the command
line. This must match the name of the zone for which the key is
<
div class="refsect1" lang="en">
<
a name="id2617269"></
a><
h2>OPTIONS</
h2>
<
div class="variablelist"><
dl>
<
dt><
span class="term">-a <
em class="replaceable"><
code>algorithm</
code></
em></
span></
dt>
Selects the cryptographic algorithm. The value of
<
code class="option">algorithm</
code> must be one of RSAMD5, RSASHA1,
DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
ECDSAP256SHA256 or ECDSAP384SHA384.
These values are case insensitive.
If no algorithm is specified, then RSASHA1 will be used by
default, unless the <
code class="option">-3</
code> option is specified,
in which case NSEC3RSASHA1 will be used instead. (If
<
code class="option">-3</
code> is used and an algorithm is specified,
that algorithm will be checked for compatibility with NSEC3.)
Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
algorithm, and DSA is recommended.
Note 2: DH automatically sets the -k flag.
<
dt><
span class="term">-3</
span></
dt>
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
<
dt><
span class="term">-E <
em class="replaceable"><
code>engine</
code></
em></
span></
dt>
Specifies the cryptographic hardware to use.
When BIND is built with OpenSSL PKCS#11 support, this defaults
to the string "pkcs11", which identifies an OpenSSL engine
that can drive a cryptographic accelerator or hardware service
module. When BIND is built with native PKCS#11 cryptography
(--enable-native-pkcs11), it defaults to the path of the PKCS#11
provider library specified via "--with-pkcs11".
<
dt><
span class="term">-l <
em class="replaceable"><
code>label</
code></
em></
span></
dt>
Specifies the label of the key pair in the crypto hardware.
The label may be preceded by an optional OpenSSL engine name,
separated by a colon, as in "pkcs11:keylabel".
<
dt><
span class="term">-n <
em class="replaceable"><
code>nametype</
code></
em></
span></
dt>
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
USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
These values are case insensitive.
<
dt><
span class="term">-C</
span></
dt>
Compatibility mode: generates an old-style key, without
any metadata. By default, <
span><
strong class="command">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.
<
dt><
span class="term">-c <
em class="replaceable"><
code>class</
code></
em></
span></
dt>
Indicates that the DNS record containing the key should have
the specified class. If not specified, class IN is used.
<
dt><
span class="term">-f <
em class="replaceable"><
code>flag</
code></
em></
span></
dt>
Set the specified flag in the flag field of the
KEY/
DNSKEY record.
The only recognized flags are KSK (Key Signing Key) and REVOKE.
<
dt><
span class="term">-G</
span></
dt>
Generate a key, but do not publish it or sign with it. This
option is incompatible with -P and -A.
<
dt><
span class="term">-h</
span></
dt>
Prints a short summary of the options and arguments to
<
span><
strong class="command">dnssec-keyfromlabel</
strong></
span>.
<
dt><
span class="term">-K <
em class="replaceable"><
code>directory</
code></
em></
span></
dt>
Sets the directory in which the key files are to be written.
<
dt><
span class="term">-k</
span></
dt>
Generate KEY records rather than DNSKEY records.
<
dt><
span class="term">-L <
em class="replaceable"><
code>ttl</
code></
em></
span></
dt>
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.
<
dt><
span class="term">-p <
em class="replaceable"><
code>protocol</
code></
em></
span></
dt>
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.
<
dt><
span class="term">-t <
em class="replaceable"><
code>type</
code></
em></
span></
dt>
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.
<
dt><
span class="term">-v <
em class="replaceable"><
code>level</
code></
em></
span></
dt>
Sets the debugging level.
<
dt><
span class="term">-y</
span></
dt>
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.)
<
div class="refsect1" lang="en">
<
a name="id2619306"></
a><
h2>TIMING OPTIONS</
h2>
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
<
div class="variablelist"><
dl>
<
dt><
span class="term">-P <
em class="replaceable"><
code>
date/
offset</
code></
em></
span></
dt>
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".
<
dt><
span class="term">-A <
em class="replaceable"><
code>
date/
offset</
code></
em></
span></
dt>
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
<
dt><
span class="term">-R <
em class="replaceable"><
code>
date/
offset</
code></
em></
span></
dt>
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.
<
dt><
span class="term">-I <
em class="replaceable"><
code>
date/
offset</
code></
em></
span></
dt>
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.
<
dt><
span class="term">-D <
em class="replaceable"><
code>
date/
offset</
code></
em></
span></
dt>
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.)
<
div class="refsect1" lang="en">
<
a name="id2619473"></
a><
h2>GENERATED KEY FILES</
h2>
When <
span><
strong class="command">dnssec-keyfromlabel</
strong></
span> completes
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.
<
div class="itemizedlist"><
ul type="disc">
<
li><
p><
code class="filename">nnnn</
code> is the key name.
<
li><
p><
code class="filename">aaa</
code> is the numeric representation
<
li><
p><
code class="filename">iiiii</
code> is the key identifier (or
<
p><
span><
strong class="command">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
The <
code class="filename">.key</
code> file contains a DNS KEY record
can be inserted into a zone file (directly or with a $INCLUDE
The <
code class="filename">.private</
code> file contains
fields. For obvious security reasons, this file does not have
<
div class="refsect1" lang="en">
<
a name="id2667490"></
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>.
<
div class="refsect1" lang="en">
<
a name="id2667523"></
a><
h2>AUTHOR</
h2>
<
p><
span class="corpauthor">Internet Systems Consortium</
span>
<
table width="100%" summary="Navigation footer">
<
td width="40%" align="left">
<
td width="20%" align="center"><
a accesskey="u" href="Bv9ARM.ch10.html">Up</
a></
td>
<
td width="40%" align="left" valign="top">
<
span class="application">dnssec-dsfromkey</
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>