dnssec-signzone.docbook 29.1 KB
Newer Older
1 2
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
               "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
3
	       [<!ENTITY mdash "&#8212;">]>
Brian Wellington's avatar
Brian Wellington committed
4
<!--
Tinderbox User's avatar
Tinderbox User committed
5
 - Copyright (C) 2004-2009, 2011-2013  Internet Systems Consortium, Inc. ("ISC")
6
 - Copyright (C) 2000-2003  Internet Software Consortium.
Brian Wellington's avatar
Brian Wellington committed
7
 -
Automatic Updater's avatar
Automatic Updater committed
8
 - Permission to use, copy, modify, and/or distribute this software for any
Brian Wellington's avatar
Brian Wellington committed
9 10 11
 - purpose with or without fee is hereby granted, provided that the above
 - copyright notice and this permission notice appear in all copies.
 -
Mark Andrews's avatar
Mark Andrews committed
12 13 14 15 16 17 18
 - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
 - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
 - AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
 - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
 - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
 - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
 - PERFORMANCE OF THIS SOFTWARE.
Brian Wellington's avatar
Brian Wellington committed
19
-->
Mark Andrews's avatar
Mark Andrews committed
20

21
<!-- $Id: dnssec-signzone.docbook,v 1.52 2011/12/22 07:32:40 each Exp $ -->
22
<refentry id="man.dnssec-signzone">
23
  <refentryinfo>
24
    <date>June 05, 2009</date>
25 26 27 28
  </refentryinfo>

  <refmeta>
    <refentrytitle><application>dnssec-signzone</application></refentrytitle>
29
   <manvolnum>8</manvolnum>
30 31 32 33 34 35 36 37
    <refmiscinfo>BIND9</refmiscinfo>
  </refmeta>

  <refnamediv>
    <refname><application>dnssec-signzone</application></refname>
    <refpurpose>DNSSEC zone signing tool</refpurpose>
  </refnamediv>

38 39 40 41
  <docinfo>
    <copyright>
      <year>2004</year>
      <year>2005</year>
Mark Andrews's avatar
Mark Andrews committed
42
      <year>2006</year>
Mark Andrews's avatar
Mark Andrews committed
43
      <year>2007</year>
Automatic Updater's avatar
Automatic Updater committed
44
      <year>2008</year>
Automatic Updater's avatar
Automatic Updater committed
45
      <year>2009</year>
Automatic Updater's avatar
Automatic Updater committed
46
      <year>2011</year>
Tinderbox User's avatar
Tinderbox User committed
47
      <year>2012</year>
Tinderbox User's avatar
Tinderbox User committed
48
      <year>2013</year>
49 50 51 52 53 54 55
      <holder>Internet Systems Consortium, Inc. ("ISC")</holder>
    </copyright>
    <copyright>
      <year>2000</year>
      <year>2001</year>
      <year>2002</year>
      <year>2003</year>
Mark Andrews's avatar
Mark Andrews committed
56
      <holder>Internet Software Consortium.</holder>
57 58 59
    </copyright>
  </docinfo>

60 61 62 63 64 65
  <refsynopsisdiv>
    <cmdsynopsis>
      <command>dnssec-signzone</command>
      <arg><option>-a</option></arg>
      <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
      <arg><option>-d <replaceable class="parameter">directory</replaceable></option></arg>
66
      <arg><option>-D</option></arg>
Francis Dupont's avatar
Francis Dupont committed
67
      <arg><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
68 69
      <arg><option>-e <replaceable class="parameter">end-time</replaceable></option></arg>
      <arg><option>-f <replaceable class="parameter">output-file</replaceable></option></arg>
70
      <arg><option>-g</option></arg>
71
      <arg><option>-h</option></arg>
72
      <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
73
      <arg><option>-k <replaceable class="parameter">key</replaceable></option></arg>
74
      <arg><option>-L <replaceable class="parameter">serial</replaceable></option></arg>
75
      <arg><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
76
      <arg><option>-i <replaceable class="parameter">interval</replaceable></option></arg>
77
      <arg><option>-I <replaceable class="parameter">input-format</replaceable></option></arg>
78
      <arg><option>-j <replaceable class="parameter">jitter</replaceable></option></arg>
