ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

cleanup trailing white space in SGML like files

Browse Source
This commit is contained in:
Mark Andrews
2015-10-22 16:09:46 +11:00
parent 04893d38e0
commit 30eec077db
74 changed files with 444 additions and 436 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
bin/check/named-checkconf.docbook
View File

@@ -71,7 +71,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>named-checkconf</command>
checks the syntax, but not the semantics, of a
<command>named</command> configuration file. The file is parsed
@@ -92,7 +92,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -184,7 +184,7 @@
</refsection>
<refsection><info><title>RETURN VALUES</title></info>
<para><command>named-checkconf</command>
returns an exit status of 1 if
errors were detected and 0 otherwise.
@@ -192,7 +192,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

12
bin/check/named-checkzone.docbook
View File

@@ -122,7 +122,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>named-checkzone</command>
checks the syntax and integrity of a zone file. It performs the
same checks as <command>named</command> does when loading a
@@ -143,7 +143,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -387,7 +387,7 @@
<listitem>
<para>
Check for records that are treated as different by DNSSEC but
are semantically equal in plain DNS.
are semantically equal in plain DNS.
Possible modes are <command>"fail"</command>,
<command>"warn"</command> (default) and
<command>"ignore"</command>.
@@ -511,7 +511,7 @@
</refsection>
<refsection><info><title>RETURN VALUES</title></info>
<para><command>named-checkzone</command>
returns an exit status of 1 if
errors were detected and 0 otherwise.
@@ -519,12 +519,12 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citerefentry>
<refentrytitle>named-checkconf</refentrytitle><manvolnum>8</manvolnum>
<refentrytitle>named-checkconf</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citetitle>RFC 1035</citetitle>,
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.

8
bin/confgen/ddns-confgen.docbook
View File

@@ -67,7 +67,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
<command>tsig-keygen</command> and <command>ddns-confgen</command>
are invocation methods for a utility that generates keys for use
@@ -99,7 +99,7 @@
local DDNS key for use with <command>nsupdate -l</command>:
it does this when a zone is configured with
<command>update-policy local;</command>.
<command>ddns-confgen</command> is only needed when a
<command>ddns-confgen</command> is only needed when a
more elaborate configuration is required: for instance,
if <command>nsupdate</command> is to be used from a remote
system.
@@ -107,7 +107,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -215,7 +215,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>nsupdate</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,

8
bin/confgen/rndc-confgen.docbook
View File

@@ -72,7 +72,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>rndc-confgen</command>
generates configuration files
for <command>rndc</command>. It can be used as a
@@ -90,7 +90,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -259,7 +259,7 @@
</refsection>
<refsection><info><title>EXAMPLES</title></info>
<para>
To allow <command>rndc</command> to be used with
no manual configuration, run
@@ -277,7 +277,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>rndc</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

14
bin/delv/delv.docbook
View File

@@ -85,7 +85,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>delv</command>
(Domain Entity Lookup &amp; Validation) is a tool for sending
DNS queries and validating the results, using the same internal
@@ -129,7 +129,7 @@
</refsection>
<refsection><info><title>SIMPLE USAGE</title></info>
<para>
A typical invocation of <command>delv</command> looks like:
@@ -196,7 +196,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -398,7 +398,7 @@
</refsection>
<refsection><info><title>QUERY OPTIONS</title></info>
<para><command>delv</command>
provides a number of query options which affect the way results are
@@ -585,7 +585,7 @@
<listitem>
<para>
Set or clear the display options
<option>+[no]comments</option>,
<option>+[no]comments</option>,
<option>+[no]rrcomments</option>, and
<option>+[no]trust</option> as a group.
</para>
@@ -668,13 +668,13 @@
</refsection>
<refsection><info><title>FILES</title></info>
<para><filename>/etc/bind.keys</filename></para>
<para><filename>/etc/resolv.conf</filename></para>
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dig</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,

22
bin/dig/dig.docbook
View File

