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