]> git.ipfire.org Git - thirdparty/bind9.git/commitdiff
update from jeremy
authorMark Andrews <marka@isc.org>
Thu, 31 May 2007 22:33:12 +0000 (22:33 +0000)
committerMark Andrews <marka@isc.org>
Thu, 31 May 2007 22:33:12 +0000 (22:33 +0000)
bin/rndc/rndc.docbook

index 5d63f64b39ec8d7bbd926e00ef6d57dc62534156..77d2f2666aee6882cc88fde8cbfdaa730186c4fe 100644 (file)
@@ -18,7 +18,7 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-<!-- $Id: rndc.docbook,v 1.7.2.7 2007/05/09 02:11:44 marka Exp $ -->
+<!-- $Id: rndc.docbook,v 1.7.2.8 2007/05/31 22:33:12 marka Exp $ -->
 
 <refentry>
   <refentryinfo>
@@ -78,7 +78,7 @@
         <command>rndc</command> communicates with the name server
        over a TCP connection, sending commands authenticated with
        digital signatures.  In the current versions of
-       <command>rndc</command> and <command>named</command> named
+      <command>rndc</command> and <command>named</command>,
         the only supported authentication algorithm is HMAC-MD5,
        which uses a shared secret on each end of the connection.
        This provides TSIG-style authentication for the command
       </varlistentry>
 
       <varlistentry>
-        <term>-y <replaceable class="parameter">keyid</replaceable></term>
+        <term>-y <replaceable class="parameter">key_id</replaceable></term>
        <listitem>
          <para>
-              Use the key <replaceable class="parameter">keyid</replaceable>
+              Use the key <replaceable class="parameter">key_id</replaceable>
               from the configuration file.
-              <replaceable class="parameter">keyid</replaceable> must be
+              <replaceable class="parameter">key_id</replaceable> must be
               known by named with the same algorithm and secret string
               in order for control message validation to succeed.
-              If no <replaceable class="parameter">keyid</replaceable>
+              If no <replaceable class="parameter">key_id</replaceable>
               is specified, <command>rndc</command> will first look
               for a key clause in the server statement of the server
               being used, or if no server statement is present for that