@@ -98,7 +98,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dig</command>
(domain information groper) is a flexible tool
for interrogating DNS name servers. It performs DNS lookups and
@@ -144,7 +144,7 @@
<para>
The IN and CH class names overlap with the IN and CH top level
domain names. Either use the <option>-t</option> and
<option>-c</option> options to specify the type and class,
<option>-c</option> options to specify the type and class,
use the <option>-q</option> the specify the domain name, or
use "IN." and "CH." when looking up these top level domains.
</para>
@@ -152,7 +152,7 @@
</refsection>
<refsection><info><title>SIMPLE USAGE</title></info>
<para>
A typical invocation of <command>dig</command> looks like:
@@ -218,7 +218,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -421,7 +421,7 @@
</refsection>
<refsection><info><title>QUERY OPTIONS</title></info>
<para><command>dig</command>
provides a number of query options which affect
@@ -1160,7 +1160,7 @@
</refsection>
<refsection><info><title>MULTIPLE QUERIES</title></info>
<para>
The BIND 9 implementation of <command>dig </command>
@@ -1209,7 +1209,7 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
</refsection>
<refsection><info><title>IDN SUPPORT</title></info>
<para>
If <command>dig</command> has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
@@ -1218,13 +1218,13 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
reply from the server.
If you'd like to turn off the IDN support for some reason, defines
the <envar>IDN_DISABLE</envar> environment variable.
The IDN support is disabled if the variable is set when
The IDN support is disabled if the variable is set when
<command>dig</command> runs.
</para>
</refsection>
<refsection><info><title>FILES</title></info>
<para><filename>/etc/resolv.conf</filename>
</para>
<para><filename>${HOME}/.digrc</filename>
@@ -1232,7 +1232,7 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>host</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,
@@ -1247,7 +1247,7 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
</refsection>
<refsection><info><title>BUGS</title></info>
<para>
There are probably too many query options.
</para>

8
bin/dig/host.docbook
View File

@@ -77,7 +77,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>host</command>
is a simple utility for performing DNS lookups.
@@ -240,7 +240,7 @@
</para>
<para>
The <option>-s</option> option tells <command>host</command>
The <option>-s</option> option tells <command>host</command>
<emphasis>not</emphasis> to send the query to the next nameserver
if any server responds with a SERVFAIL response, which is the
reverse of normal stub resolver behavior.
@@ -260,10 +260,10 @@
</refsection>
<refsection><info><title>IDN SUPPORT</title></info>
<para>
If <command>host</command> has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
domain name) support, it can accept and display non-ASCII domain names.
<command>host</command> appropriately converts character encoding of
domain name before sending a request to DNS server or displaying a
reply from the server.

10
bin/dig/nslookup.docbook
View File

@@ -87,7 +87,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>Nslookup</command>
is a program to query Internet domain name servers. <command>Nslookup</command>
has two modes: interactive and non-interactive. Interactive mode allows
@@ -100,7 +100,7 @@
</refsection>
<refsection><info><title>ARGUMENTS</title></info>
<para>
Interactive mode is entered in the following cases:
<orderedlist numeration="loweralpha" inheritnum="ignore" continuation="restarts">
@@ -144,7 +144,7 @@ nslookup -query=hinfo -timeout=10
</refsection>
<refsection><info><title>INTERACTIVE COMMANDS</title></info>
<variablelist>
<varlistentry>
<term><constant>host</constant> <optional>server</optional></term>
@@ -480,13 +480,13 @@ nslookup -query=hinfo -timeout=10
</refsection>
<refsection><info><title>FILES</title></info>
<para><filename>/etc/resolv.conf</filename>
</para>
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dig</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,

14
bin/dnssec/dnssec-dsfromkey.docbook
View File

@@ -84,7 +84,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dnssec-dsfromkey</command>
outputs the Delegation Signer (DS) resource record (RR), as defined in
RFC 3658 and RFC 4509, for the given key(s).
@@ -92,7 +92,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -183,7 +183,7 @@
<para>
Include ZSKs when generating DS records. Without this option,
only keys which have the KSK flag set will be converted to DS
records and printed. Useful only in zone file mode.
records and printed. Useful only in zone file mode.
</para>
</listitem>
</varlistentry>
@@ -252,7 +252,7 @@
</refsection>
<refsection><info><title>EXAMPLE</title></info>
<para>
To build the SHA-256 DS RR from the
<userinput>Kexample.com.+003+26160</userinput>
@@ -268,7 +268,7 @@
</refsection>
<refsection><info><title>FILES</title></info>
<para>
The keyfile can be designed by the key identification
<filename>Knnnn.+aaa+iiiii</filename> or the full file name
@@ -283,14 +283,14 @@
</refsection>
<refsection><info><title>CAVEAT</title></info>
<para>
A keyfile error can give a "file not found" even if the file exists.
</para>
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

