1DNSSEC-IMPORTKEY(8) BIND9 DNSSEC-IMPORTKEY(8)
2
6 dnssec-importkey - import DNSKEY records from external systems so they
7 can be managed
8
10 dnssec-importkey [-K directory] [-L ttl] [-P date/offset]
11 [-P sync date/offset] [-D date/offset]
12 [-D sync date/offset] [-h] [-v level] [-V] {keyfile}
13 dnssec-importkey {-f filename} [-K directory] [-L ttl] [-P date/offset]
15 [-P sync date/offset] [-D date/offset]
16 [-D sync date/offset] [-h] [-v level] [-V] [dnsname]
17
19 dnssec-importkey reads a public DNSKEY record and generates a pair of
20 .key/.private files. The DNSKEY record may be read from an existing
21 .key file, in which case a corresponding .private file will be
22 generated, or it may be read from any other file or from the standard
23 input, in which case both .key and .private files will be generated.
24 The newly-created .private file does not contain private key data, and
26 cannot be used for signing. However, having a .private file makes it
27 possible to set publication (-P) and deletion (-D) times for the key,
28 which means the public key can be added to and removed from the DNSKEY
29 RRset on schedule even if the true private key is stored offline.
30
32 -f filename
33 Zone file mode: instead of a public keyfile name, the argument is
34 the DNS domain name of a zone master file, which can be read from
35 file. If the domain name is the same as file, then it may be
36 omitted.
37 If file is set to "-", then the zone data is read from the standard
39 input.
40 -K directory
42 Sets the directory in which the key files are to reside.
43 -L ttl
45 Sets the default TTL to use for this key when it is converted into
46 a DNSKEY RR. If the key is imported into a zone, this is the TTL
47 that will be used for it, unless there was already a DNSKEY RRset
48 in place, in which case the existing TTL would take precedence.
49 Setting the default TTL to 0 or none removes it.
50 -h
52 Emit usage message and exit.
53 -v level
55 Sets the debugging level.
56 -V
58 Prints version information.
59
61 Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the
62 argument begins with a '+' or '-', it is interpreted as an offset from
63 the present time. For convenience, if such an offset is followed by one
64 of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the offset is
65 computed in years (defined as 365 24-hour days, ignoring leap years),
66 months (defined as 30 24-hour days), weeks, days, hours, or minutes,
67 respectively. Without a suffix, the offset is computed in seconds. To
68 explicitly prevent a date from being set, use 'none' or 'never'.
69 -P date/offset
71 Sets the date on which a key is to be published to the zone. After
72 that date, the key will be included in the zone but will not be
73 used to sign it.
74 -P sync date/offset
76 Sets the date on which CDS and CDNSKEY records that match this key
77 are to be published to the zone.
78 -D date/offset
80 Sets the date on which the key is to be deleted. After that date,
81 the key will no longer be included in the zone. (It may remain in
82 the key repository, however.)
83 -D sync date/offset
85 Sets the date on which the CDS and CDNSKEY records that match this
86 key are to be deleted.
87
89 A keyfile can be designed by the key identification Knnnn.+aaa+iiiii or
90 the full file name Knnnn.+aaa+iiiii.key as generated by
91 dnssec-keygen(8).
92
94 dnssec-keygen(8), dnssec-signzone(8), BIND 9 Administrator Reference
95 Manual, RFC 5011.
96
98 Internet Systems Consortium, Inc.
99
101 Copyright © 2013-2016, 2018, 2019 Internet Systems Consortium, Inc.
102 ("ISC")
103ISC August 21, 2015 DNSSEC-IMPORTKEY(8)