Gecko [ nbspublicschool.com ]

Name	Size	Permission
sample	[ DIR ]	drwxr-xr-x
Bv9ARM.ch01.html	26.11 KB	-rw-r--r--
Bv9ARM.ch02.html	7.18 KB	-rw-r--r--
Bv9ARM.ch03.html	30.38 KB	-rw-r--r--
Bv9ARM.ch04.html	129.65 KB	-rw-r--r--
Bv9ARM.ch05.html	6.29 KB	-rw-r--r--
Bv9ARM.ch06.html	684.15 KB	-rw-r--r--
Bv9ARM.ch07.html	19.56 KB	-rw-r--r--
Bv9ARM.ch08.html	6.32 KB	-rw-r--r--
Bv9ARM.ch09.html	10.27 KB	-rw-r--r--
Bv9ARM.ch10.html	6.92 KB	-rw-r--r--
Bv9ARM.ch11.html	53.24 KB	-rw-r--r--
Bv9ARM.ch12.html	20.45 KB	-rw-r--r--
Bv9ARM.ch13.html	9.88 KB	-rw-r--r--
Bv9ARM.html	29.71 KB	-rw-r--r--
Bv9ARM.pdf	1.24 MB	-rw-r--r--
CHANGES	528.76 KB	-rw-r--r--
README	22.46 KB	-rw-r--r--
isc-logo.pdf	281.24 KB	-rw-r--r--
man.arpaname.html	3.01 KB	-rw-r--r--
man.ddns-confgen.html	9.49 KB	-rw-r--r--
man.delv.html	23.87 KB	-rw-r--r--
man.dig.html	40.63 KB	-rw-r--r--
man.dnssec-checkds.html	5.35 KB	-rw-r--r--
man.dnssec-coverage.html	11.35 KB	-rw-r--r--
man.dnssec-dsfromkey.html	9.68 KB	-rw-r--r--
man.dnssec-importkey.html	9.58 KB	-rw-r--r--
man.dnssec-keyfromlabel.html	19.12 KB	-rw-r--r--
man.dnssec-keygen.html	22.31 KB	-rw-r--r--
man.dnssec-keymgr.html	15.15 KB	-rw-r--r--
man.dnssec-revoke.html	5.62 KB	-rw-r--r--
man.dnssec-settime.html	14.55 KB	-rw-r--r--
man.dnssec-signzone.html	30.69 KB	-rw-r--r--
man.dnssec-verify.html	7.43 KB	-rw-r--r--
man.dnstap-read.html	4.39 KB	-rw-r--r--
man.genrandom.html	4.13 KB	-rw-r--r--
man.host.html	12.74 KB	-rw-r--r--
man.isc-hmac-fixup.html	4.6 KB	-rw-r--r--
man.lwresd.html	12.45 KB	-rw-r--r--
man.mdig.html	23.18 KB	-rw-r--r--
man.named-checkconf.html	6.77 KB	-rw-r--r--
man.named-checkzone.html	20.21 KB	-rw-r--r--
man.named-journalprint.html	4.2 KB	-rw-r--r--
man.named-nzd2nzf.html	3.86 KB	-rw-r--r--
man.named-rrchecker.html	4.21 KB	-rw-r--r--
man.named.conf.html	73.42 KB	-rw-r--r--
man.named.html	19.07 KB	-rw-r--r--
man.nsec3hash.html	4.17 KB	-rw-r--r--
man.nslookup.html	14.49 KB	-rw-r--r--
man.nsupdate.html	28.11 KB	-rw-r--r--
man.pkcs11-destroy.html	5.57 KB	-rw-r--r--
man.pkcs11-keygen.html	7.13 KB	-rw-r--r--
man.pkcs11-list.html	5.46 KB	-rw-r--r--
man.pkcs11-tokens.html	3.73 KB	-rw-r--r--
man.rndc-confgen.html	11.48 KB	-rw-r--r--
man.rndc.conf.html	10.17 KB	-rw-r--r--
man.rndc.html	39.89 KB	-rw-r--r--
named.conf.default	1.76 KB	-rw-r--r--
notes.html	7.31 KB	-rw-r--r--
notes.pdf	50.96 KB	-rw-r--r--

