168N/A - Copyright (C) 2004, 2005, 2007 Internet Systems Consortium, Inc. ("ISC") 168N/A - Copyright (C) 2000, 2001 Internet Software Consortium. 168N/A - Permission to use, copy, modify, and/or distribute this software for any 168N/A - purpose with or without fee is hereby granted, provided that the above 168N/A - copyright notice and this permission notice appear in all copies. 168N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 168N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 168N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 168N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 168N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 168N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 168N/A - PERFORMANCE OF THIS SOFTWARE. 168N/A<
meta http-
equiv="Content-Type" content="text/html; charset=ISO-8859-1">
168N/A<
meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
168N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><
div class="refentry" lang="en">
168N/A<
div class="refnamediv">
168N/A<
p><
span class="application">rndc</
span> — name server control utility</
p>
168N/A<
div class="refsynopsisdiv">
168N/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>
586N/A<
div class="refsect1" lang="en">
618N/A<
a name="id2543413"></
a><
h2>DESCRIPTION</
h2>
168N/A<
p><
span><
strong class="command">rndc</
strong></
span>
168N/A controls the operation of a name
844N/A server. It supersedes the <
span><
strong class="command">ndc</
strong></
span> utility
844N/A that was provided in old BIND releases. If
168N/A <
span><
strong class="command">rndc</
strong></
span> is invoked with no command line
1258N/A options or arguments, it prints a short summary of the
168N/A supported commands and the available options and their
168N/A<
p><
span><
strong class="command">rndc</
strong></
span>
168N/A communicates with the name server
519N/A over a TCP connection, sending commands authenticated with
519N/A digital signatures. In the current versions of
168N/A <
span><
strong class="command">rndc</
strong></
span> and <
span><
strong class="command">named</
strong></
span>,
168N/A the only supported authentication algorithm is HMAC-MD5,
168N/A which uses a shared secret on each end of the connection.
168N/A This provides TSIG-style authentication for the command
168N/A request and the name server's response. All commands sent
168N/A over the channel must be signed by a key_id known to the
168N/A<
p><
span><
strong class="command">rndc</
strong></
span>
168N/A reads a configuration file to
168N/A determine how to contact the name server and decide what
168N/A algorithm and key it should use.
168N/A<
div class="refsect1" lang="en">
501N/A<
a name="id2543448"></
a><
h2>OPTIONS</
h2>
168N/A<
div class="variablelist"><
dl>
168N/A<
dt><
span class="term">-b <
em class="replaceable"><
code>source-address</
code></
em></
span></
dt>
168N/A Use <
em class="replaceable"><
code>source-address</
code></
em>
168N/A as the source address for the connection to the server.
485N/A Multiple instances are permitted to allow setting of both
485N/A the IPv4 and IPv6 source addresses.
485N/A<
dt><
span class="term">-c <
em class="replaceable"><
code>config-file</
code></
em></
span></
dt>
168N/A Use <
em class="replaceable"><
code>config-file</
code></
em>
206N/A as the configuration file instead of the default,
168N/A<
dt><
span class="term">-k <
em class="replaceable"><
code>key-file</
code></
em></
span></
dt>
577N/A Use <
em class="replaceable"><
code>key-file</
code></
em>
277N/A as the key file instead of the default,
168N/A commands sent to the server if the <
em class="replaceable"><
code>config-file</
code></
em>
168N/A<
dt><
span class="term">-s <
em class="replaceable"><
code>server</
code></
em></
span></
dt>
168N/A<
dd><
p><
em class="replaceable"><
code>server</
code></
em> is
168N/A the name or address of the server which matches a
168N/A server statement in the configuration file for
168N/A <
span><
strong class="command">rndc</
strong></
span>. If no server is supplied on the
168N/A command line, the host named by the default-server clause
168N/A in the options statement of the <
span><
strong class="command">rndc</
strong></
span>
181N/A configuration file will be used.
168N/A<
dt><
span class="term">-p <
em class="replaceable"><
code>port</
code></
em></
span></
dt>
168N/A Send commands to TCP port
168N/A <
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>key_id</
code></
em></
span></
dt>
Use the key <
em class="replaceable"><
code>key_id</
code></
em>
from the configuration file.
<
em class="replaceable"><
code>key_id</
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>key_id</
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="id2543656"></
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="id2543683"></
a><
h2>SEE ALSO</
h2>
<
p><
span class="citerefentry"><
span class="refentrytitle">
rndc.conf</
span>(5)</
span>,
<
span class="citerefentry"><
span class="refentrytitle">rndc-confgen</
span>(8)</
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="id2543738"></
a><
h2>AUTHOR</
h2>
<
p><
span class="corpauthor">Internet Systems Consortium</
span>