79
      <arg><option>-N <replaceable class="parameter">soa-serial-format</replaceable></option></arg>
80
      <arg><option>-o <replaceable class="parameter">origin</replaceable></option></arg>
81
      <arg><option>-O <replaceable class="parameter">output-format</replaceable></option></arg>
82
      <arg><option>-P</option></arg>
83 84
      <arg><option>-p</option></arg>
      <arg><option>-R</option></arg>
85
      <arg><option>-r <replaceable class="parameter">randomdev</replaceable></option></arg>
86
      <arg><option>-S</option></arg>
87
      <arg><option>-s <replaceable class="parameter">start-time</replaceable></option></arg>
88
      <arg><option>-T <replaceable class="parameter">ttl</replaceable></option></arg>
89
      <arg><option>-t</option></arg>
90
      <arg><option>-u</option></arg>
91
      <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
92
      <arg><option>-X <replaceable class="parameter">extended end-time</replaceable></option></arg>
93
      <arg><option>-x</option></arg>
94
      <arg><option>-z</option></arg>
95 96 97
      <arg><option>-3 <replaceable class="parameter">salt</replaceable></option></arg>
      <arg><option>-H <replaceable class="parameter">iterations</replaceable></option></arg>
      <arg><option>-A</option></arg>
98 99 100 101 102 103 104
      <arg choice="req">zonefile</arg>
      <arg rep="repeat">key</arg>
    </cmdsynopsis>
  </refsynopsisdiv>

  <refsect1>
    <title>DESCRIPTION</title>
105 106 107 108 109 110 111
    <para><command>dnssec-signzone</command>
      signs a zone.  It generates
      NSEC and RRSIG records and produces a signed version of the
      zone. The security status of delegations from the signed zone
      (that is, whether the child zones are secure or not) is
      determined by the presence or absence of a
      <filename>keyset</filename> file for each child zone.
112 113 114 115 116 117 118 119 120
    </para>
  </refsect1>

  <refsect1>
    <title>OPTIONS</title>

    <variablelist>
      <varlistentry>
        <term>-a</term>
121 122 123 124 125
        <listitem>
          <para>
            Verify all generated signatures.
          </para>
        </listitem>
126 127 128 129
      </varlistentry>

      <varlistentry>
        <term>-c <replaceable class="parameter">class</replaceable></term>
130 131 132 133 134
        <listitem>
          <para>
            Specifies the DNS class of the zone.
          </para>
        </listitem>
135 136
      </varlistentry>

137 138 139 140 141 142 143 144 145 146 147 148 149 150
      <varlistentry>
        <term>-C</term>
        <listitem>
          <para>
            Compatibility mode: Generate a
            <filename>keyset-<replaceable>zonename</replaceable></filename>
            file in addition to
            <filename>dsset-<replaceable>zonename</replaceable></filename>
            when signing a zone, for use by older versions of
            <command>dnssec-signzone</command>.
          </para>
        </listitem>
      </varlistentry>

151
      <varlistentry>
152
        <term>-d <replaceable class="parameter">directory</replaceable></term>
153 154
        <listitem>
          <para>
155 156
            Look for <filename>dsset-</filename> or
            <filename>keyset-</filename> files in <option>directory</option>.
157 158
          </para>
        </listitem>
159 160
      </varlistentry>

161 162 163 164 165 166 167 168 169 170
      <varlistentry>
        <term>-D</term>
        <listitem>
          <para>
	    Output only those record types automatically managed by
	    <command>dnssec-signzone</command>, i.e. RRSIG, NSEC,
	    NSEC3 and NSEC3PARAM records. If smart signing
	    (<option>-S</option>) is used, DNSKEY records are also
	    included. The resulting file can be included in the original
	    zone file with <command>$INCLUDE</command>. This option
171
	    cannot be combined with <option>-O raw</option>, 
Evan Hunt's avatar
Evan Hunt committed
172
            <option>-O map</option>, or serial number updating.
173 174 175 176
          </para>
        </listitem>
      </varlistentry>

