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