14
bin/dnssec/dnssec-importkey.docbook
View File

@@ -71,7 +71,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dnssec-importkey</command>
reads a public DNSKEY record and generates a pair of
.key/.private files. The DNSKEY record may be read from an
@@ -92,7 +92,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -110,7 +110,7 @@
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-K <replaceable class="parameter">directory</replaceable></term>
<listitem>
@@ -142,7 +142,7 @@
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-v <replaceable class="parameter">level</replaceable></term>
<listitem>
@@ -165,7 +165,7 @@
</refsection>
<refsection><info><title>TIMING OPTIONS</title></info>
<para>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
@@ -205,7 +205,7 @@
</refsection>
<refsection><info><title>FILES</title></info>
<para>
A keyfile can be designed by the key identification
<filename>Knnnn.+aaa+iiiii</filename> or the full file name
@@ -215,7 +215,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

14
bin/dnssec/dnssec-keyfromlabel.docbook
View File

@@ -79,7 +79,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dnssec-keyfromlabel</command>
generates a key pair of files that referencing a key object stored
in a cryptographic hardware service module (HSM). The private key
@@ -96,7 +96,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -364,7 +364,7 @@
</refsection>
<refsection><info><title>TIMING OPTIONS</title></info>
<para>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
@@ -450,7 +450,7 @@
</para>
<para>
If the key is being created as an explicit successor to another
key, then the default prepublication interval is 30 days;
key, then the default prepublication interval is 30 days;
otherwise it is zero.
</para>
<para>
@@ -467,7 +467,7 @@
</refsection>
<refsection><info><title>GENERATED KEY FILES</title></info>
<para>
When <command>dnssec-keyfromlabel</command> completes
successfully,
@@ -491,7 +491,7 @@
</para>
</listitem>
</itemizedlist>
<para><command>dnssec-keyfromlabel</command>
<para><command>dnssec-keyfromlabel</command>
creates two files, with names based
on the printed string. <filename>Knnnn.+aaa+iiiii.key</filename>
contains the public key, and
@@ -513,7 +513,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

16
bin/dnssec/dnssec-keygen.docbook
View File

@@ -96,7 +96,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dnssec-keygen</command>
generates keys for DNSSEC (Secure DNS), as defined in RFC 2535
and RFC 4034. It can also generate keys for use with
@@ -111,7 +111,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -441,7 +441,7 @@
</refsection>
<refsection><info><title>TIMING OPTIONS</title></info>
<para>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
@@ -529,7 +529,7 @@
</para>
<para>
If the key is being created as an explicit successor to another
key, then the default prepublication interval is 30 days;
key, then the default prepublication interval is 30 days;
otherwise it is zero.
</para>
<para>
@@ -547,7 +547,7 @@
<refsection><info><title>GENERATED KEYS</title></info>
<para>
When <command>dnssec-keygen</command> completes
successfully,
@@ -572,7 +572,7 @@
</para>
</listitem>
</itemizedlist>
<para><command>dnssec-keygen</command>
<para><command>dnssec-keygen</command>
creates two files, with names based
on the printed string. <filename>Knnnn.+aaa+iiiii.key</filename>
contains the public key, and
@@ -600,7 +600,7 @@
</refsection>
<refsection><info><title>EXAMPLE</title></info>
<para>
To generate a 768-bit DSA key for the domain
<userinput>example.com</userinput>, the following command would be
@@ -622,7 +622,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dnssec-signzone</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

8
bin/dnssec/dnssec-revoke.docbook
View File

@@ -60,7 +60,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dnssec-revoke</command>
reads a DNSSEC key file, sets the REVOKED bit on the key as defined
in RFC 5011, and creates a new pair of key files containing the
@@ -69,7 +69,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -80,7 +80,7 @@
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-K <replaceable class="parameter">directory</replaceable></term>
<listitem>
@@ -159,7 +159,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