Francis Dupont's avatar
Francis Dupont committed
177 178 179 180 181 182 183
      <varlistentry>
        <term>-E <replaceable class="parameter">engine</replaceable></term>
        <listitem>
          <para>
            Uses a crypto hardware (OpenSSL engine) for the crypto operations
            it supports, for instance signing with private keys from
            a secure key store. When compiled with PKCS#11 support
Evan Hunt's avatar
Evan Hunt committed
184
            it defaults to pkcs11; the empty name resets it to no engine.
Francis Dupont's avatar
Francis Dupont committed
185 186 187 188
          </para>
        </listitem>
      </varlistentry>

189
      <varlistentry>
190
        <term>-g</term>
191 192
        <listitem>
          <para>
193 194 195
            Generate DS records for child zones from
            <filename>dsset-</filename> or <filename>keyset-</filename>
            file.  Existing DS records will be removed.
196 197
          </para>
        </listitem>
198 199
      </varlistentry>

200
      <varlistentry>
201
        <term>-K <replaceable class="parameter">directory</replaceable></term>
202 203
        <listitem>
          <para>
204 205
            Key repository: Specify a directory to search for DNSSEC keys.
            If not specified, defaults to the current directory.
206 207
          </para>
        </listitem>
208 209
      </varlistentry>

210
      <varlistentry>
211
        <term>-k <replaceable class="parameter">key</replaceable></term>
212 213
        <listitem>
          <para>
214 215 216 217 218 219 220 221 222 223 224 225
            Treat specified key as a key signing key ignoring any
            key flags.  This option may be specified multiple times.
          </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term>-l <replaceable class="parameter">domain</replaceable></term>
        <listitem>
          <para>
            Generate a DLV set in addition to the key (DNSKEY) and DS sets.
            The domain is appended to the name of the records.
226 227
          </para>
        </listitem>
228 229
      </varlistentry>

230 231
      <varlistentry>
        <term>-s <replaceable class="parameter">start-time</replaceable></term>
232 233 234 235 236 237 238 239 240 241 242 243
        <listitem>
          <para>
            Specify the date and time when the generated RRSIG records
            become valid.  This can be either an absolute or relative
            time.  An absolute start time is indicated by a number
            in YYYYMMDDHHMMSS notation; 20000530144500 denotes
            14:45:00 UTC on May 30th, 2000.  A relative start time is
            indicated by +N, which is N seconds from the current time.
            If no <option>start-time</option> is specified, the current
            time minus 1 hour (to allow for clock skew) is used.
          </para>
        </listitem>
244 245 246 247
      </varlistentry>

      <varlistentry>
        <term>-e <replaceable class="parameter">end-time</replaceable></term>
248 249 250 251 252 253 254 255 256
        <listitem>
          <para>
            Specify the date and time when the generated RRSIG records
            expire.  As with <option>start-time</option>, an absolute
            time is indicated in YYYYMMDDHHMMSS notation.  A time relative
            to the start time is indicated with +N, which is N seconds from
            the start time.  A time relative to the current time is
            indicated with now+N.  If no <option>end-time</option> is
            specified, 30 days from the start time is used as a default.
257 258
            <option>end-time</option> must be later than
            <option>start-time</option>.
259 260
          </para>
        </listitem>
261 262
      </varlistentry>

263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287
      <varlistentry>
        <term>-X <replaceable class="parameter">extended end-time</replaceable></term>
        <listitem>
          <para>
            Specify the date and time when the generated RRSIG records
            for the DNSKEY RRset will expire.  This is to be used in cases
            when the DNSKEY signatures need to persist longer than
            signatures on other records; e.g., when the private component
            of the KSK is kept offline and the KSK signature is to be
            refreshed manually.
          </para>
          <para>
            As with <option>start-time</option>, an absolute
            time is indicated in YYYYMMDDHHMMSS notation.  A time relative
            to the start time is indicated with +N, which is N seconds from
            the start time.  A time relative to the current time is
            indicated with now+N.  If no <option>extended end-time</option> is
            specified, the value of <option>end-time</option> is used as
            the default.  (<option>end-time</option>, in turn, defaults to
            30 days from the start time.) <option>extended end-time</option>
            must be later than <option>start-time</option>.
          </para>
        </listitem>
      </varlistentry>

288 289
      <varlistentry>
        <term>-f <replaceable class="parameter">output-file</replaceable></term>