Code Editor : man.dnssec-signzone.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-signzone</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-settime.html" title="dnssec-settime">
<link rel="next" href="man.dnssec-verify.html" title="dnssec-verify">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr><th colspan="3" align="center">dnssec-signzone</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="man.dnssec-settime.html">Prev</a>�</td>
<th width="60%" align="center">Manual pages</th>
<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-verify.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
<div class="refentry">
<a name="man.dnssec-signzone"></a><div class="titlepage"></div>

<div class="refnamediv">
<h2>Name</h2>

 dnssec-signzone
 &#8212; DNSSEC zone signing tool
 
</div>

<div class="refsynopsisdiv">
<h2>Synopsis</h2>
 <div class="cmdsynopsis">
 <code class="command">dnssec-signzone</code> 
 [<code class="option">-a</code>]
 [<code class="option">-c <code>class</code></code>]
 [<code class="option">-d <code>directory</code></code>]
 [<code class="option">-D</code>]
 [<code class="option">-E <code>engine</code></code>]
 [<code class="option">-e <code>end-time</code></code>]
 [<code class="option">-f <code>output-file</code></code>]
 [<code class="option">-g</code>]
 [<code class="option">-h</code>]
 [<code class="option">-i <code>interval</code></code>]
 [<code class="option">-I <code>input-format</code></code>]
 [<code class="option">-j <code>jitter</code></code>]
 [<code class="option">-K <code>directory</code></code>]
 [<code class="option">-k <code>key</code></code>]
 [<code class="option">-L <code>serial</code></code>]
 [<code class="option">-l <code>domain</code></code>]
 [<code class="option">-M <code>maxttl</code></code>]
 [<code class="option">-N <code>soa-serial-format</code></code>]
 [<code class="option">-o <code>origin</code></code>]
 [<code class="option">-O <code>output-format</code></code>]
 [<code class="option">-P</code>]
 [<code class="option">-p</code>]
 [<code class="option">-Q</code>]
 [<code class="option">-R</code>]
 [<code class="option">-r <code>randomdev</code></code>]
 [<code class="option">-S</code>]
 [<code class="option">-s <code>start-time</code></code>]
 [<code class="option">-T <code>ttl</code></code>]
 [<code class="option">-t</code>]
 [<code class="option">-u</code>]
 [<code class="option">-v <code>level</code></code>]
 [<code class="option">-V</code>]
 [<code class="option">-X <code>extended end-time</code></code>]
 [<code class="option">-x</code>]
 [<code class="option">-z</code>]
 [<code class="option">-3 <code>salt</code></code>]
 [<code class="option">-H <code>iterations</code></code>]
 [<code class="option">-A</code>]
 {zonefile}
 [key...]
 </div>
 </div>

<div class="refsection">
<a name="id-1.14.16.7"></a><h2>DESCRIPTION</h2>

dnssec-signzone
 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
 <code class="filename">keyset</code> file for each child zone.
 
 </div>

<div class="refsection">
<a name="id-1.14.16.8"></a><h2>OPTIONS</h2>

<div class="variablelist"><dl class="variablelist">
<dt>-a</dt>
<dd>
 
 Verify all generated signatures.
 
 </dd>
<dt>-c <code>class</code></dt>
<dd>
 
 Specifies the DNS class of the zone.
 
 </dd>
<dt>-C</dt>
<dd>
 
 Compatibility mode: Generate a
 <code class="filename">keyset-<code>zonename</code></code>
 file in addition to
 <code class="filename">dsset-<code>zonename</code></code>
 when signing a zone, for use by older versions of
 dnssec-signzone.
 
 </dd>
<dt>-d <code>directory</code></dt>
<dd>
 
 Look for <code class="filename">dsset-</code> or
 <code class="filename">keyset-</code> files in <code class="option">directory</code>.
 
 </dd>
<dt>-D</dt>
<dd>
 
	 Output only those record types automatically managed by
	 dnssec-signzone, i.e. RRSIG, NSEC,
	 NSEC3 and NSEC3PARAM records. If smart signing
	 (<code class="option">-S</code>) is used, DNSKEY records are also
	 included. The resulting file can be included in the original
	 zone file with $INCLUDE. This option
	 cannot be combined with <code class="option">-O raw</code>,
 <code class="option">-O map</code>, or serial number updating.
 
 </dd>
