1<!-- 2 - Copyright (C) 2013, 2014 Internet Systems Consortium, Inc. ("ISC") 3 - 4 - Permission to use, copy, modify, and/or distribute this software for any 5 - purpose with or without fee is hereby granted, provided that the above 6 - copyright notice and this permission notice appear in all copies. 7 - 8 - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 9 - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 10 - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 11 - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 12 - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 13 - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 14 - PERFORMANCE OF THIS SOFTWARE. 15--> 16 17<!-- Id --> 18<html> 19<head> 20<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> 21<title>dnssec-importkey</title> 22<meta name="generator" content="DocBook XSL Stylesheets V1.71.1"> 23</head> 24<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"> 25<a name="man.dnssec-importkey"></a><div class="titlepage"></div> 26<div class="refnamediv"> 27<h2>Name</h2> 28<p><span class="application">dnssec-importkey</span> — Import DNSKEY records from external systems so they can be managed.</p> 29</div> 30<div class="refsynopsisdiv"> 31<h2>Synopsis</h2> 32<div class="cmdsynopsis"><p><code class="command">dnssec-importkey</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">-P <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-h</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] {<code class="option">keyfile</code>}</p></div> 33<div class="cmdsynopsis"><p><code class="command">dnssec-importkey</code> {<code class="option">-f <em class="replaceable"><code>filename</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">-P <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-h</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] [<code class="option">dnsname</code>]</p></div> 34</div> 35<div class="refsect1" lang="en"> 36<a name="id2543475"></a><h2>DESCRIPTION</h2> 37<p><span><strong class="command">dnssec-importkey</strong></span> 38 reads a public DNSKEY record and generates a pair of 39 .key/.private files. The DNSKEY record may be read from an 40 existing .key file, in which case a corresponding .private file 41 will be generated, or it may be read from any other file or 42 from the standard input, in which case both .key and .private 43 files will be generated. 44 </p> 45<p> 46 The newly-created .private file does <span class="emphasis"><em>not</em></span> 47 contain private key data, and cannot be used for signing. 48 However, having a .private file makes it possible to set 49 publication (<code class="option">-P</code>) and deletion 50 (<code class="option">-D</code>) times for the key, which means the 51 public key can be added to and removed from the DNSKEY RRset 52 on schedule even if the true private key is stored offline. 53 </p> 54</div> 55<div class="refsect1" lang="en"> 56<a name="id2543500"></a><h2>OPTIONS</h2> 57<div class="variablelist"><dl> 58<dt><span class="term">-f <em class="replaceable"><code>filename</code></em></span></dt> 59<dd> 60<p> 61 Zone file mode: instead of a public keyfile name, the argument 62 is the DNS domain name of a zone master file, which can be read 63 from <code class="option">file</code>. If the domain name is the same as 64 <code class="option">file</code>, then it may be omitted. 65 </p> 66<p> 67 If <code class="option">file</code> is set to <code class="literal">"-"</code>, then 68 the zone data is read from the standard input. 69 </p> 70</dd> 71<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt> 72<dd><p> 73 Sets the directory in which the key files are to reside. 74 </p></dd> 75<dt><span class="term">-L <em class="replaceable"><code>ttl</code></em></span></dt> 76<dd><p> 77 Sets the default TTL to use for this key when it is converted 78 into a DNSKEY RR. If the key is imported into a zone, 79 this is the TTL that will be used for it, unless there was 80 already a DNSKEY RRset in place, in which case the existing TTL 81 would take precedence. Setting the default TTL to 82 <code class="literal">0</code> or <code class="literal">none</code> removes it. 83 </p></dd> 84<dt><span class="term">-h</span></dt> 85<dd><p> 86 Emit usage message and exit. 87 </p></dd> 88<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt> 89<dd><p> 90 Sets the debugging level. 91 </p></dd> 92<dt><span class="term">-V</span></dt> 93<dd><p> 94 Prints version information. 95 </p></dd> 96</dl></div> 97</div> 98<div class="refsect1" lang="en"> 99<a name="id2543632"></a><h2>TIMING OPTIONS</h2> 100<p> 101 Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. 102 If the argument begins with a '+' or '-', it is interpreted as 103 an offset from the present time. For convenience, if such an offset 104 is followed by one of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', 105 then the offset is computed in years (defined as 365 24-hour days, 106 ignoring leap years), months (defined as 30 24-hour days), weeks, 107 days, hours, or minutes, respectively. Without a suffix, the offset 108 is computed in seconds. To explicitly prevent a date from being 109 set, use 'none' or 'never'. 110 </p> 111<div class="variablelist"><dl> 112<dt><span class="term">-P <em class="replaceable"><code>date/offset</code></em></span></dt> 113<dd><p> 114 Sets the date on which a key is to be published to the zone. 115 After that date, the key will be included in the zone but will 116 not be used to sign it. 117 </p></dd> 118<dt><span class="term">-D <em class="replaceable"><code>date/offset</code></em></span></dt> 119<dd><p> 120 Sets the date on which the key is to be deleted. After that 121 date, the key will no longer be included in the zone. (It 122 may remain in the key repository, however.) 123 </p></dd> 124</dl></div> 125</div> 126<div class="refsect1" lang="en"> 127<a name="id2543678"></a><h2>FILES</h2> 128<p> 129 A keyfile can be designed by the key identification 130 <code class="filename">Knnnn.+aaa+iiiii</code> or the full file name 131 <code class="filename">Knnnn.+aaa+iiiii.key</code> as generated by 132 <span class="refentrytitle">dnssec-keygen</span>(8). 133 </p> 134</div> 135<div class="refsect1" lang="en"> 136<a name="id2543700"></a><h2>SEE ALSO</h2> 137<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>, 138 <span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>, 139 <em class="citetitle">BIND 9 Administrator Reference Manual</em>, 140 <em class="citetitle">RFC 5011</em>. 141 </p> 142</div> 143<div class="refsect1" lang="en"> 144<a name="id2543733"></a><h2>AUTHOR</h2> 145<p><span class="corpauthor">Internet Systems Consortium</span> 146 </p> 147</div> 148</div></body> 149</html> 150