290 291 292 293
        <listitem>
          <para>
            The name of the output file containing the signed zone.  The
            default is to append <filename>.signed</filename> to
294 295 296 297
            the input filename.  If <option>output-file</option> is
            set to <literal>"-"</literal>, then the signed zone is
            written to the standard output, with a default output
            format of "full".
298 299
          </para>
        </listitem>
300 301 302 303
      </varlistentry>

      <varlistentry>
        <term>-h</term>
304 305 306 307 308 309
        <listitem>
          <para>
            Prints a short summary of the options and arguments to
            <command>dnssec-signzone</command>.
          </para>
        </listitem>
310 311 312 313
      </varlistentry>

      <varlistentry>
        <term>-i <replaceable class="parameter">interval</replaceable></term>
314 315
        <listitem>
          <para>
316
            When a previously-signed zone is passed as input, records
317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334
            may be resigned.  The <option>interval</option> option
            specifies the cycle interval as an offset from the current
            time (in seconds).  If a RRSIG record expires after the
            cycle interval, it is retained.  Otherwise, it is considered
            to be expiring soon, and it will be replaced.
          </para>
          <para>
            The default cycle interval is one quarter of the difference
            between the signature end and start times.  So if neither
            <option>end-time</option> or <option>start-time</option>
            are specified, <command>dnssec-signzone</command>
            generates
            signatures that are valid for 30 days, with a cycle
            interval of 7.5 days.  Therefore, if any existing RRSIG records
            are due to expire in less than 7.5 days, they would be
            replaced.
          </para>
        </listitem>
335 336
      </varlistentry>

337 338 339 340 341
      <varlistentry>
        <term>-I <replaceable class="parameter">input-format</replaceable></term>
        <listitem>
          <para>
            The format of the input zone file.
342
	    Possible formats are <command>"text"</command> (default),
Evan Hunt's avatar
Evan Hunt committed
343
	    <command>"raw"</command>, and <command>"map"</command>.
344 345 346 347 348 349 350 351 352
	    This option is primarily intended to be used for dynamic
            signed zones so that the dumped zone file in a non-text
            format containing updates can be signed directly.
	    The use of this option does not make much sense for
	    non-dynamic zones.
          </para>
        </listitem>
      </varlistentry>

353
      <varlistentry>
354 355 356 357 358 359
        <term>-j <replaceable class="parameter">jitter</replaceable></term>
        <listitem>
          <para>
            When signing a zone with a fixed signature lifetime, all
            RRSIG records issued at the time of signing expires
            simultaneously.  If the zone is incrementally signed, i.e.
360 361
            a previously-signed zone is passed as input to the signer,
            all expired signatures have to be regenerated at about the
362 363 364 365 366 367 368 369 370 371 372 373 374
            same time.  The <option>jitter</option> option specifies a
            jitter window that will be used to randomize the signature
            expire time, thus spreading incremental signature
            regeneration over time.
          </para>
          <para>
            Signature lifetime jitter also to some extent benefits
            validators and servers by spreading out cache expiration,
            i.e. if large numbers of RRSIGs don't expire at the same time
            from all caches there will be less congestion than if all
            validators need to refetch at mostly the same time.
          </para>
        </listitem>
375 376
      </varlistentry>

377 378 379 380
      <varlistentry>
        <term>-L <replaceable class="parameter">serial</replaceable></term>
        <listitem>
          <para>
Evan Hunt's avatar
Evan Hunt committed
381
            When writing a signed zone to "raw" or "map" format, set the
382 383 384
            "source serial" value in the header to the specified serial
            number.  (This is expected to be used primarily for testing
            purposes.)
385 386 387 388
          </para>
        </listitem>
      </varlistentry>

389 390
      <varlistentry>
        <term>-n <replaceable class="parameter">ncpus</replaceable></term>
391 392 393 394 395 396
        <listitem>
          <para>
            Specifies the number of threads to use.  By default, one
            thread is started for each detected CPU.
          </para>
        </listitem>
397 398
      </varlistentry>

399 400 401 402 403 404
      <varlistentry>
        <term>-N <replaceable class="parameter">soa-serial-format</replaceable></term>
        <listitem>
          <para>
            The SOA serial number format of the signed zone.
	    Possible formats are <command>"keep"</command> (default),
