1RNDC(8)                              BIND9                             RNDC(8)
2
3
4

NAME

6       rndc - name server control utility
7

SYNOPSIS

9       rndc [-b source-address] [-c config-file] [-k key-file] [-s server]
10            [-p port] [-V] [-y key_id] {command}
11

DESCRIPTION

13       rndc controls the operation of a name server. It supersedes the ndc
14       utility that was provided in old BIND releases. If rndc is invoked with
15       no command line options or arguments, it prints a short summary of the
16       supported commands and the available options and their arguments.
17
18       rndc communicates with the name server over a TCP connection, sending
19       commands authenticated with digital signatures. In the current versions
20       of rndc and named, the only supported authentication algorithm is
21       HMAC-MD5, which uses a shared secret on each end of the connection.
22       This provides TSIG-style authentication for the command request and the
23       name server's response. All commands sent over the channel must be
24       signed by a key_id known to the server.
25
26       rndc reads a configuration file to determine how to contact the name
27       server and decide what algorithm and key it should use.
28

OPTIONS

30       -b source-address
31           Use source-address as the source address for the connection to the
32           server. Multiple instances are permitted to allow setting of both
33           the IPv4 and IPv6 source addresses.
34
35       -c config-file
36           Use config-file as the configuration file instead of the default,
37           /etc/rndc.conf.
38
39       -k key-file
40           Use key-file as the key file instead of the default, /etc/rndc.key.
41           The key in /etc/rndc.key will be used to authenticate commands sent
42           to the server if the config-file does not exist.
43
44       -s server
45           server is the name or address of the server which matches a server
46           statement in the configuration file for rndc. If no server is
47           supplied on the command line, the host named by the default-server
48           clause in the options statement of the rndc configuration file will
49           be used.
50
51       -p port
52           Send commands to TCP port port instead of BIND 9's default control
53           channel port, 953.
54
55       -V
56           Enable verbose logging.
57
58       -y key_id
59           Use the key key_id from the configuration file.  key_id must be
60           known by named with the same algorithm and secret string in order
61           for control message validation to succeed. If no key_id is
62           specified, rndc will first look for a key clause in the server
63           statement of the server being used, or if no server statement is
64           present for that host, then the default-key clause of the options
65           statement. Note that the configuration file contains shared secrets
66           which are used to send authenticated control commands to name
67           servers. It should therefore not have general read or write access.
68
69       For the complete set of commands supported by rndc, see the BIND 9
70       Administrator Reference Manual or run rndc without arguments to see its
71       help message.
72

LIMITATIONS

74       rndc does not yet support all the commands of the BIND 8 ndc utility.
75
76       There is currently no way to provide the shared secret for a key_id
77       without using the configuration file.
78
79       Several error messages could be clearer.
80

SEE ALSO

82       rndc.conf(5), named(8), named.conf(5), ndc(8), BIND 9 Administrator
83       Reference Manual.
84

AUTHOR

86       Internet Systems Consortium
87

89       Copyright © 2004, 2005, 2007 Internet Systems Consortium, Inc. ("ISC")
90       Copyright © 2000, 2001 Internet Software Consortium.
91
92
93
94BIND9                            June 30, 2000                         RNDC(8)
Impressum