363N/A<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">

363N/A

363N/A

7161N/A<refentry>

7161N/A <refentryinfo>

7161N/A <date>June 30, 2000</date>

363N/A </refentryinfo>

363N/A

363N/A <refmeta>

2369N/A <refentrytitle><application>rndc</application></refentrytitle>

2369N/A <manvolnum>8</manvolnum>

363N/A <refmiscinfo>BIND9</refmiscinfo>

363N/A </refmeta>

364N/A

363N/A <refnamediv>

363N/A <refname><application>rndc</application></refname>

7161N/A <refpurpose>name server control utility</refpurpose>

2369N/A </refnamediv>

363N/A

844N/A <refsynopsisdiv>

7161N/A <cmdsynopsis>

363N/A <command>rndc</command>

3182N/A <arg><option>-b <replaceable class="parameter">source-address</replaceable></option></arg>

363N/A <arg><option>-c <replaceable class="parameter">config-file</replaceable></option></arg>

3996N/A <arg><option>-k <replaceable class="parameter">key-file</replaceable></option></arg>

3996N/A <arg><option>-s <replaceable class="parameter">server</replaceable></option></arg>

363N/A <arg><option>-p <replaceable class="parameter">port</replaceable></option></arg>

695N/A <arg><option>-V</option></arg>

365N/A <arg><option>-y <replaceable class="parameter">key_id</replaceable></option></arg>

363N/A <arg choice="req">command</arg>

363N/A </cmdsynopsis>

363N/A </refsynopsisdiv>

363N/A

363N/A <refsect1>

2369N/A <title>DESCRIPTION</title>

363N/A <para>

363N/A <command>rndc</command> controls the operation of a name

363N/A server. It supersedes the <command>ndc</command> utility

695N/A that was provided in old BIND releases. If

363N/A <command>rndc</command> is invoked with no command line

363N/A options or arguments, it prints a short summary of the

363N/A supported commands and the available options and their

7161N/A arguments.

814N/A </para>

363N/A <para>

7161N/A <command>rndc</command> communicates with the name server

791N/A over a TCP connection, sending commands authenticated with

791N/A digital signatures. In the current versions of

791N/A <command>rndc</command> and <command>named</command> named

791N/A the only supported authentication algorithm is HMAC-MD5,

363N/A which uses a shared secret on each end of the connection.

3091N/A This provides TSIG-style authentication for the command

3091N/A request and the name server's response. All commands sent

3091N/A over the channel must be signed by a key_id known to the

3091N/A server.

363N/A </para>

7161N/A <para>

363N/A <command>rndc</command> reads a configuration file to

363N/A determine how to contact the name server and decide what

363N/A algorithm and key it should use.

363N/A </para>

363N/A </refsect1>

363N/A

363N/A <refsect1>

363N/A <title>OPTIONS</title>

363N/A

363N/A <variablelist>

363N/A <varlistentry>

2369N/A <term>-b <replaceable class="parameter">source-address</replaceable></term>

2369N/A <listitem>

2369N/A <para>

2369N/A Use <replaceable class="parameter">source-address</replaceable>

2369N/A as the source address for the connection to the server.

2369N/A Multiple instances are permitted to allow setting of both

2369N/A the IPv4 and IPv6 source addresses.

363N/A </para>

2369N/A </listitem>

2369N/A </varlistentry>

363N/A

2369N/A <varlistentry>

363N/A <term>-c <replaceable class="parameter">config-file</replaceable></term>

363N/A <listitem>

363N/A <para>

363N/A Use <replaceable class="parameter">config-file</replaceable>

7161N/A as the configuration file instead of the default,

7161N/A <filename>/etc/rndc.conf</filename>.

7161N/A </para>

7161N/A </listitem>

363N/A </varlistentry>

695N/A

695N/A <varlistentry>

363N/A <term>-k <replaceable class="parameter">key-file</replaceable></term>

363N/A <listitem>

363N/A <para>

363N/A Use <replaceable class="parameter">key-file</replaceable>

363N/A as the key file instead of the default,

363N/A <filename>/etc/rndc.key</filename>. The key in

7161N/A <filename>/etc/rndc.key</filename> will be used to authenticate

7161N/A commands sent to the server if the <replaceable class="parameter">config-file</replaceable>

363N/A does not exist.

363N/A </para>

363N/A </listitem>

363N/A </varlistentry>

695N/A

363N/A <varlistentry>

363N/A <term>-s <replaceable class="parameter">server</replaceable></term>

363N/A <listitem>

363N/A <para>

363N/A <replaceable class="parameter">server</replaceable> is

363N/A the name or address of the server which matches a

7161N/A server statement in the configuration file for

2887N/A <command>rndc</command>. If no server is supplied on the

363N/A command line, the host named by the default-server clause

363N/A in the option statement of the configuration file will be

363N/A used.

363N/A </para>

363N/A </listitem>

7161N/A </varlistentry>

363N/A

7161N/A <varlistentry>

7161N/A <term>-p <replaceable class="parameter">port</replaceable></term>

<listitem>

<para>

Send commands to TCP port

<replaceable class="parameter">port</replaceable> instead

of BIND 9's default control channel port, 953.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-V</term>

<listitem>

<para>

Enable verbose logging.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-y <replaceable class="parameter">keyid</replaceable></term>

<listitem>

<para>

Use the key <replaceable class="parameter">keyid</replaceable>

from the configuration file.

<replaceable class="parameter">keyid</replaceable> must be

known by named with the same algorithm and secret string

in order for control message validation to succeed.

If no <replaceable class="parameter">keyid</replaceable>

is specified, <command>rndc</command> 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

or write access.

</para>

</listitem>

</varlistentry>

</variablelist>

<para>

For the complete set of commands supported by <command>rndc</command>,

see the BIND 9 Administrator Reference Manual or run

<command>rndc</command> without arguments to see its help message.

</para>

</refsect1>

<refsect1>

<title>LIMITATIONS</title>

<para>

<command>rndc</command> does not yet support all the commands of

the BIND 8 <command>ndc</command> utility.

</para>

<para>

There is currently no way to provide the shared secret for a

<option>key_id</option> without using the configuration file.

</para>

<para>

Several error messages could be clearer.

</para>

</refsect1>

<refsect1>

<title>SEE ALSO</title>

<para>

<citerefentry>

<refentrytitle>rndc.conf</refentrytitle>

<manvolnum>5</manvolnum>

</citerefentry>,

<citerefentry>

<refentrytitle>named</refentrytitle>

<manvolnum>8</manvolnum>

</citerefentry>,

<citerefentry>

<refentrytitle>named.conf</refentrytitle>

<manvolnum>5</manvolnum>

</citerefentry>

<citerefentry>

<refentrytitle>ndc</refentrytitle>

<manvolnum>8</manvolnum>

</citerefentry>,

<citetitle>BIND 9 Administrator Reference Manual</citetitle>.

</para>

</refsect1>

<refsect1>

<title>AUTHOR</title>

<para>

<corpauthor>Internet Systems Consortium</corpauthor>

</para>

</refsect1>

</refentry>