<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.0//EN"
"http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd">
-<!-- File: $Id: Bv9ARM-book.xml,v 1.137 2001/05/31 11:01:29 tale Exp $ -->
+<!-- File: $Id: Bv9ARM-book.xml,v 1.138 2001/05/31 22:39:52 bwelling Exp $ -->
<book>
<title>BIND 9 Administrator Reference Manual</title>
<command>rndc</command> will also look in
<filename>/var/run/named.key</filename> (or wherever
<varname>localstatedir</varname> was defined when
- the <acronym>BIND</acroynm> build was configured).
+ the <acronym>BIND</acronym> build was configured).
The <filename>named.key</filename> file is generated by
<command>named</command> as described in
- <xref linkend="controls_statement_definition_and_usage">.</para>
+ <xref linkend="controls_statement_definition_and_usage"/>.</para>
<para>The format of the configuration file is similar to
that of <filename>named.conf</filename>, but limited to
<command>inet</command> control channels have a <command>keys</command>
clause. The other is to have a <command>controls</command> statement
with no <command>inet</command> phrases it all. The latter will
- prevent the creation of any control channel</para>.
+ prevent the creation of any control channel.</para>
<para>The <filename>named.key</filename> feature was created to
ease the transition of systems from <acronym>BIND</acronym> 8,