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