From: Mark Andrews Date: Thu, 31 May 2007 22:28:35 +0000 (+0000) Subject: update from jeremy X-Git-Tag: v9.5.0a6~44 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=122c58bd11790c7576cdb1c6fd8e4439d0d7f7a5;p=thirdparty%2Fbind9.git update from jeremy --- diff --git a/bin/rndc/rndc.docbook b/bin/rndc/rndc.docbook index d576b7060fe..35311a3b833 100644 --- a/bin/rndc/rndc.docbook +++ b/bin/rndc/rndc.docbook @@ -18,7 +18,7 @@ - PERFORMANCE OF THIS SOFTWARE. --> - + June 30, 2000 @@ -78,7 +78,7 @@ communicates with the name server over a TCP connection, sending commands authenticated with digital signatures. In the current versions of - rndc and named named + rndc and named, 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 @@ -172,16 +172,16 @@ - -y keyid + -y key_id - Use the key keyid + Use the key key_id from the configuration file. - keyid + key_id must be known by named with the same algorithm and secret string in order for control message validation to succeed. - If no keyid + If no key_id is specified, rndc 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