rrnnddcc controls the operation of a name server. It supersedes the nnddcc utility that was provided in old BIND releases. If rrnnddcc 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.
rrnnddcc communicates with the name server over a TCP connection, sending commands authenticated with digital signatures. In the current versions of rrnnddcc and nnaammeedd, 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.
rrnnddcc reads a configuration file to determine how to contact the name server and decide what algorithm and key it should use.
-b _s_o_u_r_c_e_-_a_d_d_r_e_s_s Use _s_o_u_r_c_e_-_a_d_d_r_e_s_s 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.
-c _c_o_n_f_i_g_-_f_i_l_e Use _c_o_n_f_i_g_-_f_i_l_e as the configuration file instead of the default, _/_e_t_c_/_r_n_d_c_._c_o_n_f.
-k _k_e_y_-_f_i_l_e Use _k_e_y_-_f_i_l_e as the key file instead of the default, _/_e_t_c_/_r_n_d_c_._k_e_y. The key in _/_e_t_c_/_r_n_d_c_._k_e_y will be used to authenticate commands sent to the server if the _c_o_n_f_i_g_-_f_i_l_e does not exist.
-s _s_e_r_v_e_r _s_e_r_v_e_r is the name or address of the server which matches a server statement in the configuration file for rrnnddcc. If no server is supplied on the command line, the host named by the default-server clause in the options statement of the rrnnddcc configuration file will be used.
-p _p_o_r_t Send commands to TCP port _p_o_r_t instead of BIND 9's default control channel port, 953.
-V Enable verbose logging.
-y _k_e_y___i_d Use the key _k_e_y___i_d from the configuration file. _k_e_y___i_d must be known by named with the same algorithm and secret string in order for control message validation to succeed. If no _k_e_y___i_d is specified, rrnnddcc 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 rrnnddcc, see the BIND 9 Administrator Reference Manual or run rrnnddcc without arguments to see its help message.
rrnnddcc does not yet support all the commands of the BIND 8 nnddcc utility.
There is currently no way to provide the shared secret for a kkeeyy__iidd without using the configuration file.
Several error messages could be clearer.
rrnnddcc..ccoonnff(5), rrnnddcc--ccoonnffggeenn(8), nnaammeedd(8), nnaammeedd..ccoonnff(5), nnddcc(8), BIND 9 Administrator Reference Manual.
Internet Systems Consortium