2362N/A - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC") 0N/A - Copyright (C) 2000-2003 Internet Software Consortium. 0N/A - Permission to use, copy, modify, and distribute this software for any 0N/A - purpose with or without fee is hereby granted, provided that the above 2362N/A - copyright notice and this permission notice appear in all copies. 2362N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 0N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 0N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 0N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 0N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 0N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 0N/A - PERFORMANCE OF THIS SOFTWARE. 0N/A<
meta http-
equiv="Content-Type" content="text/html; charset=ISO-8859-1">
2362N/A<
meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
2362N/A<
link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
0N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
0N/A<
div class="navheader">
0N/A<
table width="100%" summary="Navigation header">
0N/A<
tr><
th colspan="3" align="center"><
code class="filename">
rndc.conf</
code></
th></
tr>
0N/A<
td width="20%" align="left">
0N/A<
th width="60%" align="center">Manual pages</
th>
0N/A<
div class="refentry" lang="en">
0N/A<
div class="refnamediv">
0N/A<
p><
code class="filename">
rndc.conf</
code> — rndc configuration file</
p>
0N/A<
div class="refsynopsisdiv">
0N/A<
div class="cmdsynopsis"><
p><
code class="command">
rndc.conf</
code> </
p></
div>
0N/A<
div class="refsect1" lang="en">
0N/A<
a name="id2604317"></
a><
h2>DESCRIPTION</
h2>
0N/A<
p><
code class="filename">
rndc.conf</
code> is the configuration file
0N/A for <
span><
strong class="command">rndc</
strong></
span>, the BIND 9 name server control
0N/A utility. This file has a similar structure and syntax to
0N/A <
code class="filename">
named.conf</
code>. Statements are enclosed
0N/A in braces and terminated with a semi-colon. Clauses in
0N/A the statements are also semi-colon terminated. The usual
0N/A comment styles are supported:
0N/A C++ style: // to end of line
0N/A Unix style: # to end of line
0N/A<
p><
code class="filename">
rndc.conf</
code> is much simpler than
0N/A statements: an options statement, a server statement
0N/A and a key statement.
0N/A The <
code class="option">options</
code> statement contains five clauses.
0N/A The <
code class="option">default-server</
code> clause is followed by the
0N/A name or address of a name server. This host will be used when
0N/A no name server is given as an argument to
0N/A <
span><
strong class="command">rndc</
strong></
span>. The <
code class="option">default-key</
code>
0N/A clause is followed by the name of a key which is identified by
0N/A a <
code class="option">key</
code> statement. If no
0N/A <
code class="option">keyid</
code> is provided on the rndc command line,
0N/A and no <
code class="option">key</
code> clause is found in a matching
0N/A <
code class="option">server</
code> statement, this default key will be
0N/A used to authenticate the server's commands and responses. The
0N/A <
code class="option">default-port</
code> clause is followed by the port
0N/A to connect to on the remote name server. If no
0N/A <
code class="option">port</
code> option is provided on the rndc command
0N/A line, and no <
code class="option">port</
code> clause is found in a
0N/A matching <
code class="option">server</
code> statement, this default port
0N/A will be used to connect.
0N/A The <
code class="option">default-source-address</
code> and
0N/A <
code class="option">default-source-address-v6</
code> clauses which
0N/A can be used to set the IPv4 and IPv6 source addresses
0N/A After the <
code class="option">server</
code> keyword, the server
0N/A statement includes a string which is the hostname or address
0N/A for a name server. The statement has three possible clauses:
0N/A <
code class="option">key</
code>, <
code class="option">port</
code> and
0N/A <
code class="option">addresses</
code>. The key name must match the
0N/A name of a key statement in the file. The port number
0N/A specifies the port to connect to. If an <
code class="option">addresses</
code>
0N/A clause is supplied these addresses will be used instead of
0N/A the server name. Each address can take a optional port.
0N/A If an <
code class="option">source-address</
code> or <
code class="option">source-address-v6</
code>
0N/A of supplied then these will be used to specify the IPv4 and IPv6
0N/A source addresses respectively.
0N/A The <
code class="option">key</
code> statement begins with an identifying
0N/A string, the name of the key. The statement has two clauses.
0N/A <
code class="option">algorithm</
code> identifies the encryption algorithm
0N/A for <
span><
strong class="command">rndc</
strong></
span> to use; currently only HMAC-MD5
0N/A supported. This is followed by a secret clause which contains
0N/A the base-64 encoding of the algorithm's encryption key. The
0N/A base-64 string is enclosed in double quotes.
0N/A There are two common ways to generate the base-64 string for the
0N/A secret. The BIND 9 program <
span><
strong class="command">rndc-confgen</
strong></
span>
0N/A be used to generate a random key, or the
0N/A <
span><
strong class="command">mmencode</
strong></
span> program, also known as
0N/A <
span><
strong class="command">mimencode</
strong></
span>, can be used to generate a
0N/A string from known input. <
span><
strong class="command">mmencode</
strong></
span> does
0N/A ship with BIND 9 but is available on many systems. See the
0N/A EXAMPLE section for sample command lines for each.
0N/A<
div class="refsect1" lang="en">
0N/A<
a name="id2604489"></
a><
h2>EXAMPLE</
h2>
0N/A<
pre class="programlisting">
0N/A default-server localhost;
0N/A default-key samplekey;
0N/A<
pre class="programlisting">
0N/A<
pre class="programlisting">
0N/A addresses { localhost port 5353; };
0N/A<
pre class="programlisting">
0N/A secret "6FMfj43Osz4lyb24OIe2iGEz9lf1llJO+lz";
0N/A<
pre class="programlisting">
secret "R3HI8P6BKw9ZwXwN3VZKuQ==";
In the above example, <
span><
strong class="command">rndc</
strong></
span> will by
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.
If <
span><
strong class="command">rndc -s testserver</
strong></
span> is used then <
span><
strong class="command">rndc</
strong></
span> will
connect to server on localhost port 5353 using the key testkey.
To generate a random secret with <
span><
strong class="command">rndc-confgen</
strong></
span>:
<
p><
strong class="userinput"><
code>rndc-confgen</
code></
strong>
A complete <
code class="filename">
rndc.conf</
code> file, including
randomly generated key, will be written to the standard
output. Commented out <
code class="option">key</
code> and
<
code class="option">controls</
code> statements for
<
code class="filename">
named.conf</
code> are also printed.
To generate a base-64 secret with <
span><
strong class="command">mmencode</
strong></
span>:
<
p><
strong class="userinput"><
code>echo "known plaintext for a secret" | mmencode</
code></
strong>
<
div class="refsect1" lang="en">
<
a name="id2604816"></
a><
h2>NAME SERVER CONFIGURATION</
h2>
The name server must be configured to accept rndc connections and
to recognize the key specified in the <
code class="filename">
rndc.conf</
code>
file, using the controls statement in <
code class="filename">
named.conf</
code>.
See the sections on the <
code class="option">controls</
code> statement in the
BIND 9 Administrator Reference Manual for details.
<
div class="refsect1" lang="en">
<
a name="id2604841"></
a><
h2>SEE ALSO</
h2>
<
p><
span class="citerefentry"><
span class="refentrytitle">rndc</
span>(8)</
span>,
<
span class="citerefentry"><
span class="refentrytitle">rndc-confgen</
span>(8)</
span>,
<
span class="citerefentry"><
span class="refentrytitle">mmencode</
span>(1)</
span>,
<
em class="citetitle">BIND 9 Administrator Reference Manual</
em>.
<
div class="refsect1" lang="en">
<
a name="id2604880"></
a><
h2>AUTHOR</
h2>
<
p><
span class="corpauthor">Internet Systems Consortium</
span>
<
table width="100%" summary="Navigation footer">
<
td width="40%" align="left">
<
td width="20%" align="center"><
a accesskey="u" href="Bv9ARM.ch10.html">Up</
a></
td>
<
td width="40%" align="left" valign="top"><
span class="application">rndc</
span>�</
td>
<
td width="20%" align="center"><
a accesskey="h" href="Bv9ARM.html">Home</
a></
td>
<
td width="40%" align="right" valign="top">�<
span class="application">rndc-confgen</
span></
td>