2N/A - Copyright (C) 2004, 2005 Internet Systems Consortium, Inc. ("ISC") 2N/A - Copyright (C) 2000-2003 Internet Software Consortium. 2N/A - Permission to use, copy, modify, and distribute this software for any 2N/A - purpose with or without fee is hereby granted, provided that the above 2N/A - copyright notice and this permission notice appear in all copies. 2N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 2N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 2N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 2N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 2N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 2N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 2N/A - PERFORMANCE OF THIS SOFTWARE. 2N/A<
meta http-
equiv="Content-Type" content="text/html; charset=ISO-8859-1">
2N/A<
meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
2N/A<
link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
2N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
2N/A<
div class="navheader">
2N/A<
table width="100%" summary="Navigation header">
2N/A<
tr><
th colspan="3" align="center"><
span class="application">rndc</
span></
th></
tr>
2N/A<
td width="20%" align="left">
2N/A<
th width="60%" align="center">Manual pages</
th>
2N/A<
div class="refentry" lang="en">
2N/A<
div class="refnamediv">
2N/A<
p><
span class="application">rndc</
span> — name server control utility</
p>
2N/A<
div class="refsynopsisdiv">
2N/A<
div class="cmdsynopsis"><
p><
code class="command">rndc</
code> [<
code class="option">-b <
em class="replaceable"><
code>source-address</
code></
em></
code>] [<
code class="option">-c <
em class="replaceable"><
code>config-file</
code></
em></
code>] [<
code class="option">-k <
em class="replaceable"><
code>key-file</
code></
em></
code>] [<
code class="option">-s <
em class="replaceable"><
code>server</
code></
em></
code>] [<
code class="option">-p <
em class="replaceable"><
code>port</
code></
em></
code>] [<
code class="option">-V</
code>] [<
code class="option">-y <
em class="replaceable"><
code>key_id</
code></
em></
code>] {command}</
p></
div>
2N/A<
div class="refsect1" lang="en">
2N/A<
a name="id2585029"></
a><
h2>DESCRIPTION</
h2>
2N/A<
p><
span><
strong class="command">rndc</
strong></
span>
2N/A controls the operation of a name
2N/A server. It supersedes the <
span><
strong class="command">ndc</
strong></
span> utility
2N/A that was provided in old BIND releases. If
2N/A <
span><
strong class="command">rndc</
strong></
span> is invoked with no command line
2N/A options or arguments, it prints a short summary of the
2N/A supported commands and the available options and their
2N/A<
p><
span><
strong class="command">rndc</
strong></
span>
2N/A communicates with the name server
2N/A over a TCP connection, sending commands authenticated with
2N/A digital signatures. In the current versions of
2N/A <
span><
strong class="command">rndc</
strong></
span> and <
span><
strong class="command">named</
strong></
span> named
2N/A the only supported authentication algorithm is HMAC-MD5,
2N/A which uses a shared secret on each end of the connection.
2N/A This provides TSIG-style authentication for the command
2N/A request and the name server's response. All commands sent
2N/A over the channel must be signed by a key_id known to the
2N/A<
p><
span><
strong class="command">rndc</
strong></
span>
2N/A reads a configuration file to
2N/A determine how to contact the name server and decide what
2N/A algorithm and key it should use.
2N/A<
div class="refsect1" lang="en">
2N/A<
a name="id2585147"></
a><
h2>OPTIONS</
h2>
2N/A<
div class="variablelist"><
dl>
2N/A<
dt><
span class="term">-b <
em class="replaceable"><
code>source-address</
code></
em></
span></
dt>
2N/A Use <
em class="replaceable"><
code>source-address</
code></
em>
2N/A as the source address for the connection to the server.
2N/A Multiple instances are permitted to allow setting of both
2N/A the IPv4 and IPv6 source addresses.
2N/A<
dt><
span class="term">-c <
em class="replaceable"><
code>config-file</
code></
em></
span></
dt>
2N/A Use <
em class="replaceable"><
code>config-file</
code></
em>
2N/A as the configuration file instead of the default,
2N/A<
dt><
span class="term">-k <
em class="replaceable"><
code>key-file</
code></
em></
span></
dt>
2N/A Use <
em class="replaceable"><
code>key-file</
code></
em>
2N/A as the key file instead of the default,
2N/A commands sent to the server if the <
em class="replaceable"><
code>config-file</
code></
em>
2N/A<
dt><
span class="term">-s <
em class="replaceable"><
code>server</
code></
em></
span></
dt>
2N/A<
dd><
p><
em class="replaceable"><
code>server</
code></
em> is
2N/A the name or address of the server which matches a
2N/A server statement in the configuration file for
2N/A <
span><
strong class="command">rndc</
strong></
span>. If no server is supplied on
2N/A command line, the host named by the default-server clause
in the option statement of the configuration file will be
<
dt><
span class="term">-p <
em class="replaceable"><
code>port</
code></
em></
span></
dt>
Send commands to TCP port
<
em class="replaceable"><
code>port</
code></
em>
of BIND 9's default control channel port, 953.
<
dt><
span class="term">-V</
span></
dt>
<
dt><
span class="term">-y <
em class="replaceable"><
code>keyid</
code></
em></
span></
dt>
Use the key <
em class="replaceable"><
code>keyid</
code></
em>
from the configuration file.
<
em class="replaceable"><
code>keyid</
code></
em>
known by named with the same algorithm and secret string
in order for control message validation to succeed.
If no <
em class="replaceable"><
code>keyid</
code></
em>
is specified, <
span><
strong class="command">rndc</
strong></
span> 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
For the complete set of commands supported by <
span><
strong class="command">rndc</
strong></
span>,
see the BIND 9 Administrator Reference Manual or run
<
span><
strong class="command">rndc</
strong></
span> without arguments to see its help
<
div class="refsect1" lang="en">
<
a name="id2585571"></
a><
h2>LIMITATIONS</
h2>
<
p><
span><
strong class="command">rndc</
strong></
span>
does not yet support all the commands of
the BIND 8 <
span><
strong class="command">ndc</
strong></
span> utility.
There is currently no way to provide the shared secret for a
<
code class="option">key_id</
code> without using the configuration file.
Several error messages could be clearer.
<
div class="refsect1" lang="en">
<
a name="id2585602"></
a><
h2>SEE ALSO</
h2>
<
p><
span class="citerefentry"><
span class="refentrytitle">
rndc.conf</
span>(5)</
span>,
<
span class="citerefentry"><
span class="refentrytitle">named</
span>(8)</
span>,
<
span class="citerefentry"><
span class="refentrytitle">
named.conf</
span>(5)</
span>
<
span class="citerefentry"><
span class="refentrytitle">ndc</
span>(8)</
span>,
<
em class="citetitle">BIND 9 Administrator Reference Manual</
em>.
<
div class="refsect1" lang="en">
<
a name="id2585649"></
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">named</
span>�</
td>
<
td width="20%" align="center"><
a accesskey="h" href="Bv9ARM.html">Home</
a></
td>
<
td width="40%" align="right" valign="top">�<
code class="filename">
rndc.conf</
code></
td>