controls the operation of a name server. It supersedes the
utility that was provided in old BIND releases. If
is invoked with no command line options or arguments, it prints a short summary of the supported commands and the available options and their arguments.
communicates with the name server over a TCP connection, sending commands authenticated with digital signatures. In the current versions of
named, the only supported authentication algorithm is HMAC-MD5, which uses a shared secret on each end of the connection. This provides TSIG-style authentication for the command request and the name server's response. All commands sent over the channel must be signed by a key_id known to the server.
reads a configuration file to determine how to contact the name server and decide what algorithm and key it should use.
as the source address for the connection to the server. Multiple instances are permitted to allow setting of both the IPv4 and IPv6 source addresses.
as the configuration file instead of the default,
as the key file instead of the default,
/etc/rndc.key. The key in
will be used to authenticate commands sent to the server if the
does not exist.
is the name or address of the server which matches a server statement in the configuration file for
rndc. If no server is supplied on the command line, the host named by the default-server clause in the options statement of the
configuration file will be used.
Send commands to TCP port
instead of BIND 9's default control channel port, 953.
Enable verbose logging.
Use the key
from the configuration file.
must be known by named with the same algorithm and secret string in order for control message validation to succeed. If no
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.
For the complete set of commands supported by
rndc, see the BIND 9 Administrator Reference Manual or run
without arguments to see its help message.
does not yet support all the commands of the BIND 8
There is currently no way to provide the shared secret for a
without using the configuration file.
Several error messages could be clearer.
BIND 9 Administrator Reference Manual.
Internet Systems Consortium
Copyright © 2004, 2005, 2007 Internet Systems Consortium, Inc. ("ISC")
Copyright © 2000, 2001 Internet Software Consortium.
- SEE ALSO
This document was created by
using the manual pages.
Time: 04:17:50 GMT, September 24, 2010