1<!-- 2 - Copyright (C) 2004-2009, 2011-2014 Internet Systems Consortium, Inc. ("ISC") 3 - Copyright (C) 2000-2003 Internet Software Consortium. 4 - 5 - Permission to use, copy, modify, and/or distribute this software for any 6 - purpose with or without fee is hereby granted, provided that the above 7 - copyright notice and this permission notice appear in all copies. 8 - 9 - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 10 - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 11 - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 12 - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 13 - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 14 - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 15 - PERFORMANCE OF THIS SOFTWARE. 16--> 17<!-- Id --> 18<html> 19<head> 20<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> 21<title>dnssec-signzone</title> 22<meta name="generator" content="DocBook XSL Stylesheets V1.71.1"> 23</head> 24<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"> 25<a name="man.dnssec-signzone"></a><div class="titlepage"></div> 26<div class="refnamediv"> 27<h2>Name</h2> 28<p><span class="application">dnssec-signzone</span> — DNSSEC zone signing tool</p> 29</div> 30<div class="refsynopsisdiv"> 31<h2>Synopsis</h2> 32<div class="cmdsynopsis"><p><code class="command">dnssec-signzone</code> [<code class="option">-a</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-d <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-D</code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] [<code class="option">-e <em class="replaceable"><code>end-time</code></em></code>] [<code class="option">-f <em class="replaceable"><code>output-file</code></em></code>] [<code class="option">-g</code>] [<code class="option">-h</code>] [<code class="option">-K <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-k <em class="replaceable"><code>key</code></em></code>] [<code class="option">-L <em class="replaceable"><code>serial</code></em></code>] [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-M <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>] [<code class="option">-I <em class="replaceable"><code>input-format</code></em></code>] [<code class="option">-j <em class="replaceable"><code>jitter</code></em></code>] [<code class="option">-N <em class="replaceable"><code>soa-serial-format</code></em></code>] [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>] [<code class="option">-O <em class="replaceable"><code>output-format</code></em></code>] [<code class="option">-P</code>] [<code class="option">-p</code>] [<code class="option">-R</code>] [<code class="option">-r <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-S</code>] [<code class="option">-s <em class="replaceable"><code>start-time</code></em></code>] [<code class="option">-T <em class="replaceable"><code>ttl</code></em></code>] [<code class="option">-t</code>] [<code class="option">-u</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-V</code>] [<code class="option">-X <em class="replaceable"><code>extended end-time</code></em></code>] [<code class="option">-x</code>] [<code class="option">-z</code>] [<code class="option">-3 <em class="replaceable"><code>salt</code></em></code>] [<code class="option">-H <em class="replaceable"><code>iterations</code></em></code>] [<code class="option">-A</code>] {zonefile} [key...]</p></div> 33</div> 34<div class="refsect1" lang="en"> 35<a name="id2543656"></a><h2>DESCRIPTION</h2> 36<p><span><strong class="command">dnssec-signzone</strong></span> 37 signs a zone. It generates 38 NSEC and RRSIG records and produces a signed version of the 39 zone. The security status of delegations from the signed zone 40 (that is, whether the child zones are secure or not) is 41 determined by the presence or absence of a 42 <code class="filename">keyset</code> file for each child zone. 43 </p> 44</div> 45<div class="refsect1" lang="en"> 46<a name="id2543671"></a><h2>OPTIONS</h2> 47<div class="variablelist"><dl> 48<dt><span class="term">-a</span></dt> 49<dd><p> 50 Verify all generated signatures. 51 </p></dd> 52<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt> 53<dd><p> 54 Specifies the DNS class of the zone. 55 </p></dd> 56<dt><span class="term">-C</span></dt> 57<dd><p> 58 Compatibility mode: Generate a 59 <code class="filename">keyset-<em class="replaceable"><code>zonename</code></em></code> 60 file in addition to 61 <code class="filename">dsset-<em class="replaceable"><code>zonename</code></em></code> 62 when signing a zone, for use by older versions of 63 <span><strong class="command">dnssec-signzone</strong></span>. 64 </p></dd> 65<dt><span class="term">-d <em class="replaceable"><code>directory</code></em></span></dt> 66<dd><p> 67 Look for <code class="filename">dsset-</code> or 68 <code class="filename">keyset-</code> files in <code class="option">directory</code>. 69 </p></dd> 70<dt><span class="term">-D</span></dt> 71<dd><p> 72 Output only those record types automatically managed by 73 <span><strong class="command">dnssec-signzone</strong></span>, i.e. RRSIG, NSEC, 74 NSEC3 and NSEC3PARAM records. If smart signing 75 (<code class="option">-S</code>) is used, DNSKEY records are also 76 included. The resulting file can be included in the original 77 zone file with <span><strong class="command">$INCLUDE</strong></span>. This option 78 cannot be combined with <code class="option">-O raw</code>, 79 <code class="option">-O map</code>, or serial number updating. 80 </p></dd> 81<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt> 82<dd> 83<p> 84 When applicable, specifies the hardware to use for 85 cryptographic operations, such as a secure key store used 86 for signing. 87 </p> 88<p> 89 When BIND is built with OpenSSL PKCS#11 support, this defaults 90 to the string "pkcs11", which identifies an OpenSSL engine 91 that can drive a cryptographic accelerator or hardware service 92 module. When BIND is built with native PKCS#11 cryptography 93 (--enable-native-pkcs11), it defaults to the path of the PKCS#11 94 provider library specified via "--with-pkcs11". 95 </p> 96</dd> 97<dt><span class="term">-g</span></dt> 98<dd><p> 99 Generate DS records for child zones from 100 <code class="filename">dsset-</code> or <code class="filename">keyset-</code> 101 file. Existing DS records will be removed. 102 </p></dd> 103<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt> 104<dd><p> 105 Key repository: Specify a directory to search for DNSSEC keys. 106 If not specified, defaults to the current directory. 107 </p></dd> 108<dt><span class="term">-k <em class="replaceable"><code>key</code></em></span></dt> 109<dd><p> 110 Treat specified key as a key signing key ignoring any 111 key flags. This option may be specified multiple times. 112 </p></dd> 113<dt><span class="term">-l <em class="replaceable"><code>domain</code></em></span></dt> 114<dd><p> 115 Generate a DLV set in addition to the key (DNSKEY) and DS sets. 116 The domain is appended to the name of the records. 117 </p></dd> 118<dt><span class="term">-M <em class="replaceable"><code>maxttl</code></em></span></dt> 119<dd><p> 120 Sets the maximum TTL for the signed zone. 121 Any TTL higher than <em class="replaceable"><code>maxttl</code></em> in the 122 input zone will be reduced to <em class="replaceable"><code>maxttl</code></em> 123 in the output. This provides certainty as to the largest 124 possible TTL in the signed zone, which is useful to know when 125 rolling keys because it is the longest possible time before 126 signatures that have been retrieved by resolvers will expire 127 from resolver caches. Zones that are signed with this 128 option should be configured to use a matching 129 <code class="option">max-zone-ttl</code> in <code class="filename">named.conf</code>. 130 (Note: This option is incompatible with <code class="option">-D</code>, 131 because it modifies non-DNSSEC data in the output zone.) 132 </p></dd> 133<dt><span class="term">-s <em class="replaceable"><code>start-time</code></em></span></dt> 134<dd><p> 135 Specify the date and time when the generated RRSIG records 136 become valid. This can be either an absolute or relative 137 time. An absolute start time is indicated by a number 138 in YYYYMMDDHHMMSS notation; 20000530144500 denotes 139 14:45:00 UTC on May 30th, 2000. A relative start time is 140 indicated by +N, which is N seconds from the current time. 141 If no <code class="option">start-time</code> is specified, the current 142 time minus 1 hour (to allow for clock skew) is used. 143 </p></dd> 144<dt><span class="term">-e <em class="replaceable"><code>end-time</code></em></span></dt> 145<dd><p> 146 Specify the date and time when the generated RRSIG records 147 expire. As with <code class="option">start-time</code>, an absolute 148 time is indicated in YYYYMMDDHHMMSS notation. A time relative 149 to the start time is indicated with +N, which is N seconds from 150 the start time. A time relative to the current time is 151 indicated with now+N. If no <code class="option">end-time</code> is 152 specified, 30 days from the start time is used as a default. 153 <code class="option">end-time</code> must be later than 154 <code class="option">start-time</code>. 155 </p></dd> 156<dt><span class="term">-X <em class="replaceable"><code>extended end-time</code></em></span></dt> 157<dd> 158<p> 159 Specify the date and time when the generated RRSIG records 160 for the DNSKEY RRset will expire. This is to be used in cases 161 when the DNSKEY signatures need to persist longer than 162 signatures on other records; e.g., when the private component 163 of the KSK is kept offline and the KSK signature is to be 164 refreshed manually. 165 </p> 166<p> 167 As with <code class="option">start-time</code>, an absolute 168 time is indicated in YYYYMMDDHHMMSS notation. A time relative 169 to the start time is indicated with +N, which is N seconds from 170 the start time. A time relative to the current time is 171 indicated with now+N. If no <code class="option">extended end-time</code> is 172 specified, the value of <code class="option">end-time</code> is used as 173 the default. (<code class="option">end-time</code>, in turn, defaults to 174 30 days from the start time.) <code class="option">extended end-time</code> 175 must be later than <code class="option">start-time</code>. 176 </p> 177</dd> 178<dt><span class="term">-f <em class="replaceable"><code>output-file</code></em></span></dt> 179<dd><p> 180 The name of the output file containing the signed zone. The 181 default is to append <code class="filename">.signed</code> to 182 the input filename. If <code class="option">output-file</code> is 183 set to <code class="literal">"-"</code>, then the signed zone is 184 written to the standard output, with a default output 185 format of "full". 186 </p></dd> 187<dt><span class="term">-h</span></dt> 188<dd><p> 189 Prints a short summary of the options and arguments to 190 <span><strong class="command">dnssec-signzone</strong></span>. 191 </p></dd> 192<dt><span class="term">-V</span></dt> 193<dd><p> 194 Prints version information. 195 </p></dd> 196<dt><span class="term">-i <em class="replaceable"><code>interval</code></em></span></dt> 197<dd> 198<p> 199 When a previously-signed zone is passed as input, records 200 may be resigned. The <code class="option">interval</code> option 201 specifies the cycle interval as an offset from the current 202 time (in seconds). If a RRSIG record expires after the 203 cycle interval, it is retained. Otherwise, it is considered 204 to be expiring soon, and it will be replaced. 205 </p> 206<p> 207 The default cycle interval is one quarter of the difference 208 between the signature end and start times. So if neither 209 <code class="option">end-time</code> or <code class="option">start-time</code> 210 are specified, <span><strong class="command">dnssec-signzone</strong></span> 211 generates 212 signatures that are valid for 30 days, with a cycle 213 interval of 7.5 days. Therefore, if any existing RRSIG records 214 are due to expire in less than 7.5 days, they would be 215 replaced. 216 </p> 217</dd> 218<dt><span class="term">-I <em class="replaceable"><code>input-format</code></em></span></dt> 219<dd><p> 220 The format of the input zone file. 221 Possible formats are <span><strong class="command">"text"</strong></span> (default), 222 <span><strong class="command">"raw"</strong></span>, and <span><strong class="command">"map"</strong></span>. 223 This option is primarily intended to be used for dynamic 224 signed zones so that the dumped zone file in a non-text 225 format containing updates can be signed directly. 226 The use of this option does not make much sense for 227 non-dynamic zones. 228 </p></dd> 229<dt><span class="term">-j <em class="replaceable"><code>jitter</code></em></span></dt> 230<dd> 231<p> 232 When signing a zone with a fixed signature lifetime, all 233 RRSIG records issued at the time of signing expires 234 simultaneously. If the zone is incrementally signed, i.e. 235 a previously-signed zone is passed as input to the signer, 236 all expired signatures have to be regenerated at about the 237 same time. The <code class="option">jitter</code> option specifies a 238 jitter window that will be used to randomize the signature 239 expire time, thus spreading incremental signature 240 regeneration over time. 241 </p> 242<p> 243 Signature lifetime jitter also to some extent benefits 244 validators and servers by spreading out cache expiration, 245 i.e. if large numbers of RRSIGs don't expire at the same time 246 from all caches there will be less congestion than if all 247 validators need to refetch at mostly the same time. 248 </p> 249</dd> 250<dt><span class="term">-L <em class="replaceable"><code>serial</code></em></span></dt> 251<dd><p> 252 When writing a signed zone to "raw" or "map" format, set the 253 "source serial" value in the header to the specified serial 254 number. (This is expected to be used primarily for testing 255 purposes.) 256 </p></dd> 257<dt><span class="term">-n <em class="replaceable"><code>ncpus</code></em></span></dt> 258<dd><p> 259 Specifies the number of threads to use. By default, one 260 thread is started for each detected CPU. 261 </p></dd> 262<dt><span class="term">-N <em class="replaceable"><code>soa-serial-format</code></em></span></dt> 263<dd> 264<p> 265 The SOA serial number format of the signed zone. 266 Possible formats are <span><strong class="command">"keep"</strong></span> (default), 267 <span><strong class="command">"increment"</strong></span> and 268 <span><strong class="command">"unixtime"</strong></span>. 269 </p> 270<div class="variablelist"><dl> 271<dt><span class="term"><span><strong class="command">"keep"</strong></span></span></dt> 272<dd><p>Do not modify the SOA serial number.</p></dd> 273<dt><span class="term"><span><strong class="command">"increment"</strong></span></span></dt> 274<dd><p>Increment the SOA serial number using RFC 1982 275 arithmetics.</p></dd> 276<dt><span class="term"><span><strong class="command">"unixtime"</strong></span></span></dt> 277<dd><p>Set the SOA serial number to the number of seconds 278 since epoch.</p></dd> 279</dl></div> 280</dd> 281<dt><span class="term">-o <em class="replaceable"><code>origin</code></em></span></dt> 282<dd><p> 283 The zone origin. If not specified, the name of the zone file 284 is assumed to be the origin. 285 </p></dd> 286<dt><span class="term">-O <em class="replaceable"><code>output-format</code></em></span></dt> 287<dd><p> 288 The format of the output file containing the signed zone. 289 Possible formats are <span><strong class="command">"text"</strong></span> (default), 290 which is the standard textual representation of the zone; 291 <span><strong class="command">"full"</strong></span>, which is text output in a 292 format suitable for processing by external scripts; 293 and <span><strong class="command">"map"</strong></span>, <span><strong class="command">"raw"</strong></span>, 294 and <span><strong class="command">"raw=N"</strong></span>, which store the zone in 295 binary formats for rapid loading by <span><strong class="command">named</strong></span>. 296 <span><strong class="command">"raw=N"</strong></span> specifies the format version of 297 the raw zone file: if N is 0, the raw file can be read by 298 any version of <span><strong class="command">named</strong></span>; if N is 1, the file 299 can be read by release 9.9.0 or higher; the default is 1. 300 </p></dd> 301<dt><span class="term">-p</span></dt> 302<dd><p> 303 Use pseudo-random data when signing the zone. This is faster, 304 but less secure, than using real random data. This option 305 may be useful when signing large zones or when the entropy 306 source is limited. 307 </p></dd> 308<dt><span class="term">-P</span></dt> 309<dd> 310<p> 311 Disable post sign verification tests. 312 </p> 313<p> 314 The post sign verification test ensures that for each algorithm 315 in use there is at least one non revoked self signed KSK key, 316 that all revoked KSK keys are self signed, and that all records 317 in the zone are signed by the algorithm. 318 This option skips these tests. 319 </p> 320</dd> 321<dt><span class="term">-Q</span></dt> 322<dd> 323<p> 324 Remove signatures from keys that are no longer active. 325 </p> 326<p> 327 Normally, when a previously-signed zone is passed as input 328 to the signer, and a DNSKEY record has been removed and 329 replaced with a new one, signatures from the old key 330 that are still within their validity period are retained. 331 This allows the zone to continue to validate with cached 332 copies of the old DNSKEY RRset. The <code class="option">-Q</code> 333 forces <span><strong class="command">dnssec-signzone</strong></span> to remove 334 signatures from keys that are no longer active. This 335 enables ZSK rollover using the procedure described in 336 RFC 4641, section 4.2.1.1 ("Pre-Publish Key Rollover"). 337 </p> 338</dd> 339<dt><span class="term">-R</span></dt> 340<dd> 341<p> 342 Remove signatures from keys that are no longer published. 343 </p> 344<p> 345 This option is similar to <code class="option">-Q</code>, except it 346 forces <span><strong class="command">dnssec-signzone</strong></span> to signatures from 347 keys that are no longer published. This enables ZSK rollover 348 using the procedure described in RFC 4641, section 4.2.1.2 349 ("Double Signature Zone Signing Key Rollover"). 350 </p> 351</dd> 352<dt><span class="term">-r <em class="replaceable"><code>randomdev</code></em></span></dt> 353<dd><p> 354 Specifies the source of randomness. If the operating 355 system does not provide a <code class="filename">/dev/random</code> 356 or equivalent device, the default source of randomness 357 is keyboard input. <code class="filename">randomdev</code> 358 specifies 359 the name of a character device or file containing random 360 data to be used instead of the default. The special value 361 <code class="filename">keyboard</code> indicates that keyboard 362 input should be used. 363 </p></dd> 364<dt><span class="term">-S</span></dt> 365<dd> 366<p> 367 Smart signing: Instructs <span><strong class="command">dnssec-signzone</strong></span> to 368 search the key repository for keys that match the zone being 369 signed, and to include them in the zone if appropriate. 370 </p> 371<p> 372 When a key is found, its timing metadata is examined to 373 determine how it should be used, according to the following 374 rules. Each successive rule takes priority over the prior 375 ones: 376 </p> 377<div class="variablelist"><dl> 378<dt></dt> 379<dd><p> 380 If no timing metadata has been set for the key, the key is 381 published in the zone and used to sign the zone. 382 </p></dd> 383<dt></dt> 384<dd><p> 385 If the key's publication date is set and is in the past, the 386 key is published in the zone. 387 </p></dd> 388<dt></dt> 389<dd><p> 390 If the key's activation date is set and in the past, the 391 key is published (regardless of publication date) and 392 used to sign the zone. 393 </p></dd> 394<dt></dt> 395<dd><p> 396 If the key's revocation date is set and in the past, and the 397 key is published, then the key is revoked, and the revoked key 398 is used to sign the zone. 399 </p></dd> 400<dt></dt> 401<dd><p> 402 If either of the key's unpublication or deletion dates are set 403 and in the past, the key is NOT published or used to sign the 404 zone, regardless of any other metadata. 405 </p></dd> 406</dl></div> 407</dd> 408<dt><span class="term">-T <em class="replaceable"><code>ttl</code></em></span></dt> 409<dd><p> 410 Specifies a TTL to be used for new DNSKEY records imported 411 into the zone from the key repository. If not 412 specified, the default is the TTL value from the zone's SOA 413 record. This option is ignored when signing without 414 <code class="option">-S</code>, since DNSKEY records are not imported 415 from the key repository in that case. It is also ignored if 416 there are any pre-existing DNSKEY records at the zone apex, 417 in which case new records' TTL values will be set to match 418 them, or if any of the imported DNSKEY records had a default 419 TTL value. In the event of a a conflict between TTL values in 420 imported keys, the shortest one is used. 421 </p></dd> 422<dt><span class="term">-t</span></dt> 423<dd><p> 424 Print statistics at completion. 425 </p></dd> 426<dt><span class="term">-u</span></dt> 427<dd><p> 428 Update NSEC/NSEC3 chain when re-signing a previously signed 429 zone. With this option, a zone signed with NSEC can be 430 switched to NSEC3, or a zone signed with NSEC3 can 431 be switch to NSEC or to NSEC3 with different parameters. 432 Without this option, <span><strong class="command">dnssec-signzone</strong></span> will 433 retain the existing chain when re-signing. 434 </p></dd> 435<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt> 436<dd><p> 437 Sets the debugging level. 438 </p></dd> 439<dt><span class="term">-x</span></dt> 440<dd><p> 441 Only sign the DNSKEY RRset with key-signing keys, and omit 442 signatures from zone-signing keys. (This is similar to the 443 <span><strong class="command">dnssec-dnskey-kskonly yes;</strong></span> zone option in 444 <span><strong class="command">named</strong></span>.) 445 </p></dd> 446<dt><span class="term">-z</span></dt> 447<dd><p> 448 Ignore KSK flag on key when determining what to sign. This 449 causes KSK-flagged keys to sign all records, not just the 450 DNSKEY RRset. (This is similar to the 451 <span><strong class="command">update-check-ksk no;</strong></span> zone option in 452 <span><strong class="command">named</strong></span>.) 453 </p></dd> 454<dt><span class="term">-3 <em class="replaceable"><code>salt</code></em></span></dt> 455<dd><p> 456 Generate an NSEC3 chain with the given hex encoded salt. 457 A dash (<em class="replaceable"><code>salt</code></em>) can 458 be used to indicate that no salt is to be used when generating the NSEC3 chain. 459 </p></dd> 460<dt><span class="term">-H <em class="replaceable"><code>iterations</code></em></span></dt> 461<dd><p> 462 When generating an NSEC3 chain, use this many iterations. The 463 default is 10. 464 </p></dd> 465<dt><span class="term">-A</span></dt> 466<dd> 467<p> 468 When generating an NSEC3 chain set the OPTOUT flag on all 469 NSEC3 records and do not generate NSEC3 records for insecure 470 delegations. 471 </p> 472<p> 473 Using this option twice (i.e., <code class="option">-AA</code>) 474 turns the OPTOUT flag off for all records. This is useful 475 when using the <code class="option">-u</code> option to modify an NSEC3 476 chain which previously had OPTOUT set. 477 </p> 478</dd> 479<dt><span class="term">zonefile</span></dt> 480<dd><p> 481 The file containing the zone to be signed. 482 </p></dd> 483<dt><span class="term">key</span></dt> 484<dd><p> 485 Specify which keys should be used to sign the zone. If 486 no keys are specified, then the zone will be examined 487 for DNSKEY records at the zone apex. If these are found and 488 there are matching private keys, in the current directory, 489 then these will be used for signing. 490 </p></dd> 491</dl></div> 492</div> 493<div class="refsect1" lang="en"> 494<a name="id2545241"></a><h2>EXAMPLE</h2> 495<p> 496 The following command signs the <strong class="userinput"><code>example.com</code></strong> 497 zone with the DSA key generated by <span><strong class="command">dnssec-keygen</strong></span> 498 (Kexample.com.+003+17247). Because the <span><strong class="command">-S</strong></span> option 499 is not being used, the zone's keys must be in the master file 500 (<code class="filename">db.example.com</code>). This invocation looks 501 for <code class="filename">dsset</code> files, in the current directory, 502 so that DS records can be imported from them (<span><strong class="command">-g</strong></span>). 503 </p> 504<pre class="programlisting">% dnssec-signzone -g -o example.com db.example.com \ 505Kexample.com.+003+17247 506db.example.com.signed 507%</pre> 508<p> 509 In the above example, <span><strong class="command">dnssec-signzone</strong></span> creates 510 the file <code class="filename">db.example.com.signed</code>. This 511 file should be referenced in a zone statement in a 512 <code class="filename">named.conf</code> file. 513 </p> 514<p> 515 This example re-signs a previously signed zone with default parameters. 516 The private keys are assumed to be in the current directory. 517 </p> 518<pre class="programlisting">% cp db.example.com.signed db.example.com 519% dnssec-signzone -o example.com db.example.com 520db.example.com.signed 521%</pre> 522</div> 523<div class="refsect1" lang="en"> 524<a name="id2545365"></a><h2>SEE ALSO</h2> 525<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>, 526 <em class="citetitle">BIND 9 Administrator Reference Manual</em>, 527 <em class="citetitle">RFC 4033</em>, <em class="citetitle">RFC 4641</em>. 528 </p> 529</div> 530<div class="refsect1" lang="en"> 531<a name="id2545393"></a><h2>AUTHOR</h2> 532<p><span class="corpauthor">Internet Systems Consortium</span> 533 </p> 534</div> 535</div></body> 536</html> 537