rndc(1)rndc(1)NAMErndc - name server control utility
SYNOPSIS
config-file] keyfile] port] server] key_id] [command]
DESCRIPTION
The command allows the system administrator to control the operation of
a name server. If is invoked without any command line options or oper‐
ands, it prints a short summary of the supported commands and the
available options.
communicates with the name server over a TCP connection, sending com‐
mands authenticated with digital signatures. In the current versions
of the only supported encryption 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 its configuration file (the default is to determine how to con‐
tact the name server and to decide what algorithm and keys it should
use.
Options
Specify an alternate configuration file.
The default configuration file is
Use keyfile as the key file instead of the default, The key in
the key file is used to authenticate commands sent to the
server if the configuration file does not exist.
Send commands to TCP port number
port on the system running the name server. The BIND 9
default control channel port is 953.
Specify the server on which this command is run.
server is the name or address of a server that matches a
statement in the configuration file. The default is the host
named by the clause in the statement of the configuration
file.
Provide debugging information.
This option is primarily of interest to the BIND 9 develop‐
ers.
Use the key_id from the configuration file. key_id must also be
known to with the same and string for control message valida‐
tion to succeed. If the option is not specified, first looks
for a clause in the statement of the configuration file. If
there is no statement for that host, then it uses the clause
of the statement of the configuration file.
Operands
command One of the following:
Dump the current contents of the cache into the file defined
by the
directive of the statement in the configura‐
tion file. For details and defaults, see
named.conf(4).
Flush all the server's caches.
Flush the server's cache for a view.
Flush the given name from the server's caches.
Retransfer the given zone without checking serial number.
See also the command.
Stop the server without saving pending updates.
See also the command.
Stop the server without saving pending updates,
reporting the process ID to standard output.
See also the command.
Set the debugging level to 0.
See also the command.
Toggle query logging.
Reload configuration file and new zones only.
Dump the queries that are currently recursing, into the file
Schedule immediate zone maintenance for the given zone.
Reload configuration file and zones.
Reload the given zone.
Retransfer a single zone without checking serial number.
Write server statistics to the statistics file as specified
by
the clause of the statement in the configura‐
tion file. For details and defaults, see
named.conf(4).
Display the status of the server.
Save pending updates to master files and stop the server.
See also the command.
Save pending updates to master files and stop the server,
reporting the process ID to standard output.
See also the command.
Enable updates to a frozen dynamic zone and reload it.
See also the command.
Increment the debugging level by 1.
See also the command.
Set the debugging level to
level. See also the command.
WARNINGS
The configuration file for contains shared secrets that are used to
send authenticated control commands to name servers. Therefore, it
should not have general read or write access.
does not yet support all the commands of the BIND 8 utility.
There is currently no way to provide the shared secret for a key_id
without using the configuration file.
AUTHOR
was developed by the Internet Systems Consortium (ISC).
FILES
Default configuration file for
Default configuration file for
Alternate default configuration file for
SEE ALSOdnssec-keygen(1)rndc-confgen(1)named(1M), named.conf(4),
rndc.conf(4).
Requests for Comments (RFC): 2845, available online at
available online at
available from the Internet Systems Consortium at
BIND 9.3 rndc(1)