<dt>-E <code>engine</code></dt>
<dd>
 
 When applicable, specifies the hardware to use for
 cryptographic operations, such as a secure key store used
 for signing.
 
 
 When BIND is built with OpenSSL PKCS#11 support, this defaults
 to the string "pkcs11", which identifies an OpenSSL engine
 that can drive a cryptographic accelerator or hardware service
 module. When BIND is built with native PKCS#11 cryptography
 (--enable-native-pkcs11), it defaults to the path of the PKCS#11
 provider library specified via "--with-pkcs11".
 
 </dd>
<dt>-g</dt>
<dd>
 
 Generate DS records for child zones from
 <code class="filename">dsset-</code> or <code class="filename">keyset-</code>
 file. Existing DS records will be removed.
 
 </dd>
<dt>-K <code>directory</code></dt>
<dd>
 
 Key repository: Specify a directory to search for DNSSEC keys.
 If not specified, defaults to the current directory.
 
 </dd>
<dt>-k <code>key</code></dt>
<dd>
 
 Treat specified key as a key signing key ignoring any
 key flags. This option may be specified multiple times.
 
 </dd>
<dt>-l <code>domain</code></dt>
<dd>
 
 Generate a DLV set in addition to the key (DNSKEY) and DS sets.
 The domain is appended to the name of the records.
 
 </dd>
<dt>-M <code>maxttl</code></dt>
<dd>
 
 Sets the maximum TTL for the signed zone.
 Any TTL higher than <code>maxttl</code> in the
 input zone will be reduced to <code>maxttl</code>
 in the output. This provides certainty as to the largest
 possible TTL in the signed zone, which is useful to know when
 rolling keys because it is the longest possible time before
 signatures that have been retrieved by resolvers will expire
 from resolver caches. Zones that are signed with this
 option should be configured to use a matching
 <code class="option">max-zone-ttl</code> in <code class="filename">named.conf</code>.
 (Note: This option is incompatible with <code class="option">-D</code>,
 because it modifies non-DNSSEC data in the output zone.)
 
 </dd>
<dt>-s <code>start-time</code></dt>
<dd>
 
 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 <code class="option">start-time</code> is specified, the current
 time minus 1 hour (to allow for clock skew) is used.
 
 </dd>
<dt>-e <code>end-time</code></dt>
<dd>
 
 Specify the date and time when the generated RRSIG records
 expire. As with <code class="option">start-time</code>, 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 <code class="option">end-time</code> is
 specified, 30 days from the start time is used as a default.
 <code class="option">end-time</code> must be later than
 <code class="option">start-time</code>.
 
 </dd>
<dt>-X <code>extended end-time</code></dt>
<dd>
 
 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.
 
 
 As with <code class="option">start-time</code>, 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 <code class="option">extended end-time</code> is
 specified, the value of <code class="option">end-time</code> is used as
 the default. (<code class="option">end-time</code>, in turn, defaults to
 30 days from the start time.) <code class="option">extended end-time</code>
 must be later than <code class="option">start-time</code>.
 
 </dd>
<dt>-f <code>output-file</code></dt>
<dd>
 
 The name of the output file containing the signed zone. The
 default is to append <code class="filename">.signed</code> to
 the input filename. If <code class="option">output-file</code> is
 set to <code class="literal">"-"</code>, then the signed zone is
 written to the standard output, with a default output
 format of "full".
 
 </dd>
<dt>-h</dt>
<dd>
 
 Prints a short summary of the options and arguments to
 dnssec-signzone.
 
 </dd>
<dt>-V</dt>
<dd>
	 
	 Prints version information.
	 
 </dd>
<dt>-i <code>interval</code></dt>
<dd>
 
 When a previously-signed zone is passed as input, records
 may be resigned. The <code class="option">interval</code> 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.
 
 
 The default cycle interval is one quarter of the difference
 between the signature end and start times. So if neither
 <code class="option">end-time</code> or <code class="option">start-time</code>
 are specified, dnssec-signzone
 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.
 
 </dd>
<dt>-I <code>input-format</code></dt>
<dd>
 
 The format of the input zone file.
	 Possible formats are "text" (default),
	 "raw", and "map".
	 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.
 
 </dd>