20
bin/dnssec/dnssec-settime.docbook
View File

@@ -66,7 +66,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dnssec-settime</command>
reads a DNSSEC private key file and sets the key timing metadata
as specified by the <option>-P</option>, <option>-A</option>,
@@ -93,7 +93,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -105,13 +105,13 @@
fail when attempting to update a legacy key. With this option,
the key will be recreated in the new format, but with the
original key data retained. The key's creation date will be
set to the present time. If no other values are specified,
then the key's publication and activation dates will also
set to the present time. If no other values are specified,
then the key's publication and activation dates will also
be set to the present time.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-K <replaceable class="parameter">directory</replaceable></term>
<listitem>
@@ -145,7 +145,7 @@
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-V</term>
<listitem>
@@ -184,7 +184,7 @@
</refsection>
<refsection><info><title>TIMING OPTIONS</title></info>
<para>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
@@ -281,7 +281,7 @@
</para>
<para>
If the key is being set to be an explicit successor to another
key, then the default prepublication interval is 30 days;
key, then the default prepublication interval is 30 days;
otherwise it is zero.
</para>
<para>
@@ -297,7 +297,7 @@
</refsection>
<refsection><info><title>PRINTING OPTIONS</title></info>
<para>
<command>dnssec-settime</command> can also be used to print the
timing metadata associated with a key.
@@ -335,7 +335,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

14
bin/dnssec/dnssec-signzone.docbook
View File