Mark Andrews's avatar
Mark Andrews committed
405
            <command>"increment"</command> and
406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436
	    <command>"unixtime"</command>.
          </para>

          <variablelist>
	    <varlistentry>
	      <term><command>"keep"</command></term>
              <listitem>
                <para>Do not modify the SOA serial number.</para>
	      </listitem>
            </varlistentry>

	    <varlistentry>
	      <term><command>"increment"</command></term>
              <listitem>
                <para>Increment the SOA serial number using RFC 1982
                      arithmetics.</para>
	      </listitem>
            </varlistentry>

	    <varlistentry>
	      <term><command>"unixtime"</command></term>
              <listitem>
                <para>Set the SOA serial number to the number of seconds
	        since epoch.</para>
	      </listitem>
            </varlistentry>
	 </variablelist>

        </listitem>
      </varlistentry>

437 438
      <varlistentry>
        <term>-o <replaceable class="parameter">origin</replaceable></term>
439 440 441 442 443 444
        <listitem>
          <para>
            The zone origin.  If not specified, the name of the zone file
            is assumed to be the origin.
          </para>
        </listitem>
445 446
      </varlistentry>

447 448 449 450 451
      <varlistentry>
        <term>-O <replaceable class="parameter">output-format</replaceable></term>
        <listitem>
          <para>
            The format of the output file containing the signed zone.
452 453
	    Possible formats are <command>"text"</command> (default),
            which is the standard textual representation of the zone;
454
	    <command>"full"</command>, which is text output in a
455
            format suitable for processing by external scripts;
Evan Hunt's avatar
Evan Hunt committed
456
            and <command>"map"</command>, <command>"raw"</command>,
457 458 459 460 461 462
            and <command>"raw=N"</command>, which store the zone in
            binary formats for rapid loading by <command>named</command>.
            <command>"raw=N"</command> specifies the format version of
            the raw zone file: if N is 0, the raw file can be read by
            any version of <command>named</command>; if N is 1, the file
            can be read by release 9.9.0 or higher; the default is 1.
463 464 465 466
          </para>
        </listitem>
      </varlistentry>

467 468
      <varlistentry>
        <term>-p</term>
469 470 471 472 473 474 475 476
        <listitem>
          <para>
            Use pseudo-random data when signing the zone.  This is faster,
            but less secure, than using real random data.  This option
            may be useful when signing large zones or when the entropy
            source is limited.
          </para>
        </listitem>
477 478
      </varlistentry>

479 480 481 482 483 484 485 486
      <varlistentry>
        <term>-P</term>
        <listitem>
          <para>
	    Disable post sign verification tests.
          </para>
          <para>
	    The post sign verification test ensures that for each algorithm
487 488
	    in use there is at least one non revoked self signed KSK key,
	    that all revoked KSK keys are self signed, and that all records
489
	    in the zone are signed by the algorithm.
490
	    This option skips these tests.
491 492 493 494
          </para>
        </listitem>
      </varlistentry>

495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512
      <varlistentry>
        <term>-R</term>
        <listitem>
          <para>
	    Remove signatures from keys that no longer exist.
          </para>
          <para>
            Normally, when a previously-signed zone is passed as input
            to the signer, and a DNSKEY record has been removed and
            replaced with a new one, signatures from the old key 
            that are still within their validity period are retained.
	    This allows the zone to continue to validate with cached
	    copies of the old DNSKEY RRset.  The <option>-R</option> forces
            <command>dnssec-signzone</command> to remove all orphaned
            signatures.
          </para>
        </listitem>
      </varlistentry>
513 514
      <varlistentry>
        <term>-r <replaceable class="parameter">randomdev</replaceable></term>
515 516 517 518 519 520 521 522 523 524 525 526 527
        <listitem>
          <para>
            Specifies the source of randomness.  If the operating
            system does not provide a <filename>/dev/random</filename>
            or equivalent device, the default source of randomness
            is keyboard input.  <filename>randomdev</filename>
            specifies
            the name of a character device or file containing random
            data to be used instead of the default.  The special value
            <filename>keyboard</filename> indicates that keyboard
            input should be used.
          </para>
        </listitem>
