- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- File: $Id: Bv9ARM-book.xml,v 1.476 2011/01/13 01:59:27 marka Exp $ -->
+<!-- File: $Id: Bv9ARM-book.xml,v 1.477 2011/01/20 10:17:23 marka Exp $ -->
<book xmlns:xi="http://www.w3.org/2001/XInclude">
<title>BIND 9 Administrator Reference Manual</title>
</para>
<para>
For more detail on ordering responses, check the
- <command>rrset-order</command> substatement in the
+ <command>rrset-order</command> sub-statement in the
<command>options</command> statement, see
<xref endterm="rrset_ordering_title" linkend="rrset_ordering"/>.
</para>
IPv6 addresses will be ignored for the purposes
of determining if dns64 is to be applied. Any
non matching address will prevent any further
- DNS64 processing from occuring for this client.
+ DNS64 processing from occurring for this client.
</para>
<para>
A optional <command>suffix</command> can also
buffer (<command>edns-udp-size</command>).
</para>
<para>
- Setting this to a low value will encourge additional
+ Setting this to a low value will encourage additional
TCP traffic to the nameserver.
</para>
</listitem>
to the master file as soon as possible afterward; in the case
of the managed key database, this will usually occur within 30
seconds. So, whenever <command>named</command> is using
- automatic key maintenace, those two files can be expected to
+ automatic key maintenance, those two files can be expected to
exist in the working directory. (For this reason among others,
the working directory should be always be writable by
<command>named</command>.)
<listitem>
<para>
Zones configured for dynamic DNS may also use this
- option to allow varying levels of autonatic DNSSEC key
+ option to allow varying levels of automatic DNSSEC key
management. There are four possible settings:
</para>
<para>