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
30 -f
31 Force an update of an old-format key with no metadata fields.
32 Without this option, dnssec-settime will fail when attempting to
33 update a legacy key. With this option, the key will be recreated in
34 the new format, but with the original key data retained. The key's
35 creation date will be set to the present time. If no other values
36 are specified, then the key's publication and activation dates will
37 also be set to the present time.
38 -K directory
40 Sets the directory in which the key files are to reside.
41 -h
43 Emit usage message and exit.
44 -v level
46 Sets the debugging level.
47 -E engine
49 Use the given OpenSSL engine. When compiled with PKCS#11 support it
50 defaults to pkcs11; the empty name resets it to no engine.
51
53 Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the
54 argument begins with a '+' or '-', it is interpreted as an offset from
55 the present time. For convenience, if such an offset is followed by one
56 of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the offset is
57 computed in years (defined as 365 24-hour days, ignoring leap years),
58 months (defined as 30 24-hour days), weeks, days, hours, or minutes,
59 respectively. Without a suffix, the offset is computed in seconds. To
60 unset a date, use 'none'.
61 -P date/offset
63 Sets the date on which a key is to be published to the zone. After
64 that date, the key will be included in the zone but will not be
65 used to sign it.
66 -A date/offset
68 Sets the date on which the key is to be activated. After that date,
69 the key will be included in the zone and used to sign it.
70 -R date/offset
72 Sets the date on which the key is to be revoked. After that date,
73 the key will be flagged as revoked. It will be included in the zone
74 and will be used to sign it.
75 -I date/offset
77 Sets the date on which the key is to be retired. After that date,
78 the key will still be included in the zone, but it will not be used
79 to sign it.
80 -D date/offset
82 Sets the date on which the key is to be deleted. After that date,
83 the key will no longer be included in the zone. (It may remain in
84 the key repository, however.)
85 -S predecessor key
87 Select a key for which the key being modified will be an explicit
88 successor. The name, algorithm, size, and type of the predecessor
89 key must exactly match those of the key being modified. The
90 activation date of the successor key will be set to the
91 inactivation date of the predecessor. The publication date will be
92 set to the activation date minus the prepublication interval, which
93 defaults to 30 days.
94 -i interval
96 Sets the prepublication interval for a key. If set, then the
97 publication and activation dates must be separated by at least this
98 much time. If the activation date is specified but the publication
99 date isn't, then the publication date will default to this much
100 time before the activation date; conversely, if the publication
101 date is specified but activation date isn't, then activation will
102 be set to this much time after publication.
103 If the key is being set to be an explicit successor to another key,
105 then the default prepublication interval is 30 days; otherwise it
106 is zero.
107 As with date offsets, if the argument is followed by one of the
109 suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the interval is
110 measured in years, months, weeks, days, hours, or minutes,
111 respectively. Without a suffix, the interval is measured in
112 seconds.
113
115 dnssec-settime can also be used to print the timing metadata associated
116 with a key.
117 -u
119 Print times in UNIX epoch format.
120 -p C/P/A/R/I/D/all
122 Print a specific metadata value or set of metadata values. The -p
123 option may be followed by one or more of the following letters to
124 indicate which value or values to print: C for the creation date, P
125 for the publication date, A for the activation date, R for the
126 revocation date, I for the inactivation date, or D for the deletion
127 date. To print all of the metadata, use -p all.
128
130 dnssec-keygen(8), dnssec-signzone(8), BIND 9 Administrator Reference
131 Manual, RFC 5011.
132
134 Internet Systems Consortium
135
137 Copyright © 2009-2011 Internet Systems Consortium, Inc. ("ISC")
138BIND9 July 15, 2009 DNSSEC-SETTIME(8)