528 529
      </varlistentry>

530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599
      <varlistentry>
        <term>-S</term>
        <listitem>
          <para>
            Smart signing: Instructs <command>dnssec-signzone</command> to
            search the key repository for keys that match the zone being
            signed, and to include them in the zone if appropriate.
          </para>
          <para>
            When a key is found, its timing metadata is examined to
            determine how it should be used, according to the following
            rules.  Each successive rule takes priority over the prior
            ones:
          </para>
          <variablelist>
	    <varlistentry>
              <listitem>
                <para>
                  If no timing metadata has been set for the key, the key is
                  published in the zone and used to sign the zone.
                </para>
	      </listitem>
            </varlistentry>

	    <varlistentry>
              <listitem>
                <para>
                  If the key's publication date is set and is in the past, the
                  key is published in the zone.
                </para>
	      </listitem>
            </varlistentry>

	    <varlistentry>
              <listitem>
                <para>
                  If the key's activation date is set and in the past, the
                  key is published (regardless of publication date) and
                  used to sign the zone.  
                </para>
	      </listitem>
            </varlistentry>

	    <varlistentry>
              <listitem>
                <para>
                  If the key's revocation date is set and in the past, and the
                  key is published, then the key is revoked, and the revoked key
                  is used to sign the zone.
                </para>
	      </listitem>
            </varlistentry>

	    <varlistentry>
              <listitem>
                <para>
                  If either of the key's unpublication or deletion dates are set
                  and in the past, the key is NOT published or used to sign the
                  zone, regardless of any other metadata.
                </para>
	      </listitem>
            </varlistentry>
	 </variablelist>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term>-T <replaceable class="parameter">ttl</replaceable></term>
        <listitem>
          <para>
600 601 602
            Specifies a TTL to be used for new DNSKEY records imported
            into the zone from the key repository.  If not
            specified, the default is the TTL value from the zone's SOA
603 604 605 606 607
            record.  This option is ignored when signing without
            <option>-S</option>, since DNSKEY records are not imported
            from the key repository in that case.  It is also ignored if
            there are any pre-existing DNSKEY records at the zone apex,
            in which case new records' TTL values will be set to match
608 609 610
            them, or if any of the imported DNSKEY records had a default
            TTL value.  In the event of a a conflict between TTL values in
            imported keys, the shortest one is used.
611 612 613 614
          </para>
        </listitem>
      </varlistentry>

615 616
      <varlistentry>
        <term>-t</term>
617 618 619 620 621
        <listitem>
          <para>
            Print statistics at completion.
          </para>
        </listitem>
622 623
      </varlistentry>

624 625 626 627 628 629 630 631 632 633 634 635 636 637
      <varlistentry>
        <term>-u</term>
        <listitem>
          <para>
            Update NSEC/NSEC3 chain when re-signing a previously signed
            zone.  With this option, a zone signed with NSEC can be
            switched to NSEC3, or a zone signed with NSEC3 can
            be switch to NSEC or to NSEC3 with different parameters.
            Without this option, <command>dnssec-signzone</command> will
            retain the existing chain when re-signing.
          </para>
        </listitem>
      </varlistentry>

638 639
      <varlistentry>
        <term>-v <replaceable class="parameter">level</replaceable></term>
640 641 642 643 644
        <listitem>
          <para>
            Sets the debugging level.
          </para>
        </listitem>
645 646
      </varlistentry>

647 648 649 650 651
      <varlistentry>
        <term>-x</term>
        <listitem>
          <para>
            Only sign the DNSKEY RRset with key-signing keys, and omit
Evan Hunt's avatar
Evan Hunt committed
652
            signatures from zone-signing keys.  (This is similar to the
653
            <command>dnssec-dnskey-kskonly yes;</command> zone option in
Evan Hunt's avatar
Evan Hunt committed
654
            <command>named</command>.)
655 656 657 658
          </para>
        </listitem>
      </varlistentry>

659 660
      <varlistentry>
        <term>-z</term>
661 662
        <listitem>
          <para>
663 664
            Ignore KSK flag on key when determining what to sign.  This
            causes KSK-flagged keys to sign all records, not just the