@@ -107,7 +107,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dnssec-signzone</command>
signs a zone. It generates
NSEC and RRSIG records and produces a signed version of the
@@ -119,7 +119,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -174,7 +174,7 @@
(<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
cannot be combined with <option>-O raw</option>,
cannot be combined with <option>-O raw</option>,
<option>-O map</option>, or serial number updating.
</para>
</listitem>
@@ -551,7 +551,7 @@
<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
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>-Q</option>
@@ -632,7 +632,7 @@
<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.
used to sign the zone.
</para>
</listitem>
</varlistentry>
@@ -800,7 +800,7 @@
</refsection>
<refsection><info><title>EXAMPLE</title></info>
<para>
The following command signs the <userinput>example.com</userinput>
zone with the DSA key generated by <command>dnssec-keygen</command>
@@ -831,7 +831,7 @@ db.example.com.signed
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

6
bin/dnssec/dnssec-verify.docbook
View File

@@ -60,7 +60,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dnssec-verify</command>
verifies that a zone is fully signed for each algorithm found
in the DNSKEY RRset for the zone, and that the NSEC / NSEC3
@@ -69,7 +69,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -192,7 +192,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citerefentry>
<refentrytitle>dnssec-signzone</refentrytitle><manvolnum>8</manvolnum>

6
bin/named/bind9.xsl
View File

@@ -49,7 +49,7 @@
function loadGraphs(){
var g;
while(g = graphs.shift()){
// alert("going for: " + g.target);
if(g.data.length > 1){
@@ -59,7 +59,7 @@
}
<xsl:if test="server/counters[@type=&quot;qtype&quot;]/counter">
// Server Incoming Query Types
// Server Incoming Query Types
graphs.push({
'title' : "Server Incoming Query Types",
'target': 'chart_incoming_qtypes',
@@ -67,7 +67,7 @@
'data': [['Type','Counter'],<xsl:for-each select="server/counters[@type=&quot;qtype&quot;]/counter">['<xsl:value-of select="@name"/>',<xsl:value-of select="."/>],</xsl:for-each>]
});
</xsl:if>
<xsl:if test="server/counters[@type=&quot;opcode&quot;]/counter">
// Server Incoming Requests by opcode
graphs.push({

12
bin/named/lwresd.docbook
View File

@@ -77,7 +77,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>lwresd</command>
is the daemon providing name lookup
@@ -87,7 +87,7 @@
resolver protocol rather than the DNS protocol.
</para>
<para><command>lwresd</command>
<para><command>lwresd</command>
listens for resolver queries on a
UDP port on the IPv4 loopback interface, 127.0.0.1. This
means that <command>lwresd</command> can only be used by
@@ -115,7 +115,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
@@ -217,7 +217,7 @@
<replaceable class="parameter">trace</replaceable>,
<replaceable class="parameter">record</replaceable>,
<replaceable class="parameter">size</replaceable>, and
<replaceable class="parameter">mctx</replaceable>.
<replaceable class="parameter">mctx</replaceable>.
These correspond to the ISC_MEM_DEBUGXXXX flags described in
<filename>&lt;isc/mem.h&gt;</filename>.
</para>
@@ -324,7 +324,7 @@
</refsection>
<refsection><info><title>FILES</title></info>
<variablelist>
@@ -351,7 +351,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

30
bin/named/named.conf.docbook
View File

@@ -60,7 +60,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><filename>named.conf</filename> is the configuration file
for
<command>named</command>. Statements are enclosed
@@ -80,7 +80,7 @@
</refsection>
<refsection><info><title>ACL</title></info>
<literallayout class="normal">
acl <replaceable>string</replaceable> { <replaceable>address_match_element</replaceable>; ... };
@@ -88,7 +88,7 @@ acl <replaceable>string</replaceable> { <replaceable>address_match_element</repl
</refsection>
<refsection><info><title>KEY</title></info>
<literallayout class="normal">
key <replaceable>domain_name</replaceable> {
algorithm <replaceable>string</replaceable>;
@@ -98,7 +98,7 @@ key <replaceable>domain_name</replaceable> {
</refsection>
<refsection><info><title>MASTERS</title></info>
<literallayout class="normal">
masters <replaceable>string</replaceable> <optional> port <replaceable>integer</replaceable> </optional> {
( <replaceable>masters</replaceable> | <replaceable>ipv4_address</replaceable> <optional>port <replaceable>integer</replaceable></optional> |
@@ -108,7 +108,7 @@ masters <replaceable>string</replaceable> <optional> port <replaceable>integer</
</refsection>
<refsection><info><title>SERVER</title></info>
<literallayout class="normal">
server ( <replaceable>ipv4_address<optional>/prefixlen</optional></replaceable> | <replaceable>ipv6_address<optional>/prefixlen</optional></replaceable> ) {
bogus <replaceable>boolean</replaceable>;
@@ -132,7 +132,7 @@ server ( <replaceable>ipv4_address<optional>/prefixlen</optional></replaceable>
</refsection>
<refsection><info><title>TRUSTED-KEYS</title></info>
<literallayout class="normal">
trusted-keys {
<replaceable>domain_name</replaceable> <replaceable>flags</replaceable> <replaceable>protocol</replaceable> <replaceable>algorithm</replaceable> <replaceable>key</replaceable>; ...
@@ -141,7 +141,7 @@ trusted-keys {
</refsection>
<refsection><info><title>MANAGED-KEYS</title></info>
<literallayout class="normal">
managed-keys {
<replaceable>domain_name</replaceable> <constant>initial-key</constant> <replaceable>flags</replaceable> <replaceable>protocol</replaceable> <replaceable>algorithm</replaceable> <replaceable>key</replaceable>; ...
@@ -150,7 +150,7 @@ managed-keys {
</refsection>
<refsection><info><title>CONTROLS</title></info>
<literallayout class="normal">
controls {
inet ( <replaceable>ipv4_address</replaceable> | <replaceable>ipv6_address</replaceable> | * )
@@ -163,7 +163,7 @@ controls {
</refsection>
<refsection><info><title>LOGGING</title></info>
<literallayout class="normal">
logging {
channel <replaceable>string</replaceable> {
@@ -182,7 +182,7 @@ logging {
</refsection>
<refsection><info><title>LWRES</title></info>
<literallayout class="normal">
lwres {
listen-on <optional> port <replaceable>integer</replaceable> </optional> {
@@ -198,7 +198,7 @@ lwres {
</refsection>
<refsection><info><title>OPTIONS</title></info>
<literallayout class="normal">
options {
avoid-v4-udp-ports { <replaceable>port</replaceable>; ... };
@@ -413,7 +413,7 @@ options {
</refsection>
<refsection><info><title>VIEW</title></info>
<literallayout class="normal">
view <replaceable>string</replaceable> <replaceable>optional_class</replaceable> {
match-clients { <replaceable>address_match_element</replaceable>; ... };
@@ -583,7 +583,7 @@ view <replaceable>string</replaceable> <replaceable>optional_class</replaceable>
</refsection>
<refsection><info><title>ZONE</title></info>
<literallayout class="normal">
zone <replaceable>string</replaceable> <replaceable>optional_class</replaceable> {
type ( master | slave | stub | hint | redirect |
@@ -681,13 +681,13 @@ zone <replaceable>string</replaceable> <replaceable>optional_class</replaceable>
</refsection>
<refsection><info><title>FILES</title></info>
<para><filename>/etc/named.conf</filename>
</para>
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

12
bin/named/named.docbook
View File

@@ -87,7 +87,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>named</command>
is a Domain Name System (DNS) server,
part of the BIND 9 distribution from ISC. For more
@@ -103,7 +103,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -436,7 +436,7 @@
</refsection>
<refsection><info><title>SIGNALS</title></info>
<para>
In routine operation, signals should not be used to control
the nameserver; <command>rndc</command> should be used
@@ -472,7 +472,7 @@
</refsection>
<refsection><info><title>CONFIGURATION</title></info>
<para>
The <command>named</command> configuration file is too complex
to describe in detail here. A complete description is provided
@@ -492,7 +492,7 @@
</refsection>
<refsection><info><title>FILES</title></info>
<variablelist>
@@ -519,7 +519,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citetitle>RFC 1033</citetitle>,
<citetitle>RFC 1034</citetitle>,
<citetitle>RFC 1035</citetitle>,

14
bin/nsupdate/nsupdate.docbook
View File

@@ -85,7 +85,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>nsupdate</command>
is used to submit Dynamic DNS Update requests as defined in RFC 2136
to a name server.
@@ -144,7 +144,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -353,7 +353,7 @@
</refsection>
<refsection><info><title>INPUT FORMAT</title></info>
<para><command>nsupdate</command>
reads input from
<parameter>filename</parameter>
@@ -785,7 +785,7 @@
</refsection>
<refsection><info><title>EXAMPLES</title></info>
<para>
The examples below show how
<command>nsupdate</command>
@@ -836,7 +836,7 @@
</refsection>
<refsection><info><title>FILES</title></info>
<variablelist>
<varlistentry>
@@ -885,7 +885,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citetitle>RFC 2136</citetitle>,
<citetitle>RFC 3007</citetitle>,
@@ -907,7 +907,7 @@
</refsection>
<refsection><info><title>BUGS</title></info>
<para>
The TSIG key is redundantly stored in two separate files.
This is a consequence of nsupdate using the DST library

6
bin/pkcs11/pkcs11-destroy.docbook
View File

@@ -59,7 +59,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
<command>pkcs11-destroy</command> destroys keys stored in a
PKCS#11 device, identified by their <option>ID</option> or
@@ -73,7 +73,7 @@
</refsection>
<refsection><info><title>ARGUMENTS</title></info>
<variablelist>
<varlistentry>
<term>-m <replaceable class="parameter">module</replaceable></term>
@@ -138,7 +138,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citerefentry>
<refentrytitle>pkcs11-keygen</refentrytitle><manvolnum>8</manvolnum>

6
bin/pkcs11/pkcs11-keygen.docbook
View File

@@ -62,7 +62,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
<command>pkcs11-keygen</command> causes a PKCS#11 device to generate
a new key pair with the given <option>label</option> (which must be
@@ -71,7 +71,7 @@
</refsection>
<refsection><info><title>ARGUMENTS</title></info>
<variablelist>
<varlistentry>
<term>-a <replaceable class="parameter">algorithm</replaceable></term>
@@ -185,7 +185,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citerefentry>
<refentrytitle>pkcs11-destroy</refentrytitle><manvolnum>8</manvolnum>

6
bin/pkcs11/pkcs11-list.docbook
View File

@@ -57,7 +57,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
<command>pkcs11-list</command>
lists the PKCS#11 objects with <option>ID</option> or
@@ -66,7 +66,7 @@
</refsection>
<refsection><info><title>ARGUMENTS</title></info>
<variablelist>
<varlistentry>
<term>-P</term>
@@ -130,7 +130,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citerefentry>
<refentrytitle>pkcs11-destroy</refentrytitle><manvolnum>8</manvolnum>

6
bin/pkcs11/pkcs11-tokens.docbook
View File

@@ -51,7 +51,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
<command>pkcs11-tokens</command>
lists the PKCS#11 available tokens with defaults from the slot/token
@@ -60,7 +60,7 @@
</refsection>
<refsection><info><title>ARGUMENTS</title></info>
<variablelist>
<varlistentry>
<term>-m <replaceable class="parameter">module</replaceable></term>
@@ -76,7 +76,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citerefentry>
<refentrytitle>pkcs11-destroy</refentrytitle><manvolnum>8</manvolnum>

8
bin/python/dnssec-checkds.docbook
View File

@@ -65,7 +65,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dnssec-checkds</command>
verifies the correctness of Delegation Signer (DS) or DNSSEC
Lookaside Validation (DLV) resource records for keys in a specified
@@ -74,7 +74,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -92,7 +92,7 @@
<term>-l <replaceable class="parameter">domain</replaceable></term>
<listitem>
<para>
Check for a DLV record in the specified lookaside domain,
Check for a DLV record in the specified lookaside domain,
instead of checking for a DS record in the zone's parent.
For example, to check for DLV records for "example.com"
in ISC's DLV zone, use:
@@ -124,7 +124,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dnssec-dsfromkey</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

8
bin/python/dnssec-coverage.docbook
View File

@@ -61,7 +61,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>dnssec-coverage</command>
verifies that the DNSSEC keys for a given zone or a set of zones
have timing metadata set properly to ensure no future lapses in DNSSEC
@@ -90,7 +90,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -122,7 +122,7 @@
<para>
The length of time to check for DNSSEC coverage. Key events
scheduled further into the future than <option>duration</option>
will be ignored, and assumed to be correct.
will be ignored, and assumed to be correct.
</para>
<para>
The value of <option>duration</option> can be set in seconds,
@@ -243,7 +243,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citerefentry>
<refentrytitle>dnssec-checkds</refentrytitle><manvolnum>8</manvolnum>

8
bin/rndc/rndc.conf.docbook
View File

@@ -60,7 +60,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><filename>rndc.conf</filename> is the configuration file
for <command>rndc</command>, the BIND 9 name server control
utility. This file has a similar structure and syntax to
@@ -147,7 +147,7 @@
</refsection>
<refsection><info><title>EXAMPLE</title></info>
<para><programlisting>
options {
@@ -219,7 +219,7 @@
</refsection>
<refsection><info><title>NAME SERVER CONFIGURATION</title></info>
<para>
The name server must be configured to accept rndc connections and
to recognize the key specified in the <filename>rndc.conf</filename>
@@ -230,7 +230,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>rndc</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,

14
bin/rndc/rndc.docbook
View File

@@ -70,7 +70,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>rndc</command>
controls the operation of a name
server. It supersedes the <command>ndc</command> utility
@@ -102,7 +102,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -226,7 +226,7 @@
</refsection>
<refsection><info><title>COMMANDS</title></info>
<para>
A list of commands supported by <command>rndc</command> can
be seen by running <command>rndc</command> without arguments.
@@ -745,7 +745,7 @@
operations (such as signing or generating
NSEC3 chains) is stored in the zone in the form
of DNS resource records of type
<command>sig-signing-type</command>.
<command>sig-signing-type</command>.
<command>rndc signing -list</command> converts
these records into a human-readable form,
indicating which keys are currently signing
@@ -771,7 +771,7 @@
flags, iterations, and salt, in that order.
</para>
<para>
Currently, the only defined value for hash algorithm
Currently, the only defined value for hash algorithm
is <literal>1</literal>, representing SHA-1.
The <option>flags</option> may be set to
<literal>0</literal> or <literal>1</literal>,
@@ -964,7 +964,7 @@
</refsection>
<refsection><info><title>LIMITATIONS</title></info>
<para>
There is currently no way to provide the shared secret for a
<option>key_id</option> without using the configuration file.
@@ -975,7 +975,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>rndc.conf</refentrytitle><manvolnum>5</manvolnum>
</citerefentry>,

4
bin/tools/arpaname.docbook
View File

@@ -51,7 +51,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
<command>arpaname</command> translates IP addresses (IPv4 and
IPv6) to the corresponding IN-ADDR.ARPA or IP6.ARPA names.
@@ -59,7 +59,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citetitle>BIND 9 Administrator Reference Manual</citetitle>.
</para>

6
bin/tools/dnstap-read.docbook
View File

@@ -53,7 +53,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
<command>dnstap-read</command>
reads <command>dnstap</command> data from a specified file
@@ -65,7 +65,7 @@
</refsection>
<refsection><info><title>OPTIONS</title></info>
<variablelist>
<varlistentry>
@@ -102,7 +102,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>

6
bin/tools/genrandom.docbook
View File

@@ -56,7 +56,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
<command>genrandom</command>
generates a file or a set of files containing a specified quantity
@@ -66,7 +66,7 @@
</refsection>
<refsection><info><title>ARGUMENTS</title></info>
<variablelist>
<varlistentry>
<term>-n <replaceable class="parameter">number</replaceable></term>
@@ -99,7 +99,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citerefentry>
<refentrytitle>rand</refentrytitle><manvolnum>3</manvolnum>

6
bin/tools/isc-hmac-fixup.docbook
View File

@@ -54,7 +54,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
Versions of BIND 9 up to and including BIND 9.6 had a bug causing
HMAC-SHA* TSIG keys which were longer than the digest length of the
@@ -81,7 +81,7 @@
</refsection>
<refsection><info><title>SECURITY CONSIDERATIONS</title></info>
<para>
Secrets that have been converted by <command>isc-hmac-fixup</command>
are shortened, but as this is how the HMAC protocol works in
@@ -93,7 +93,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citetitle>BIND 9 Administrator Reference Manual</citetitle>,
<citetitle>RFC 2104</citetitle>.

10
bin/tools/mdig.docbook
View File

@@ -77,7 +77,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>mdig</command>
is a multiple/pipelined query version of <command>dig</command>:
instead of waiting for a response after sending each query,
@@ -126,7 +126,7 @@
</refsection>
<refsection><info><title>ANYWHERE OPTIONS</title></info>
<para>
The <option>-f</option> option makes <command>mdig</command>
@@ -149,7 +149,7 @@
</refsection>
<refsection><info><title>GLOBAL OPTIONS</title></info>
<para>
The <option>-4</option> option forces <command>mdig</command> to
@@ -390,7 +390,7 @@
</refsection>
<refsection><info><title>LOCAL OPTIONS</title></info>
<para>
The <option>-c</option> option sets the query class to
@@ -653,7 +653,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para><citerefentry>
<refentrytitle>dig</refentrytitle><manvolnum>1</manvolnum>
</citerefentry>,

8
bin/tools/named-journalprint.docbook
View File

@@ -52,14 +52,14 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
<command>named-journalprint</command>
prints the contents of a zone journal file in a human-readable
form.
form.
</para>
<para>
Journal files are automatically created by <command>named</command>
Journal files are automatically created by <command>named</command>
when changes are made to dynamic zones (e.g., by
<command>nsupdate</command>). They record each addition
or deletion of a resource record, in binary format, allowing the
@@ -79,7 +79,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>

4
bin/tools/named-rrchecker.docbook
View File

@@ -56,7 +56,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para><command>named-rrchecker</command>
read a individual DNS resource record from standard input and checks if it
is syntactically correct.
@@ -85,7 +85,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citetitle>RFC 1034</citetitle>,
<citetitle>RFC 1035</citetitle>,

6
bin/tools/nsec3hash.docbook
View File

@@ -55,7 +55,7 @@
</refsynopsisdiv>
<refsection><info><title>DESCRIPTION</title></info>
<para>
<command>nsec3hash</command> generates an NSEC3 hash based on
a set of NSEC3 parameters. This can be used to check the validity
@@ -64,7 +64,7 @@
</refsection>
<refsection><info><title>ARGUMENTS</title></info>
<variablelist>
<varlistentry>
<term>salt</term>
@@ -108,7 +108,7 @@
</refsection>
<refsection><info><title>SEE ALSO</title></info>
<para>
<citetitle>BIND 9 Administrator Reference Manual</citetitle>,
<citetitle>RFC 5155</citetitle>.