mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-29 05:28:00 +00:00
Code Issues Releases Wiki Activity

regen

Browse Source
This commit is contained in:
Mark Andrews 2007-05-31 23:28:55 +00:00
parent 122c58bd11
commit c247e3f281
3 changed files with 18 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
bin/rndc/rndc.8
View File

@ -13,7 +13,7 @@
.\" OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR .\" OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
.\" PERFORMANCE OF THIS SOFTWARE. .\" PERFORMANCE OF THIS SOFTWARE.
.\" .\"
.\" $Id: rndc.8,v 1.39 2007/05/09 03:33:51 marka Exp $ .\" $Id: rndc.8,v 1.40 2007/05/31 23:28:55 marka Exp $
.\" .\"
.hy 0 .hy 0
.ad l .ad l
@ -47,8 +47,7 @@ is invoked with no command line options or arguments, it prints a short summary
communicates with the name server over a TCP connection, sending commands authenticated with digital signatures. In the current versions of communicates with the name server over a TCP connection, sending commands authenticated with digital signatures. In the current versions of
\fBrndc\fR \fBrndc\fR
and and
\fBnamed\fR \fBnamed\fR, 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 request and the name server's response. All commands sent over the channel must be signed by a key_id known to the server.
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 request and the name server's response. All commands sent over the channel must be signed by a key_id known to the server.
.PP .PP
\fBrndc\fR \fBrndc\fR
reads a configuration file to determine how to contact the name server and decide what algorithm and key it should use. reads a configuration file to determine how to contact the name server and decide what algorithm and key it should use.
@ -100,14 +99,14 @@ instead of BIND 9's default control channel port, 953.
Enable verbose logging. Enable verbose logging.
.RE .RE
.PP .PP
\-y \fIkeyid\fR \-y \fIkey_id\fR
.RS 4 .RS 4
Use the key Use the key
\fIkeyid\fR \fIkey_id\fR
from the configuration file. from the configuration file.
\fIkeyid\fR \fIkey_id\fR
must be known by named with the same algorithm and secret string in order for control message validation to succeed. If no must be known by named with the same algorithm and secret string in order for control message validation to succeed. If no
\fIkeyid\fR \fIkey_id\fR
is specified, is specified,
\fBrndc\fR \fBrndc\fR
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 host, then the default\-key clause of the options statement. Note that the configuration file contains shared secrets which are used to send authenticated control commands to name servers. It should therefore not have general read or write access. 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 host, then the default\-key clause of the options statement. Note that the configuration file contains shared secrets which are used to send authenticated control commands to name servers. It should therefore not have general read or write access.

12
bin/rndc/rndc.html
View File

@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE. - PERFORMANCE OF THIS SOFTWARE.
--> -->
<!-- $Id: rndc.html,v 1.28 2007/05/09 03:33:51 marka Exp $ --> <!-- $Id: rndc.html,v 1.29 2007/05/31 23:28:55 marka Exp $ -->
<html> <html>
<head> <head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
@ -46,7 +46,7 @@
communicates with the name server communicates with the name server
over a TCP connection, sending commands authenticated with over a TCP connection, sending commands authenticated with
digital signatures. In the current versions of digital signatures. In the current versions of
<span><strong class="command">rndc</strong></span> and <span><strong class="command">named</strong></span> named <span><strong class="command">rndc</strong></span> and <span><strong class="command">named</strong></span>,
the only supported authentication algorithm is HMAC-MD5, the only supported authentication algorithm is HMAC-MD5,
which uses a shared secret on each end of the connection. which uses a shared secret on each end of the connection.
This provides TSIG-style authentication for the command This provides TSIG-style authentication for the command
@ -107,15 +107,15 @@
<dd><p> <dd><p>
Enable verbose logging. Enable verbose logging.
</p></dd> </p></dd>
<dt><span class="term">-y <em class="replaceable"><code>keyid</code></em></span></dt> <dt><span class="term">-y <em class="replaceable"><code>key_id</code></em></span></dt>
<dd><p> <dd><p>
Use the key <em class="replaceable"><code>keyid</code></em> Use the key <em class="replaceable"><code>key_id</code></em>
from the configuration file. from the configuration file.
<em class="replaceable"><code>keyid</code></em> <em class="replaceable"><code>key_id</code></em>
must be must be
known by named with the same algorithm and secret string known by named with the same algorithm and secret string
in order for control message validation to succeed. in order for control message validation to succeed.
If no <em class="replaceable"><code>keyid</code></em> If no <em class="replaceable"><code>key_id</code></em>
is specified, <span><strong class="command">rndc</strong></span> will first look is specified, <span><strong class="command">rndc</strong></span> will first look
for a key clause in the server statement of the server for a key clause in the server statement of the server
being used, or if no server statement is present for that being used, or if no server statement is present for that

12
doc/arm/man.rndc.html
View File

@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE. - PERFORMANCE OF THIS SOFTWARE.
--> -->
<!-- $Id: man.rndc.html,v 1.52 2007/05/30 02:30:15 marka Exp $ --> <!-- $Id: man.rndc.html,v 1.53 2007/05/31 23:28:55 marka Exp $ -->
<html> <html>
<head> <head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
@ -64,7 +64,7 @@
communicates with the name server communicates with the name server
over a TCP connection, sending commands authenticated with over a TCP connection, sending commands authenticated with
digital signatures. In the current versions of digital signatures. In the current versions of
<span><strong class="command">rndc</strong></span> and <span><strong class="command">named</strong></span> named <span><strong class="command">rndc</strong></span> and <span><strong class="command">named</strong></span>,
the only supported authentication algorithm is HMAC-MD5, the only supported authentication algorithm is HMAC-MD5,
which uses a shared secret on each end of the connection. which uses a shared secret on each end of the connection.
This provides TSIG-style authentication for the command This provides TSIG-style authentication for the command
@ -125,15 +125,15 @@
<dd><p> <dd><p>
Enable verbose logging. Enable verbose logging.
</p></dd> </p></dd>
<dt><span class="term">-y <em class="replaceable"><code>keyid</code></em></span></dt> <dt><span class="term">-y <em class="replaceable"><code>key_id</code></em></span></dt>
<dd><p> <dd><p>
Use the key <em class="replaceable"><code>keyid</code></em> Use the key <em class="replaceable"><code>key_id</code></em>
from the configuration file. from the configuration file.
<em class="replaceable"><code>keyid</code></em> <em class="replaceable"><code>key_id</code></em>
must be must be
known by named with the same algorithm and secret string known by named with the same algorithm and secret string
in order for control message validation to succeed. in order for control message validation to succeed.
If no <em class="replaceable"><code>keyid</code></em> If no <em class="replaceable"><code>key_id</code></em>
is specified, <span><strong class="command">rndc</strong></span> will first look is specified, <span><strong class="command">rndc</strong></span> will first look
for a key clause in the server statement of the server for a key clause in the server statement of the server
being used, or if no server statement is present for that being used, or if no server statement is present for that