1 .\" Copyright (C) 2004, 2005, 2007 Internet Systems Consortium, Inc. ("ISC")
2 .\" Copyright (C) 2000, 2001 Internet Software Consortium.
4 .\" Permission to use, copy, modify, and distribute this software for any
5 .\" purpose with or without fee is hereby granted, provided that the above
6 .\" copyright notice and this permission notice appear in all copies.
8 .\" THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
9 .\" REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
10 .\" AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
11 .\" INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
12 .\" LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
13 .\" OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
14 .\" PERFORMANCE OF THIS SOFTWARE.
16 .\" $Id: rndc.conf.5,v 1.23.18.15 2007/05/09 13:35:47 marka Exp $
20 .\" Title: \fIrndc.conf\fR
22 .\" Generator: DocBook XSL Stylesheets v1.71.1 <http://docbook.sf.net/>
23 .\" Date: June 30, 2000
27 .TH "\fIRNDC.CONF\fR" "5" "June 30, 2000" "BIND9" "BIND9"
28 .\" disable hyphenation
30 .\" disable justification (adjust text to left margin only)
33 rndc.conf \- rndc configuration file
40 is the configuration file for
41 \fBrndc\fR, the BIND 9 name server control utility. This file has a similar structure and syntax to
42 \fInamed.conf\fR. Statements are enclosed in braces and terminated with a semi\-colon. Clauses in the statements are also semi\-colon terminated. The usual comment styles are supported:
46 C++ style: // to end of line
48 Unix style: # to end of line
52 \fInamed.conf\fR. The file uses three statements: an options statement, a server statement and a key statement.
56 statement contains five clauses. The
58 clause is followed by the name or address of a name server. This host will be used when no name server is given as an argument to
61 clause is followed by the name of a key which is identified by a
65 is provided on the rndc command line, and no
67 clause is found in a matching
69 statement, this default key will be used to authenticate the server's commands and responses. The
71 clause is followed by the port to connect to on the remote name server. If no
73 option is provided on the rndc command line, and no
75 clause is found in a matching
77 statement, this default port will be used to connect. The
78 \fBdefault\-source\-address\fR
80 \fBdefault\-source\-address\-v6\fR
81 clauses which can be used to set the IPv4 and IPv6 source addresses respectively.
85 keyword, the server statement includes a string which is the hostname or address for a name server. The statement has three possible clauses:
89 \fBaddresses\fR. The key name must match the name of a key statement in the file. The port number specifies the port to connect to. If an
91 clause is supplied these addresses will be used instead of the server name. Each address can take an optional port. If an
94 \fBsource\-address\-v6\fR
95 of supplied then these will be used to specify the IPv4 and IPv6 source addresses respectively.
99 statement begins with an identifying string, the name of the key. The statement has two clauses.
101 identifies the encryption algorithm for
103 to use; currently only HMAC\-MD5 is supported. This is followed by a secret clause which contains the base\-64 encoding of the algorithm's encryption key. The base\-64 string is enclosed in double quotes.
105 There are two common ways to generate the base\-64 string for the secret. The BIND 9 program
107 can be used to generate a random key, or the
109 program, also known as
110 \fBmimencode\fR, can be used to generate a base\-64 string from known input.
112 does not ship with BIND 9 but is available on many systems. See the EXAMPLE section for sample command lines for each.
118 default\-server localhost;
119 default\-key samplekey;
138 addresses { localhost port 5353; };
148 secret "6FMfj43Osz4lyb24OIe2iGEz9lf1llJO+lz";
158 secret "R3HI8P6BKw9ZwXwN3VZKuQ==";
164 In the above example,
166 will by default use the server at localhost (127.0.0.1) and the key called samplekey. Commands to the localhost server will use the samplekey key, which must also be defined in the server's configuration file with the same name and secret. The key statement indicates that samplekey uses the HMAC\-MD5 algorithm and its secret clause contains the base\-64 encoding of the HMAC\-MD5 secret enclosed in double quotes.
169 \fBrndc \-s testserver\fR
172 will connect to server on localhost port 5353 using the key testkey.
174 To generate a random secret with
181 file, including the randomly generated key, will be written to the standard output. Commented\-out
189 To generate a base\-64 secret with
192 \fBecho "known plaintext for a secret" | mmencode\fR
193 .SH "NAME SERVER CONFIGURATION"
195 The name server must be configured to accept rndc connections and to recognize the key specified in the
197 file, using the controls statement in
198 \fInamed.conf\fR. See the sections on the
200 statement in the BIND 9 Administrator Reference Manual for details.
204 \fBrndc\-confgen\fR(8),
206 BIND 9 Administrator Reference Manual.
209 Internet Systems Consortium
211 Copyright \(co 2004, 2005, 2007 Internet Systems Consortium, Inc. ("ISC")
213 Copyright \(co 2000, 2001 Internet Software Consortium.