Update repub branch u/fanf2/patch to rebasing branch u/fanf2/rebasing revision v9_13_...
[ipreg/bind9.git] / bin / dnssec / dnssec-signzone.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2 <!--
3 - Copyright (C) 2000-2009, 2011-2019 Internet Systems Consortium, Inc. ("ISC")
4 -
5 - This Source Code Form is subject to the terms of the Mozilla Public
6 - License, v. 2.0. If a copy of the MPL was not distributed with this
7 - file, You can obtain one at http://mozilla.org/MPL/2.0/.
8 -->
9 <html lang="en">
10 <head>
11 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
12 <title>dnssec-signzone</title>
13 <meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
14 </head>
15 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
16 <a name="man.dnssec-signzone"></a><div class="titlepage"></div>
22 <div class="refnamediv">
23 <h2>Name</h2>
24 <p>
25 <span class="application">dnssec-signzone</span>
26 &#8212; DNSSEC zone signing tool
27 </p>
28 </div>
32 <div class="refsynopsisdiv">
33 <h2>Synopsis</h2>
34 <div class="cmdsynopsis"><p>
35 <code class="command">dnssec-signzone</code>
36 [<code class="option">-a</code>]
37 [<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
38 [<code class="option">-d <em class="replaceable"><code>directory</code></em></code>]
39 [<code class="option">-D</code>]
40 [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>]
41 [<code class="option">-e <em class="replaceable"><code>end-time</code></em></code>]
42 [<code class="option">-f <em class="replaceable"><code>output-file</code></em></code>]
43 [<code class="option">-g</code>]
44 [<code class="option">-h</code>]
45 [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>]
46 [<code class="option">-I <em class="replaceable"><code>input-format</code></em></code>]
47 [<code class="option">-j <em class="replaceable"><code>jitter</code></em></code>]
48 [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>]
49 [<code class="option">-k <em class="replaceable"><code>key</code></em></code>]
50 [<code class="option">-L <em class="replaceable"><code>serial</code></em></code>]
51 [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>]
52 [<code class="option">-M <em class="replaceable"><code>maxttl</code></em></code>]
53 [<code class="option">-N <em class="replaceable"><code>soa-serial-format</code></em></code>]
54 [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>]
55 [<code class="option">-O <em class="replaceable"><code>output-format</code></em></code>]
56 [<code class="option">-P</code>]
57 [<code class="option">-Q</code>]
58 [<code class="option">-R</code>]
59 [<code class="option">-S</code>]
60 [<code class="option">-s <em class="replaceable"><code>start-time</code></em></code>]
61 [<code class="option">-T <em class="replaceable"><code>ttl</code></em></code>]
62 [<code class="option">-t</code>]
63 [<code class="option">-u</code>]
64 [<code class="option">-v <em class="replaceable"><code>level</code></em></code>]
65 [<code class="option">-V</code>]
66 [<code class="option">-X <em class="replaceable"><code>extended end-time</code></em></code>]
67 [<code class="option">-x</code>]
68 [<code class="option">-z</code>]
69 [<code class="option">-3 <em class="replaceable"><code>salt</code></em></code>]
70 [<code class="option">-H <em class="replaceable"><code>iterations</code></em></code>]
71 [<code class="option">-A</code>]
72 {zonefile}
73 [key...]
74 </p></div>
75 </div>
77 <div class="refsection">
78 <a name="id-1.7"></a><h2>DESCRIPTION</h2>
80 <p><span class="command"><strong>dnssec-signzone</strong></span>
81 signs a zone. It generates
82 NSEC and RRSIG records and produces a signed version of the
83 zone. The security status of delegations from the signed zone
84 (that is, whether the child zones are secure or not) is
85 determined by the presence or absence of a
86 <code class="filename">keyset</code> file for each child zone.
87 </p>
88 </div>
90 <div class="refsection">
91 <a name="id-1.8"></a><h2>OPTIONS</h2>
94 <div class="variablelist"><dl class="variablelist">
95 <dt><span class="term">-a</span></dt>
96 <dd>
97 <p>
98 Verify all generated signatures.
99 </p>
100 </dd>
101 <dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
102 <dd>
103 <p>
104 Specifies the DNS class of the zone.
105 </p>
106 </dd>
107 <dt><span class="term">-C</span></dt>
108 <dd>
109 <p>
110 Compatibility mode: Generate a
111 <code class="filename">keyset-<em class="replaceable"><code>zonename</code></em></code>
112 file in addition to
113 <code class="filename">dsset-<em class="replaceable"><code>zonename</code></em></code>
114 when signing a zone, for use by older versions of
115 <span class="command"><strong>dnssec-signzone</strong></span>.
116 </p>
117 </dd>
118 <dt><span class="term">-d <em class="replaceable"><code>directory</code></em></span></dt>
119 <dd>
120 <p>
121 Look for <code class="filename">dsset-</code> or
122 <code class="filename">keyset-</code> files in <code class="option">directory</code>.
123 </p>
124 </dd>
125 <dt><span class="term">-D</span></dt>
126 <dd>
127 <p>
128 Output only those record types automatically managed by
129 <span class="command"><strong>dnssec-signzone</strong></span>, i.e. RRSIG, NSEC,
130 NSEC3 and NSEC3PARAM records. If smart signing
131 (<code class="option">-S</code>) is used, DNSKEY records are also
132 included. The resulting file can be included in the original
133 zone file with <span class="command"><strong>$INCLUDE</strong></span>. This option
134 cannot be combined with <code class="option">-O raw</code>,
135 <code class="option">-O map</code>, or serial number updating.
136 </p>
137 </dd>
138 <dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
139 <dd>
140 <p>
141 When applicable, specifies the hardware to use for
142 cryptographic operations, such as a secure key store used
143 for signing.
144 </p>
145 <p>
146 When BIND is built with OpenSSL PKCS#11 support, this defaults
147 to the string "pkcs11", which identifies an OpenSSL engine
148 that can drive a cryptographic accelerator or hardware service
149 module. When BIND is built with native PKCS#11 cryptography
150 (--enable-native-pkcs11), it defaults to the path of the PKCS#11
151 provider library specified via "--with-pkcs11".
152 </p>
153 </dd>
154 <dt><span class="term">-g</span></dt>
155 <dd>
156 <p>
157 Generate DS records for child zones from
158 <code class="filename">dsset-</code> or <code class="filename">keyset-</code>
159 file. Existing DS records will be removed.
160 </p>
161 </dd>
162 <dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
163 <dd>
164 <p>
165 Key repository: Specify a directory to search for DNSSEC keys.
166 If not specified, defaults to the current directory.
167 </p>
168 </dd>
169 <dt><span class="term">-k <em class="replaceable"><code>key</code></em></span></dt>
170 <dd>
171 <p>
172 Treat specified key as a key signing key ignoring any
173 key flags. This option may be specified multiple times.
174 </p>
175 </dd>
176 <dt><span class="term">-l <em class="replaceable"><code>domain</code></em></span></dt>
177 <dd>
178 <p>
179 Generate a DLV set in addition to the key (DNSKEY) and DS sets.
180 The domain is appended to the name of the records.
181 </p>
182 </dd>
183 <dt><span class="term">-M <em class="replaceable"><code>maxttl</code></em></span></dt>
184 <dd>
185 <p>
186 Sets the maximum TTL for the signed zone.
187 Any TTL higher than <em class="replaceable"><code>maxttl</code></em> in the
188 input zone will be reduced to <em class="replaceable"><code>maxttl</code></em>
189 in the output. This provides certainty as to the largest
190 possible TTL in the signed zone, which is useful to know when
191 rolling keys because it is the longest possible time before
192 signatures that have been retrieved by resolvers will expire
193 from resolver caches. Zones that are signed with this
194 option should be configured to use a matching
195 <code class="option">max-zone-ttl</code> in <code class="filename">named.conf</code>.
196 (Note: This option is incompatible with <code class="option">-D</code>,
197 because it modifies non-DNSSEC data in the output zone.)
198 </p>
199 </dd>
200 <dt><span class="term">-s <em class="replaceable"><code>start-time</code></em></span></dt>
201 <dd>
202 <p>
203 Specify the date and time when the generated RRSIG records
204 become valid. This can be either an absolute or relative
205 time. An absolute start time is indicated by a number
206 in YYYYMMDDHHMMSS notation; 20000530144500 denotes
207 14:45:00 UTC on May 30th, 2000. A relative start time is
208 indicated by +N, which is N seconds from the current time.
209 If no <code class="option">start-time</code> is specified, the current
210 time minus 1 hour (to allow for clock skew) is used.
211 </p>
212 </dd>
213 <dt><span class="term">-e <em class="replaceable"><code>end-time</code></em></span></dt>
214 <dd>
215 <p>
216 Specify the date and time when the generated RRSIG records
217 expire. As with <code class="option">start-time</code>, an absolute
218 time is indicated in YYYYMMDDHHMMSS notation. A time relative
219 to the start time is indicated with +N, which is N seconds from
220 the start time. A time relative to the current time is
221 indicated with now+N. If no <code class="option">end-time</code> is
222 specified, 30 days from the start time is used as a default.
223 <code class="option">end-time</code> must be later than
224 <code class="option">start-time</code>.
225 </p>
226 </dd>
227 <dt><span class="term">-X <em class="replaceable"><code>extended end-time</code></em></span></dt>
228 <dd>
229 <p>
230 Specify the date and time when the generated RRSIG records
231 for the DNSKEY RRset will expire. This is to be used in cases
232 when the DNSKEY signatures need to persist longer than
233 signatures on other records; e.g., when the private component
234 of the KSK is kept offline and the KSK signature is to be
235 refreshed manually.
236 </p>
237 <p>
238 As with <code class="option">start-time</code>, an absolute
239 time is indicated in YYYYMMDDHHMMSS notation. A time relative
240 to the start time is indicated with +N, which is N seconds from
241 the start time. A time relative to the current time is
242 indicated with now+N. If no <code class="option">extended end-time</code> is
243 specified, the value of <code class="option">end-time</code> is used as
244 the default. (<code class="option">end-time</code>, in turn, defaults to
245 30 days from the start time.) <code class="option">extended end-time</code>
246 must be later than <code class="option">start-time</code>.
247 </p>
248 </dd>
249 <dt><span class="term">-f <em class="replaceable"><code>output-file</code></em></span></dt>
250 <dd>
251 <p>
252 The name of the output file containing the signed zone. The
253 default is to append <code class="filename">.signed</code> to
254 the input filename. If <code class="option">output-file</code> is
255 set to <code class="literal">"-"</code>, then the signed zone is
256 written to the standard output, with a default output
257 format of "full".
258 </p>
259 </dd>
260 <dt><span class="term">-h</span></dt>
261 <dd>
262 <p>
263 Prints a short summary of the options and arguments to
264 <span class="command"><strong>dnssec-signzone</strong></span>.
265 </p>
266 </dd>
267 <dt><span class="term">-V</span></dt>
268 <dd>
269 <p>
270 Prints version information.
271 </p>
272 </dd>
273 <dt><span class="term">-i <em class="replaceable"><code>interval</code></em></span></dt>
274 <dd>
275 <p>
276 When a previously-signed zone is passed as input, records
277 may be resigned. The <code class="option">interval</code> option
278 specifies the cycle interval as an offset from the current
279 time (in seconds). If a RRSIG record expires after the
280 cycle interval, it is retained. Otherwise, it is considered
281 to be expiring soon, and it will be replaced.
282 </p>
283 <p>
284 The default cycle interval is one quarter of the difference
285 between the signature end and start times. So if neither
286 <code class="option">end-time</code> or <code class="option">start-time</code>
287 are specified, <span class="command"><strong>dnssec-signzone</strong></span>
288 generates
289 signatures that are valid for 30 days, with a cycle
290 interval of 7.5 days. Therefore, if any existing RRSIG records
291 are due to expire in less than 7.5 days, they would be
292 replaced.
293 </p>
294 </dd>
295 <dt><span class="term">-I <em class="replaceable"><code>input-format</code></em></span></dt>
296 <dd>
297 <p>
298 The format of the input zone file.
299 Possible formats are <span class="command"><strong>"text"</strong></span> (default),
300 <span class="command"><strong>"raw"</strong></span>, and <span class="command"><strong>"map"</strong></span>.
301 This option is primarily intended to be used for dynamic
302 signed zones so that the dumped zone file in a non-text
303 format containing updates can be signed directly.
304 The use of this option does not make much sense for
305 non-dynamic zones.
306 </p>
307 </dd>
308 <dt><span class="term">-j <em class="replaceable"><code>jitter</code></em></span></dt>
309 <dd>
310 <p>
311 When signing a zone with a fixed signature lifetime, all
312 RRSIG records issued at the time of signing expires
313 simultaneously. If the zone is incrementally signed, i.e.
314 a previously-signed zone is passed as input to the signer,
315 all expired signatures have to be regenerated at about the
316 same time. The <code class="option">jitter</code> option specifies a
317 jitter window that will be used to randomize the signature
318 expire time, thus spreading incremental signature
319 regeneration over time.
320 </p>
321 <p>
322 Signature lifetime jitter also to some extent benefits
323 validators and servers by spreading out cache expiration,
324 i.e. if large numbers of RRSIGs don't expire at the same time
325 from all caches there will be less congestion than if all
326 validators need to refetch at mostly the same time.
327 </p>
328 </dd>
329 <dt><span class="term">-L <em class="replaceable"><code>serial</code></em></span></dt>
330 <dd>
331 <p>
332 When writing a signed zone to "raw" or "map" format, set the
333 "source serial" value in the header to the specified serial
334 number. (This is expected to be used primarily for testing
335 purposes.)
336 </p>
337 </dd>
338 <dt><span class="term">-n <em class="replaceable"><code>ncpus</code></em></span></dt>
339 <dd>
340 <p>
341 Specifies the number of threads to use. By default, one
342 thread is started for each detected CPU.
343 </p>
344 </dd>
345 <dt><span class="term">-N <em class="replaceable"><code>soa-serial-format</code></em></span></dt>
346 <dd>
347 <p>
348 The SOA serial number format of the signed zone.
349 Possible formats are <span class="command"><strong>"keep"</strong></span> (default),
350 <span class="command"><strong>"increment"</strong></span>, <span class="command"><strong>"unixtime"</strong></span>,
351 and <span class="command"><strong>"date"</strong></span>.
352 </p>
354 <div class="variablelist"><dl class="variablelist">
355 <dt><span class="term"><span class="command"><strong>"keep"</strong></span></span></dt>
356 <dd>
357 <p>Do not modify the SOA serial number.</p>
358 </dd>
359 <dt><span class="term"><span class="command"><strong>"increment"</strong></span></span></dt>
360 <dd>
361 <p>Increment the SOA serial number using RFC 1982
362 arithmetics.</p>
363 </dd>
364 <dt><span class="term"><span class="command"><strong>"unixtime"</strong></span></span></dt>
365 <dd>
366 <p>Set the SOA serial number to the number of seconds
367 since epoch.</p>
368 </dd>
369 <dt><span class="term"><span class="command"><strong>"date"</strong></span></span></dt>
370 <dd>
371 <p>Set the SOA serial number to today's date in
372 YYYYMMDDNN format.</p>
373 </dd>
374 </dl></div>
376 </dd>
377 <dt><span class="term">-o <em class="replaceable"><code>origin</code></em></span></dt>
378 <dd>
379 <p>
380 The zone origin. If not specified, the name of the zone file
381 is assumed to be the origin.
382 </p>
383 </dd>
384 <dt><span class="term">-O <em class="replaceable"><code>output-format</code></em></span></dt>
385 <dd>
386 <p>
387 The format of the output file containing the signed zone.
388 Possible formats are <span class="command"><strong>"text"</strong></span> (default),
389 which is the standard textual representation of the zone;
390 <span class="command"><strong>"full"</strong></span>, which is text output in a
391 format suitable for processing by external scripts;
392 and <span class="command"><strong>"map"</strong></span>, <span class="command"><strong>"raw"</strong></span>,
393 and <span class="command"><strong>"raw=N"</strong></span>, which store the zone in
394 binary formats for rapid loading by <span class="command"><strong>named</strong></span>.
395 <span class="command"><strong>"raw=N"</strong></span> specifies the format version of
396 the raw zone file: if N is 0, the raw file can be read by
397 any version of <span class="command"><strong>named</strong></span>; if N is 1, the file
398 can be read by release 9.9.0 or higher; the default is 1.
399 </p>
400 </dd>
401 <dt><span class="term">-P</span></dt>
402 <dd>
403 <p>
404 Disable post sign verification tests.
405 </p>
406 <p>
407 The post sign verification test ensures that for each algorithm
408 in use there is at least one non revoked self signed KSK key,
409 that all revoked KSK keys are self signed, and that all records
410 in the zone are signed by the algorithm.
411 This option skips these tests.
412 </p>
413 </dd>
414 <dt><span class="term">-Q</span></dt>
415 <dd>
416 <p>
417 Remove signatures from keys that are no longer active.
418 </p>
419 <p>
420 Normally, when a previously-signed zone is passed as input
421 to the signer, and a DNSKEY record has been removed and
422 replaced with a new one, signatures from the old key
423 that are still within their validity period are retained.
424 This allows the zone to continue to validate with cached
425 copies of the old DNSKEY RRset. The <code class="option">-Q</code>
426 forces <span class="command"><strong>dnssec-signzone</strong></span> to remove
427 signatures from keys that are no longer active. This
428 enables ZSK rollover using the procedure described in
429 RFC 4641, section ("Pre-Publish Key Rollover").
430 </p>
431 </dd>
432 <dt><span class="term">-R</span></dt>
433 <dd>
434 <p>
435 Remove signatures from keys that are no longer published.
436 </p>
437 <p>
438 This option is similar to <code class="option">-Q</code>, except it
439 forces <span class="command"><strong>dnssec-signzone</strong></span> to signatures from
440 keys that are no longer published. This enables ZSK rollover
441 using the procedure described in RFC 4641, section
442 ("Double Signature Zone Signing Key Rollover").
443 </p>
444 </dd>
445 <dt><span class="term">-S</span></dt>
446 <dd>
447 <p>
448 Smart signing: Instructs <span class="command"><strong>dnssec-signzone</strong></span> to
449 search the key repository for keys that match the zone being
450 signed, and to include them in the zone if appropriate.
451 </p>
452 <p>
453 When a key is found, its timing metadata is examined to
454 determine how it should be used, according to the following
455 rules. Each successive rule takes priority over the prior
456 ones:
457 </p>
458 <div class="variablelist"><dl class="variablelist">
459 <dt></dt>
460 <dd>
461 <p>
462 If no timing metadata has been set for the key, the key is
463 published in the zone and used to sign the zone.
464 </p>
465 </dd>
466 <dt></dt>
467 <dd>
468 <p>
469 If the key's publication date is set and is in the past, the
470 key is published in the zone.
471 </p>
472 </dd>
473 <dt></dt>
474 <dd>
475 <p>
476 If the key's activation date is set and in the past, the
477 key is published (regardless of publication date) and
478 used to sign the zone.
479 </p>
480 </dd>
481 <dt></dt>
482 <dd>
483 <p>
484 If the key's revocation date is set and in the past, and the
485 key is published, then the key is revoked, and the revoked key
486 is used to sign the zone.
487 </p>
488 </dd>
489 <dt></dt>
490 <dd>
491 <p>
492 If either of the key's unpublication or deletion dates are set
493 and in the past, the key is NOT published or used to sign the
494 zone, regardless of any other metadata.
495 </p>
496 </dd>
497 <dt></dt>
498 <dd>
499 <p>
500 If key's sync publication date is set and in the past,
501 synchronization records (type CDS and/or CDNSKEY) are
502 created.
503 </p>
504 </dd>
505 <dt></dt>
506 <dd>
507 <p>
508 If key's sync deletion date is set and in the past,
509 synchronization records (type CDS and/or CDNSKEY) are
510 removed.
511 </p>
512 </dd>
513 </dl></div>
514 </dd>
515 <dt><span class="term">-T <em class="replaceable"><code>ttl</code></em></span></dt>
516 <dd>
517 <p>
518 Specifies a TTL to be used for new DNSKEY records imported
519 into the zone from the key repository. If not
520 specified, the default is the TTL value from the zone's SOA
521 record. This option is ignored when signing without
522 <code class="option">-S</code>, since DNSKEY records are not imported
523 from the key repository in that case. It is also ignored if
524 there are any pre-existing DNSKEY records at the zone apex,
525 in which case new records' TTL values will be set to match
526 them, or if any of the imported DNSKEY records had a default
527 TTL value. In the event of a a conflict between TTL values in
528 imported keys, the shortest one is used.
529 </p>
530 </dd>
531 <dt><span class="term">-t</span></dt>
532 <dd>
533 <p>
534 Print statistics at completion.
535 </p>
536 </dd>
537 <dt><span class="term">-u</span></dt>
538 <dd>
539 <p>
540 Update NSEC/NSEC3 chain when re-signing a previously signed
541 zone. With this option, a zone signed with NSEC can be
542 switched to NSEC3, or a zone signed with NSEC3 can
543 be switch to NSEC or to NSEC3 with different parameters.
544 Without this option, <span class="command"><strong>dnssec-signzone</strong></span> will
545 retain the existing chain when re-signing.
546 </p>
547 </dd>
548 <dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
549 <dd>
550 <p>
551 Sets the debugging level.
552 </p>
553 </dd>
554 <dt><span class="term">-x</span></dt>
555 <dd>
556 <p>
557 Only sign the DNSKEY, CDNSKEY, and CDS RRsets with
558 key-signing keys, and omit signatures from zone-signing
559 keys. (This is similar to the
560 <span class="command"><strong>dnssec-dnskey-kskonly yes;</strong></span> zone option in
561 <span class="command"><strong>named</strong></span>.)
562 </p>
563 </dd>
564 <dt><span class="term">-z</span></dt>
565 <dd>
566 <p>
567 Ignore KSK flag on key when determining what to sign. This
568 causes KSK-flagged keys to sign all records, not just the
569 DNSKEY RRset. (This is similar to the
570 <span class="command"><strong>update-check-ksk no;</strong></span> zone option in
571 <span class="command"><strong>named</strong></span>.)
572 </p>
573 </dd>
574 <dt><span class="term">-3 <em class="replaceable"><code>salt</code></em></span></dt>
575 <dd>
576 <p>
577 Generate an NSEC3 chain with the given hex encoded salt.
578 A dash (<em class="replaceable"><code>salt</code></em>) can
579 be used to indicate that no salt is to be used when generating the NSEC3 chain.
580 </p>
581 </dd>
582 <dt><span class="term">-H <em class="replaceable"><code>iterations</code></em></span></dt>
583 <dd>
584 <p>
585 When generating an NSEC3 chain, use this many iterations. The
586 default is 10.
587 </p>
588 </dd>
589 <dt><span class="term">-A</span></dt>
590 <dd>
591 <p>
592 When generating an NSEC3 chain set the OPTOUT flag on all
593 NSEC3 records and do not generate NSEC3 records for insecure
594 delegations.
595 </p>
596 <p>
597 Using this option twice (i.e., <code class="option">-AA</code>)
598 turns the OPTOUT flag off for all records. This is useful
599 when using the <code class="option">-u</code> option to modify an NSEC3
600 chain which previously had OPTOUT set.
601 </p>
602 </dd>
603 <dt><span class="term">zonefile</span></dt>
604 <dd>
605 <p>
606 The file containing the zone to be signed.
607 </p>
608 </dd>
609 <dt><span class="term">key</span></dt>
610 <dd>
611 <p>
612 Specify which keys should be used to sign the zone. If
613 no keys are specified, then the zone will be examined
614 for DNSKEY records at the zone apex. If these are found and
615 there are matching private keys, in the current directory,
616 then these will be used for signing.
617 </p>
618 </dd>
619 </dl></div>
620 </div>
622 <div class="refsection">
623 <a name="id-1.9"></a><h2>EXAMPLE</h2>
625 <p>
626 The following command signs the <strong class="userinput"><code>example.com</code></strong>
627 zone with the ECDSAP256SHA256 key generated by key generated by
628 <span class="command"><strong>dnssec-keygen</strong></span> (Kexample.com.+013+17247).
629 Because the <span class="command"><strong>-S</strong></span> option is not being used,
630 the zone's keys must be in the master file
631 (<code class="filename">db.example.com</code>). This invocation looks
632 for <code class="filename">dsset</code> files, in the current directory,
633 so that DS records can be imported from them (<span class="command"><strong>-g</strong></span>).
634 </p>
635 <pre class="programlisting">% dnssec-signzone -g -o example.com db.example.com \
636 Kexample.com.+013+17247
637 db.example.com.signed
638 %</pre>
639 <p>
640 In the above example, <span class="command"><strong>dnssec-signzone</strong></span> creates
641 the file <code class="filename">db.example.com.signed</code>. This
642 file should be referenced in a zone statement in a
643 <code class="filename">named.conf</code> file.
644 </p>
645 <p>
646 This example re-signs a previously signed zone with default parameters.
647 The private keys are assumed to be in the current directory.
648 </p>
649 <pre class="programlisting">% cp db.example.com.signed db.example.com
650 % dnssec-signzone -o example.com db.example.com
651 db.example.com.signed
652 %</pre>
653 </div>
655 <div class="refsection">
656 <a name="id-1.10"></a><h2>SEE ALSO</h2>
658 <p><span class="citerefentry">
659 <span class="refentrytitle">dnssec-keygen</span>(8)
660 </span>,
661 <em class="citetitle">BIND 9 Administrator Reference Manual</em>,
662 <em class="citetitle">RFC 4033</em>, <em class="citetitle">RFC 4641</em>.
663 </p>
664 </div>
666 </div></body>
667 </html>