<dt>-j <code>jitter</code></dt>
<dd>
 
 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.
 a previously-signed zone is passed as input to the signer,
 all expired signatures have to be regenerated at about the
 same time. The <code class="option">jitter</code> option specifies a
 jitter window that will be used to randomize the signature
 expire time, thus spreading incremental signature
 regeneration over time.
 
 
 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.
 
 </dd>
<dt>-L <code>serial</code></dt>
<dd>
 
 When writing a signed zone to "raw" or "map" format, set the
 "source serial" value in the header to the specified serial
 number. (This is expected to be used primarily for testing
 purposes.)
 
 </dd>
<dt>-n <code>ncpus</code></dt>
<dd>
 
 Specifies the number of threads to use. By default, one
 thread is started for each detected CPU.
 
 </dd>
<dt>-N <code>soa-serial-format</code></dt>
<dd>
 
 The SOA serial number format of the signed zone.
	 Possible formats are "keep" (default),
 "increment", "unixtime",
 and "date".

<div class="variablelist"><dl class="variablelist">
<dt>"keep"</dt>
<dd>
 Do not modify the SOA serial number.
	 </dd>
<dt>"increment"</dt>
<dd>
 Increment the SOA serial number using RFC 1982
 arithmetics.
	 </dd>
<dt>"unixtime"</dt>
<dd>
 Set the SOA serial number to the number of seconds
	 since epoch.
	 </dd>
<dt>"date"</dt>
<dd>
 Set the SOA serial number to today's date in
 YYYYMMDDNN format.
	 </dd>
</dl></div>

</dd>
<dt>-o <code>origin</code></dt>
<dd>
 
 The zone origin. If not specified, the name of the zone file
 is assumed to be the origin.
 
 </dd>
<dt>-O <code>output-format</code></dt>
<dd>
 
 The format of the output file containing the signed zone.
	 Possible formats are "text" (default),
 which is the standard textual representation of the zone;
	 "full", which is text output in a
 format suitable for processing by external scripts;
 and "map", "raw",
 and "raw=N", which store the zone in
 binary formats for rapid loading by named.
 "raw=N" specifies the format version of
 the raw zone file: if N is 0, the raw file can be read by
 any version of named; if N is 1, the file
 can be read by release 9.9.0 or higher; the default is 1.
 
 </dd>
<dt>-p</dt>
<dd>
 
 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.
 
 </dd>
<dt>-P</dt>
<dd>
 
	 Disable post sign verification tests.
 
 
	 The post sign verification test ensures that for each algorithm
	 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
	 in the zone are signed by the algorithm.
	 This option skips these tests.
 
 </dd>
<dt>-Q</dt>
<dd>
 
	 Remove signatures from keys that are no longer active.
 
 
 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 <code class="option">-Q</code>
 forces dnssec-signzone to remove
 signatures from keys that are no longer active. This
 enables ZSK rollover using the procedure described in
 RFC 4641, section 4.2.1.1 ("Pre-Publish Key Rollover").
 
 </dd>
<dt>-R</dt>
<dd>
 
	 Remove signatures from keys that are no longer published.
 
 
 This option is similar to <code class="option">-Q</code>, except it
 forces dnssec-signzone to signatures from
 keys that are no longer published. This enables ZSK rollover
 using the procedure described in RFC 4641, section 4.2.1.2
 ("Double Signature Zone Signing Key Rollover").
 
 </dd>
<dt>-r <code>randomdev</code></dt>
<dd>
 
 Specifies the source of randomness. If the operating
 system does not provide a <code class="filename">/dev/random</code>
 or equivalent device, the default source of randomness
 is keyboard input. <code class="filename">randomdev</code>
 specifies
 the name of a character device or file containing random
 data to be used instead of the default. The special value
 <code class="filename">keyboard</code> indicates that keyboard
 input should be used.
 
 </dd>
<dt>-S</dt>
<dd>
 
 Smart signing: Instructs dnssec-signzone to
 search the key repository for keys that match the zone being
 signed, and to include them in the zone if appropriate.
 
 
 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:
 
 <div class="variablelist"><dl class="variablelist">
<dt></dt>
<dd>
 
 If no timing metadata has been set for the key, the key is
 published in the zone and used to sign the zone.
 
	 </dd>
