@@ -141,7 +141,7 @@ Specify the format of the zone file. Possible formats are
\fB"text"\fR
(default),
\fB"raw"\fR, and
\fB"fast"\fR.
\fB"map"\fR.
.RE
.PP
\-F \fIformat\fR
...
...
@@ -152,7 +152,7 @@ Specify the format of the output file specified. For
Possible formats are
\fB"text"\fR
(default), which is the standard textual representation of the zone, and
\fB"fast"\fR,
\fB"map"\fR,
\fB"raw"\fR, and
\fB"raw=N"\fR, which store the zone in a binary format for rapid loading by
\fBnamed\fR.
...
...
@@ -177,7 +177,7 @@ checks with the specified failure mode. Possible modes are
.PP
\-L \fIserial\fR
.RS 4
When compiling a zone to "raw" or "fast" format, set the "source serial" value in the header to the specified serial number. (This is expected to be used primarily for testing purposes.)
When compiling a 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.)
@@ -78,7 +78,7 @@ Output only those record types automatically managed by
\fBdnssec\-signzone\fR, i.e. RRSIG, NSEC, NSEC3 and NSEC3PARAM records. If smart signing (\fB\-S\fR) is used, DNSKEY records are also included. The resulting file can be included in the original zone file with
\fB$INCLUDE\fR. This option cannot be combined with
\fB\-O raw\fR,
\fB\-O fast\fR, or serial number updating.
\fB\-O map\fR, or serial number updating.
.RE
.PP
\-E \fIengine\fR
...
...
@@ -180,7 +180,7 @@ The format of the input zone file. Possible formats are
\fB"text"\fR
(default),
\fB"raw"\fR, and
\fB"fast"\fR. 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.
\fB"map"\fR. 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.
.RE
.PP
\-j \fIjitter\fR
...
...
@@ -194,7 +194,7 @@ Signature lifetime jitter also to some extent benefits validators and servers by
.PP
\-L \fIserial\fR
.RS 4
When writing a signed zone to "raw" or "fast" format, set the "source serial" value in the header to the specified serial number. (This is expected to be used primarily for testing purposes.)
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.)
.RE
.PP
\-n \fIncpus\fR
...
...
@@ -240,7 +240,7 @@ The format of the output file containing the signed zone. Possible formats are
\fB"text"\fR
(default), which is the standard textual representation of the zone;
\fB"full"\fR, which is text output in a format suitable for processing by external scripts; and
\fB"fast"\fR,
\fB"map"\fR,
\fB"raw"\fR, and
\fB"raw=N"\fR, which store the zone in binary formats for rapid loading by
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt>
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2598803">Discussion of MX Records</a></span></dt>
<dt><spanclass="sect1"><ahref="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt>
<dt><spanclass="sect1"><ahref="Bv9ARM.ch07.html#id2604496"><span><strongclass="command">Chroot</strong></span> and <span><strongclass="command">Setuid</strong></span></a></span></dt>
<dt><spanclass="sect1"><ahref="Bv9ARM.ch07.html#id2604564"><span><strongclass="command">Chroot</strong></span> and <span><strongclass="command">Setuid</strong></span></a></span></dt>