1DNSSEC-SIGNZONE(8) BIND9 DNSSEC-SIGNZONE(8)
2
6 dnssec-signzone - DNSSEC zone signing tool
7
9 dnssec-signzone [-a] [-c class] [-d directory] [-E engine]
10 [-e end-time] [-f output-file] [-g] [-h] [-K directory]
11 [-k key] [-l domain] [-i interval] [-I input-format]
12 [-j jitter] [-N soa-serial-format] [-o origin]
13 [-O output-format] [-p] [-P] [-r randomdev] [-S]
14 [-s start-time] [-T ttl] [-t] [-u] [-v level] [-x] [-z]
15 [-3 salt] [-H iterations] [-A] {zonefile} [key...]
16
18 dnssec-signzone signs a zone. It generates NSEC and RRSIG records and
19 produces a signed version of the zone. The security status of
20 delegations from the signed zone (that is, whether the child zones are
21 secure or not) is determined by the presence or absence of a keyset
22 file for each child zone.
23
25 -a
26 Verify all generated signatures.
27 -c class
29 Specifies the DNS class of the zone.
30 -C
32 Compatibility mode: Generate a keyset-zonename file in addition to
33 dsset-zonename when signing a zone, for use by older versions of
34 dnssec-signzone.
35 -d directory
37 Look for dsset- or keyset- files in directory.
38 -E engine
40 Uses a crypto hardware (OpenSSL engine) for the crypto operations
41 it supports, for instance signing with private keys from a secure
42 key store. When compiled with PKCS#11 support it defaults to
43 pkcs11; the empty name resets it to no engine.
44 -g
46 Generate DS records for child zones from dsset- or keyset- file.
47 Existing DS records will be removed.
48 -K directory
50 Key repository: Specify a directory to search for DNSSEC keys. If
51 not specified, defaults to the current directory.
52 -k key
54 Treat specified key as a key signing key ignoring any key flags.
55 This option may be specified multiple times.
56 -l domain
58 Generate a DLV set in addition to the key (DNSKEY) and DS sets. The
59 domain is appended to the name of the records.
60 -s start-time
62 Specify the date and time when the generated RRSIG records become
63 valid. This can be either an absolute or relative time. An absolute
64 start time is indicated by a number in YYYYMMDDHHMMSS notation;
65 20000530144500 denotes 14:45:00 UTC on May 30th, 2000. A relative
66 start time is indicated by +N, which is N seconds from the current
67 time. If no start-time is specified, the current time minus 1 hour
68 (to allow for clock skew) is used.
69 -e end-time
71 Specify the date and time when the generated RRSIG records expire.
72 As with start-time, an absolute time is indicated in YYYYMMDDHHMMSS
73 notation. A time relative to the start time is indicated with +N,
74 which is N seconds from the start time. A time relative to the
75 current time is indicated with now+N. If no end-time is specified,
76 30 days from the start time is used as a default. end-time must be
77 later than start-time.
78 -f output-file
80 The name of the output file containing the signed zone. The default
81 is to append .signed to the input filename.
82 -h
84 Prints a short summary of the options and arguments to
85 dnssec-signzone.
86 -i interval
88 When a previously-signed zone is passed as input, records may be
89 resigned. The interval option specifies the cycle interval as an
90 offset from the current time (in seconds). If a RRSIG record
91 expires after the cycle interval, it is retained. Otherwise, it is
92 considered to be expiring soon, and it will be replaced.
93 The default cycle interval is one quarter of the difference between
95 the signature end and start times. So if neither end-time or
96 start-time are specified, dnssec-signzone generates signatures that
97 are valid for 30 days, with a cycle interval of 7.5 days.
98 Therefore, if any existing RRSIG records are due to expire in less
99 than 7.5 days, they would be replaced.
100 -I input-format
102 The format of the input zone file. Possible formats are "text"
103 (default) and "raw". This option is primarily intended to be used
104 for dynamic signed zones so that the dumped zone file in a non-text
105 format containing updates can be signed directly. The use of this
106 option does not make much sense for non-dynamic zones.
107 -j jitter
109 When signing a zone with a fixed signature lifetime, all RRSIG
110 records issued at the time of signing expires simultaneously. If
111 the zone is incrementally signed, i.e. a previously-signed zone is
112 passed as input to the signer, all expired signatures have to be
113 regenerated at about the same time. The jitter option specifies a
114 jitter window that will be used to randomize the signature expire
115 time, thus spreading incremental signature regeneration over time.
116 Signature lifetime jitter also to some extent benefits validators
118 and servers by spreading out cache expiration, i.e. if large
119 numbers of RRSIGs don't expire at the same time from all caches
120 there will be less congestion than if all validators need to
121 refetch at mostly the same time.
122 -n ncpus
124 Specifies the number of threads to use. By default, one thread is
125 started for each detected CPU.
126 -N soa-serial-format
128 The SOA serial number format of the signed zone. Possible formats
129 are "keep" (default), "increment" and "unixtime".
130 "keep"
132 Do not modify the SOA serial number.
133 "increment"
135 Increment the SOA serial number using RFC 1982 arithmetics.
136 "unixtime"
138 Set the SOA serial number to the number of seconds since
139 epoch.
140 -o origin
142 The zone origin. If not specified, the name of the zone file is
143 assumed to be the origin.
144 -O output-format
146 The format of the output file containing the signed zone. Possible
147 formats are "text" (default) and "raw".
148 -p
150 Use pseudo-random data when signing the zone. This is faster, but
151 less secure, than using real random data. This option may be useful
152 when signing large zones or when the entropy source is limited.
153 -P
155 Disable post sign verification tests.
156 The post sign verification test ensures that for each algorithm in
158 use there is at least one non revoked self signed KSK key, that all
159 revoked KSK keys are self signed, and that all records in the zone
160 are signed by the algorithm. This option skips these tests.
161 -r randomdev
163 Specifies the source of randomness. If the operating system does
164 not provide a /dev/random or equivalent device, the default source
165 of randomness is keyboard input. randomdev specifies the name of a
166 character device or file containing random data to be used instead
167 of the default. The special value keyboard indicates that keyboard
168 input should be used.
169 -S
171 Smart signing: Instructs dnssec-signzone to search the key
172 repository for keys that match the zone being signed, and to
173 include them in the zone if appropriate.
174 When a key is found, its timing metadata is examined to determine
176 how it should be used, according to the following rules. Each
177 successive rule takes priority over the prior ones:
178 If no timing metadata has been set for the key, the key is
180 published in the zone and used to sign the zone.
181 If the key's publication date is set and is in the past,
183 the key is published in the zone.
184 If the key's activation date is set and in the past, the
186 key is published (regardless of publication date) and used
187 to sign the zone.
188 If the key's revocation date is set and in the past, and
190 the key is published, then the key is revoked, and the
191 revoked key is used to sign the zone.
192 If either of the key's unpublication or deletion dates are
194 set and in the past, the key is NOT published or used to
195 sign the zone, regardless of any other metadata.
196 -T ttl
198 Specifies the TTL to be used for new DNSKEY records imported into
199 the zone from the key repository. If not specified, the default is
200 the minimum TTL value from the zone's SOA record. This option is
201 ignored when signing without -S, since DNSKEY records are not
202 imported from the key repository in that case. It is also ignored
203 if there are any pre-existing DNSKEY records at the zone apex, in
204 which case new records' TTL values will be set to match them.
205 -t
207 Print statistics at completion.
208 -u
210 Update NSEC/NSEC3 chain when re-signing a previously signed zone.
211 With this option, a zone signed with NSEC can be switched to NSEC3,
212 or a zone signed with NSEC3 can be switch to NSEC or to NSEC3 with
213 different parameters. Without this option, dnssec-signzone will
214 retain the existing chain when re-signing.
215 -v level
217 Sets the debugging level.
218 -x
220 Only sign the DNSKEY RRset with key-signing keys, and omit
221 signatures from zone-signing keys. (This is similar to the
222 dnssec-dnskey-kskonly yes; zone option in named.)
223 -z
225 Ignore KSK flag on key when determining what to sign. This causes
226 KSK-flagged keys to sign all records, not just the DNSKEY RRset.
227 (This is similar to the update-check-ksk no; zone option in named.)
228 -3 salt
230 Generate an NSEC3 chain with the given hex encoded salt. A dash
231 (salt) can be used to indicate that no salt is to be used when
232 generating the NSEC3 chain.
233 -H iterations
235 When generating an NSEC3 chain, use this many interations. The
236 default is 10.
237 -A
239 When generating an NSEC3 chain set the OPTOUT flag on all NSEC3
240 records and do not generate NSEC3 records for insecure delegations.
241 Using this option twice (i.e., -AA) turns the OPTOUT flag off for
243 all records. This is useful when using the -u option to modify an
244 NSEC3 chain which previously had OPTOUT set.
245 zonefile
247 The file containing the zone to be signed.
248 key
250 Specify which keys should be used to sign the zone. If no keys are
251 specified, then the zone will be examined for DNSKEY records at the
252 zone apex. If these are found and there are matching private keys,
253 in the current directory, then these will be used for signing.
254
256 The following command signs the example.com zone with the DSA key
257 generated by dnssec-keygen (Kexample.com.+003+17247). Because the -S
258 option is not being used, the zone's keys must be in the master file
259 (db.example.com). This invocation looks for dsset files, in the current
260 directory, so that DS records can be imported from them (-g).
261 % dnssec-signzone -g -o example.com db.example.com \
263 Kexample.com.+003+17247
264 db.example.com.signed
265 %
266 In the above example, dnssec-signzone creates the file
268 db.example.com.signed. This file should be referenced in a zone
269 statement in a named.conf file.
270 This example re-signs a previously signed zone with default parameters.
272 The private keys are assumed to be in the current directory.
273 % cp db.example.com.signed db.example.com
275 % dnssec-signzone -o example.com db.example.com
276 db.example.com.signed
277 %
278
280 dnssec-keygen(8), BIND 9 Administrator Reference Manual, RFC 4033.
281
283 Internet Systems Consortium
284
286 Copyright © 2004-2009 Internet Systems Consortium, Inc. ("ISC")
287 Copyright © 2000-2003 Internet Software Consortium.
288BIND9 June 05, 2009 DNSSEC-SIGNZONE(8)