external/bsd/bind/dist/doc/arm/man.dnssec-signzone.html

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