| Skip Navigation Links | |
| Exit Print View | |
 | man pages section 1M: System Administration Commands Oracle Solaris 11 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
| man pages section 1M: System Administration Commands Oracle Solaris 11 Information Library |
- name server control utility
rndc [-V] [-bsrc-addr] [-cconfig-file] [-kkey-file] [-sserver] [-pport] [-ykey_id]command
Therndc utility controls the operation of a name server. It supersedesthendc utility that was provided in previous BIND releases. Ifrndcis invoked with no command line options or arguments, it prints ashort summary of the supported commands and the available options and their arguments.
Therndc utility communicates with the name server over a TCP connection,sending commands authenticated with digital signatures. The only supported authentication algorithm inthe current versions ofrndc andnamed(1M) is HMAC-MD5, which uses ashared secret on each end of the connection. This algorithm provides TSIG-styleauthentication for the command request and the name server's response. All commandssent over the channel must be signed by akey_id known to theserver.
Therndc utility reads a configuration file to determine how to contactthe name server and decide what algorithm and key it should use.
The following options are supported:
Usesource-address 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.
Useconfig-file as the configuration file instead of the default/etc/rndc.conf.
Usekey-file as the key file instead of the default,/etc/rndc.key. The key in/etc/rndc.key is used to authenticate commands sent to the server if theconfig-file does not exist.
Theserver argument is the name or address of the server that matches a server statement in the configuration file forrndc. If no server is supplied on the command line, the host named by the default-server clause in the options statement of therndc configuration file is used.
Send commands to TCP portport instead of BIND 9's default control channel port, 953.
Enable verbose logging.
Use the keykey_id from the configuration file. Thekey_id argument must be known bynamed with the same algorithm and secret string for control message validation to succeed. If nokey_id is specified,rndc 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 thedefault-key clause of the options statement. The configuration file contains shared secrets that 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 byrndc, see theBIND 9 Administrator Reference Manualor runrndc without arguments to see its help message.
Therndc utility does not support all the commands of the BIND8ndc utility.
There is no way to provide the shared secret for akey_idwithout using the configuration file.
Several error messages tend toward the cryptic.
Seeattributes(5) for descriptions of the following attributes:
|
named(1M),rndc-confgen(1M),named.conf(4),rndc.conf(4),attributes(5)
See the BIND 9Administrator's Reference Manual. As of the date of publication ofthis man page, this document is available athttps://www.isc.org/software/bind/documentation.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.Legal Notices |   |