Evan Hunt's avatar
Evan Hunt committed
665 666 667
            DNSKEY RRset.  (This is similar to the
            <command>update-check-ksk no;</command> zone option in
            <command>named</command>.)
668 669
          </para>
        </listitem>
670 671
      </varlistentry>

672 673 674 675
      <varlistentry>
        <term>-3 <replaceable class="parameter">salt</replaceable></term>
        <listitem>
          <para>
676
            Generate an NSEC3 chain with the given hex encoded salt.
677 678 679 680 681 682 683 684 685 686
	    A dash (<replaceable class="parameter">salt</replaceable>) can
	    be used to indicate that no salt is to be used when generating		    the NSEC3 chain.
          </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term>-H <replaceable class="parameter">iterations</replaceable></term>
        <listitem>
          <para>
Mark Andrews's avatar
typos  
Mark Andrews committed
687
	    When generating an NSEC3 chain, use this many iterations.  The
688
	    default is 10.
689 690 691 692 693 694 695 696
          </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term>-A</term>
        <listitem>
          <para>
697
	    When generating an NSEC3 chain set the OPTOUT flag on all
698 699 700
	    NSEC3 records and do not generate NSEC3 records for insecure
	    delegations.
          </para>
701 702 703 704 705 706
          <para>
	    Using this option twice (i.e., <option>-AA</option>)
	    turns the OPTOUT flag off for all records.  This is useful
	    when using the <option>-u</option> option to modify an NSEC3
	    chain which previously had OPTOUT set.
          </para>
707 708 709
        </listitem>
      </varlistentry>

710 711
      <varlistentry>
        <term>zonefile</term>
712 713 714 715 716
        <listitem>
          <para>
            The file containing the zone to be signed.
          </para>
        </listitem>
717 718 719 720
      </varlistentry>

      <varlistentry>
        <term>key</term>
721 722
        <listitem>
          <para>
723 724 725 726 727
	    Specify which keys should be used to sign the zone.  If
	    no keys are specified, then the zone will be examined
	    for DNSKEY records at the zone apex.  If these are found and
	    there are matching private keys, in the current directory,
	    then these will be used for signing.
728 729
          </para>
        </listitem>
730 731 732 733 734 735 736 737
      </varlistentry>

    </variablelist>
  </refsect1>

  <refsect1>
    <title>EXAMPLE</title>
    <para>
738
      The following command signs the <userinput>example.com</userinput>
739
      zone with the DSA key generated by <command>dnssec-keygen</command>
740 741 742 743 744
      (Kexample.com.+003+17247).  Because the <command>-S</command> option
      is not being used, the zone's keys must be in the master file
      (<filename>db.example.com</filename>).  This invocation looks
      for <filename>dsset</filename> files, in the current directory,
      so that DS records can be imported from them (<command>-g</command>).
745
    </para>
746 747 748 749
<programlisting>% dnssec-signzone -g -o example.com db.example.com \
Kexample.com.+003+17247
db.example.com.signed
%</programlisting>
750
    <para>
751
      In the above example, <command>dnssec-signzone</command> creates
752
      the file <filename>db.example.com.signed</filename>.  This
753
      file should be referenced in a zone statement in a
754
      <filename>named.conf</filename> file.
755
    </para>
756 757 758 759 760 761 762 763
    <para>
      This example re-signs a previously signed zone with default parameters.
      The private keys are assumed to be in the current directory.
    </para>
<programlisting>% cp db.example.com.signed db.example.com
% dnssec-signzone -o example.com db.example.com
db.example.com.signed
%</programlisting>
764 765 766 767
  </refsect1>

  <refsect1>
    <title>SEE ALSO</title>
768 769
    <para><citerefentry>
        <refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
770 771
      </citerefentry>,
      <citetitle>BIND 9 Administrator Reference Manual</citetitle>,
772
      <citetitle>RFC 4033</citetitle>.
773 774 775 776 777
    </para>
  </refsect1>

  <refsect1>
    <title>AUTHOR</title>
778
    <para><corpauthor>Internet Systems Consortium</corpauthor>
779 780 781
    </para>
  </refsect1>

782
</refentry><!--
783 784 785 786
 - Local variables:
 - mode: sgml
 - End:
-->