<dt></dt>
<dd>
 
 If the key's publication date is set and is in the past, the
 key is published in the zone.
 
	 </dd>
<dt></dt>
<dd>
 
 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.
 
	 </dd>
<dt></dt>
<dd>
 
 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.
 
	 </dd>
<dt></dt>
<dd>
 
 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.
 
	 </dd>
</dl></div>
 </dd>
<dt>-T <code>ttl</code></dt>
<dd>
 
 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
 record. This option is ignored when signing without
 <code class="option">-S</code>, 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
 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.
 
 </dd>
<dt>-t</dt>
<dd>
 
 Print statistics at completion.
 
 </dd>
<dt>-u</dt>
<dd>
 
 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, dnssec-signzone will
 retain the existing chain when re-signing.
 
 </dd>
<dt>-v <code>level</code></dt>
<dd>
 
 Sets the debugging level.
 
 </dd>
<dt>-x</dt>
<dd>
 
 Only sign the DNSKEY RRset with key-signing keys, and omit
 signatures from zone-signing keys. (This is similar to the
 dnssec-dnskey-kskonly yes; zone option in
 named.)
 
 </dd>
<dt>-z</dt>
<dd>
 
 Ignore KSK flag on key when determining what to sign. This
 causes KSK-flagged keys to sign all records, not just the
 DNSKEY RRset. (This is similar to the
 update-check-ksk no; zone option in
 named.)
 
 </dd>
<dt>-3 <code>salt</code></dt>
<dd>
 
 Generate an NSEC3 chain with the given hex encoded salt.
	 A dash (<code>salt</code>) can
	 be used to indicate that no salt is to be used when generating		 the NSEC3 chain.
 
 </dd>
<dt>-H <code>iterations</code></dt>
<dd>
 
	 When generating an NSEC3 chain, use this many iterations. The
	 default is 10.
 
 </dd>
<dt>-A</dt>
<dd>
 
	 When generating an NSEC3 chain set the OPTOUT flag on all
	 NSEC3 records and do not generate NSEC3 records for insecure
	 delegations.
 
 
	 Using this option twice (i.e., <code class="option">-AA</code>)
	 turns the OPTOUT flag off for all records. This is useful
	 when using the <code class="option">-u</code> option to modify an NSEC3
	 chain which previously had OPTOUT set.
 
 </dd>
<dt>zonefile</dt>
<dd>
 
 The file containing the zone to be signed.
 
 </dd>
<dt>key</dt>
<dd>
 
	 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.
 
 </dd>
</dl></div>
 </div>

<div class="refsection">
<a name="id-1.14.16.9"></a><h2>EXAMPLE</h2>

The following command signs the <code>example.com</code>
 zone with the DSA key generated by dnssec-keygen
 (Kexample.com.+003+17247). Because the -S option
 is not being used, the zone's keys must be in the master file
 (<code class="filename">db.example.com</code>). This invocation looks
 for <code class="filename">dsset</code> files, in the current directory,
 so that DS records can be imported from them (-g).
 
<pre class="programlisting">% dnssec-signzone -g -o example.com db.example.com \
Kexample.com.+003+17247
db.example.com.signed
%</pre>
 
 In the above example, dnssec-signzone creates
 the file <code class="filename">db.example.com.signed</code>. This
 file should be referenced in a zone statement in a
 <code class="filename">named.conf</code> file.
 
 
 This example re-signs a previously signed zone with default parameters.
 The private keys are assumed to be in the current directory.
 
<pre class="programlisting">% cp db.example.com.signed db.example.com
% dnssec-signzone -o example.com db.example.com
db.example.com.signed
%</pre>
 </div>

dnssec-keygen(8)
 ,
 BIND 9 Administrator Reference Manual,
 RFC 4033, RFC 4641.
 
 </div>

</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="man.dnssec-settime.html">Prev</a>�</td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
<td width="40%" align="right">�<a accesskey="n" href="man.dnssec-verify.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
dnssec-settime�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�dnssec-verify
</td>
</tr>
</table>
</div>
BIND 9.11.4-P2 (Extended Support Version)
</body>
</html>

${this.title}

Code Editor : man.dnssec-signzone.html