1DNSSEC-SETTIME(8) BIND9 DNSSEC-SETTIME(8)
2
6 dnssec-settime - Set the key timing metadata for a DNSSEC key
7
9 dnssec-settime [-f] [-K directory] [-P date/offset] [-A date/offset]
10 [-R date/offset] [-I date/offset] [-D date/offset] [-h]
11 [-v level] [-E engine] {keyfile}
12
14 dnssec-settime reads a DNSSEC private key file and sets the key timing
15 metadata as specified by the -P, -A, -R, -I, and -D options. The
16 metadata can then be used by dnssec-signzone or other signing software
17 to determine when a key is to be published, whether it should be used
18 for signing a zone, etc.
19 If none of these options is set on the command line, then
21 dnssec-settime simply prints the key timing metadata already stored in
22 the key.
23 When key metadata fields are changed, both files of a key pair
25 (Knnnn.+aaa+iiiii.key and Knnnn.+aaa+iiiii.private) are regenerated.
26 Metadata fields are stored in the private file. A human-readable
27 description of the metadata is also placed in comments in the key file.
28 The private file's permissions are always set to be inaccessible to
29 anyone other than the owner (mode 0600).
30
32 -f
33 Force an update of an old-format key with no metadata fields.
34 Without this option, dnssec-settime will fail when attempting to
35 update a legacy key. With this option, the key will be recreated in
36 the new format, but with the original key data retained. The key's
37 creation date will be set to the present time. If no other values
38 are specified, then the key's publication and activation dates will
39 also be set to the present time.
40 -K directory
42 Sets the directory in which the key files are to reside.
43 -h
45 Emit usage message and exit.
46 -v level
48 Sets the debugging level.
49 -E engine
51 Use the given OpenSSL engine. When compiled with PKCS#11 support it
52 defaults to pkcs11; the empty name resets it to no engine.
53
55 Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the
56 argument begins with a '+' or '-', it is interpreted as an offset from
57 the present time. For convenience, if such an offset is followed by one
58 of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the offset is
59 computed in years (defined as 365 24-hour days, ignoring leap years),
60 months (defined as 30 24-hour days), weeks, days, hours, or minutes,
61 respectively. Without a suffix, the offset is computed in seconds. To
62 unset a date, use 'none'.
63 -P date/offset
65 Sets the date on which a key is to be published to the zone. After
66 that date, the key will be included in the zone but will not be
67 used to sign it.
68 -A date/offset
70 Sets the date on which the key is to be activated. After that date,
71 the key will be included in the zone and used to sign it.
72 -R date/offset
74 Sets the date on which the key is to be revoked. After that date,
75 the key will be flagged as revoked. It will be included in the zone
76 and will be used to sign it.
77 -I date/offset
79 Sets the date on which the key is to be retired. After that date,
80 the key will still be included in the zone, but it will not be used
81 to sign it.
82 -D date/offset
84 Sets the date on which the key is to be deleted. After that date,
85 the key will no longer be included in the zone. (It may remain in
86 the key repository, however.)
87 -S predecessor key
89 Select a key for which the key being modified will be an explicit
90 successor. The name, algorithm, size, and type of the predecessor
91 key must exactly match those of the key being modified. The
92 activation date of the successor key will be set to the
93 inactivation date of the predecessor. The publication date will be
94 set to the activation date minus the prepublication interval, which
95 defaults to 30 days.
96 -i interval
98 Sets the prepublication interval for a key. If set, then the
99 publication and activation dates must be separated by at least this
100 much time. If the activation date is specified but the publication
101 date isn't, then the publication date will default to this much
102 time before the activation date; conversely, if the publication
103 date is specified but activation date isn't, then activation will
104 be set to this much time after publication.
105 If the key is being set to be an explicit successor to another key,
107 then the default prepublication interval is 30 days; otherwise it
108 is zero.
109 As with date offsets, if the argument is followed by one of the
111 suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the interval is
112 measured in years, months, weeks, days, hours, or minutes,
113 respectively. Without a suffix, the interval is measured in
114 seconds.
115
117 dnssec-settime can also be used to print the timing metadata associated
118 with a key.
119 -u
121 Print times in UNIX epoch format.
122 -p C/P/A/R/I/D/all
124 Print a specific metadata value or set of metadata values. The -p
125 option may be followed by one or more of the following letters to
126 indicate which value or values to print: C for the creation date, P
127 for the publication date, A for the activation date, R for the
128 revocation date, I for the inactivation date, or D for the deletion
129 date. To print all of the metadata, use -p all.
130
132 dnssec-keygen(8), dnssec-signzone(8), BIND 9 Administrator Reference
133 Manual, RFC 5011.
134
136 Internet Systems Consortium
137
139 Copyright © 2009-2011 Internet Systems Consortium, Inc. ("ISC")
140BIND9 July 15, 2009 DNSSEC-SETTIME(8)