1 .\" Copyright (C) 2004, 2005, 2007, 2013 Internet Systems Consortium, Inc. ("ISC")
2 .\" Copyright (C) 2000, 2001 Internet Software Consortium.
4 .\" Permission to use, copy, modify, and/or distribute this software for any
5 .\" purpose with or without fee is hereby granted, provided that the above
6 .\" copyright notice and this permission notice appear in all copies.
8 .\" THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
9 .\" REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
10 .\" AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
11 .\" INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
12 .\" LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
13 .\" OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
14 .\" PERFORMANCE OF THIS SOFTWARE.
22 .\" Generator: DocBook XSL Stylesheets v1.71.1 <http://docbook.sf.net/>
23 .\" Date: June 7, 2013
27 .TH "RNDC" "8" "June 7, 2013" "BIND9" "BIND9"
28 .\" disable hyphenation
30 .\" disable justification (adjust text to left margin only)
33 rndc \- name server control utility
36 \fBrndc\fR [\fB\-b\ \fR\fB\fIsource\-address\fR\fR] [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR] [\fB\-k\ \fR\fB\fIkey\-file\fR\fR] [\fB\-s\ \fR\fB\fIserver\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-V\fR] [\fB\-y\ \fR\fB\fIkey_id\fR\fR] {command}
40 controls the operation of a name server. It supersedes the
42 utility that was provided in old BIND releases. If
44 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.
47 communicates with the name server over a TCP connection, sending commands authenticated with digital signatures. In the current versions of
50 \fBnamed\fR, 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.
53 reads a configuration file to determine how to contact the name server and decide what algorithm and key it should use.
56 \-b \fIsource\-address\fR
60 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.
63 \-c \fIconfig\-file\fR
67 as the configuration file instead of the default,
75 as the key file instead of the default,
76 \fI/etc/rndc.key\fR. The key in
78 will be used to authenticate commands sent to the server if the
86 is the name or address of the server which matches a server statement in the configuration file for
87 \fBrndc\fR. If no server is supplied on the command line, the host named by the default\-server clause in the options statement of the
89 configuration file will be used.
94 Send commands to TCP port
96 instead of BIND 9's default control channel port, 953.
101 Enable verbose logging.
108 from the configuration file.
110 must be known by named with the same algorithm and secret string in order for control message validation to succeed. If no
114 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.
118 A list of commands supported by
120 can be seen by running
124 Currently supported commands are:
128 Reload configuration file and zones.
131 \fBreload \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
133 Reload the given zone.
136 \fBrefresh \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
138 Schedule zone maintenance for the given zone.
141 \fBretransfer \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
143 Retransfer the given slave zone from the master server.
145 If the zone is configured to use
146 \fBinline\-signing\fR, the signed version of the zone is discarded; after the retransfer of the unsigned version is complete, the signed version will be regenerated with all new signatures.
149 \fBsign \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
151 Fetch all DNSSEC keys for the given zone from the key directory (see the
153 option in the BIND 9 Administrator Reference Manual). If they are within their publication period, merge them into the zone's DNSKEY RRset. If the DNSKEY RRset is changed, then the zone is automatically re\-signed with the new key set.
155 This command requires that the
157 zone option be set to
160 maintain, and also requires the zone to be configured to allow dynamic DNS. (See "Dynamic Update Policies" in the Administrator Reference Manual for more details.)
163 \fBloadkeys \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
165 Fetch all DNSSEC keys for the given zone from the key directory. If they are within their publication period, merge them into the zone's DNSKEY RRset. Unlike
166 \fBrndc sign\fR, however, the zone is not immediately re\-signed by the new keys, but is allowed to incrementally re\-sign over time.
168 This command requires that the
170 zone option be set to
171 maintain, and also requires the zone to be configured to allow dynamic DNS. (See "Dynamic Update Policies" in the Administrator Reference Manual for more details.)
174 \fBfreeze \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
176 Suspend updates to a dynamic zone. If no zone is specified, then all zones are suspended. This allows manual edits to be made to a zone normally updated by dynamic update. It also causes changes in the journal file to be synced into the master file. All dynamic update attempts will be refused while the zone is frozen.
179 \fBthaw \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
181 Enable updates to a frozen dynamic zone. If no zone is specified, then all frozen zones are enabled. This causes the server to reload the zone from disk, and re\-enables dynamic updates after the load has completed. After a zone is thawed, dynamic updates will no longer be refused. If the zone has changed and the
182 \fBixfr\-from\-differences\fR
183 option is in use, then the journal file will be updated to reflect changes in the zone. Otherwise, if the zone has changed, any existing journal file will be removed.
186 \fBsync \fR\fB[\-clean]\fR\fB \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
188 Sync changes in the journal file for a dynamic zone to the master file. If the "\-clean" option is specified, the journal file is also removed. If no zone is specified, then all zones are synced.
191 \fBnotify \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
193 Resend NOTIFY messages for the zone.
198 Reload the configuration file and load new zones, but do not reload existing zone files even if they have changed. This is faster than a full
200 when there is a large number of zones because it avoids the need to examine the modification times of the zones files.
205 Write server statistics to the statistics file.
208 \fBquerylog\fR [on|off]
210 Enable or disable query logging. (For backward compatibility, this command can also be used without an argument to toggle query logging on and off.)
212 Query logging can also be enabled by explicitly directing the
229 \fBdumpdb \fR\fB[\-all|\-cache|\-zone]\fR\fB \fR\fB[\fIview ...\fR]\fR
231 Dump the server's caches (default) and/or zones to the dump file for the specified views. If no view is specified, all views are dumped.
234 \fBsecroots \fR\fB[\fIview ...\fR]\fR
236 Dump the server's security roots to the secroots file for the specified views. If no view is specified, security roots for all views are dumped.
239 \fBstop \fR\fB[\-p]\fR
241 Stop the server, making sure any recent changes made through dynamic update or IXFR are first saved to the master files of the updated zones. If
244 \fBnamed\fR's process id is returned. This allows an external process to determine when
246 had completed stopping.
249 \fBhalt \fR\fB[\-p]\fR
251 Stop the server immediately. Recent changes made through dynamic update or IXFR are not saved to the master files, but will be rolled forward from the journal files when the server is restarted. If
254 \fBnamed\fR's process id is returned. This allows an external process to determine when
256 had completed halting.
261 Increment the servers debugging level by one.
264 \fBtrace \fR\fB\fIlevel\fR\fR
266 Sets the server's debugging level to an explicit value.
271 Sets the server's debugging level to 0.
276 Flushes the server's cache.
279 \fBflushname\fR \fIname\fR [\fIview\fR]
281 Flushes the given name from the server's DNS cache and, if applicable, from the server's nameserver address database or bad\-server cache.
284 \fBflushtree\fR \fIname\fR [\fIview\fR]
286 Flushes the given name, and all of its subdomains, from the server's DNS cache. Note that this does
288 affect he server's address database or bad\-server cache.
293 Display status of the server. Note that the number of zones includes the internal
297 hint zone if there is not an explicit root zone configured.
302 Dump the list of queries
304 is currently recursing on.
307 \fBvalidation ( on | off | check ) \fR\fB[\fIview ...\fR]\fR\fB \fR
309 Enable, disable, or check the current status of DNSSEC validation. Note
311 also needs to be set to
315 to be effective. It defaults to enabled.
320 List the names of all TSIG keys currently configured for use by
322 in each view. The list both statically configured keys and dynamic TKEY\-negotiated keys.
325 \fBtsig\-delete\fR \fIkeyname\fR [\fIview\fR]
327 Delete a given TKEY\-negotiated key from the server. (This does not apply to statically configured TSIG keys.)
330 \fBaddzone \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR\fB \fR\fB\fIconfiguration\fR\fR\fB \fR
332 Add a zone while the server is running. This command requires the
333 \fBallow\-new\-zones\fR
337 string specified on the command line is the zone configuration text that would ordinarily be placed in
340 The configuration is saved in a file called
341 \fI\fIhash\fR\fR\fI.nzf\fR, where
343 is a cryptographic hash generated from the name of the view. When
345 is restarted, the file will be loaded into the view configuration, so that zones that were added can persist after a restart.
349 command would add the zone
353 $\fBrndc addzone example.com '{ type master; file "example.com.db"; };'\fR
355 (Note the brackets and semi\-colon around the zone configuration text.)
358 \fBdelzone \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR\fB \fR
360 Delete a zone while the server is running. Only zones that were originally added via
362 can be deleted in this manner.
365 \fBsigning \fR\fB[( \-list | \-clear \fIkeyid/algorithm\fR | \-clear all | \-nsec3param ( \fIparameters\fR | none ) ) ]\fR\fB \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR\fB \fR
367 List, edit, or remove the DNSSEC signing state for the specified zone. The status of ongoing DNSSEC operations (such as signing or generating NSEC3 chains) is stored in the zone in the form of DNS resource records of type
368 \fBsig\-signing\-type\fR.
369 \fBrndc signing \-list\fR
370 converts these records into a human\-readable form, indicating which keys are currently signing or have finished signing the zone, and which NSEC3 chains are being created or removed.
372 \fBrndc signing \-clear\fR
373 can remove a single key (specified in the same format that
374 \fBrndc signing \-list\fR
375 uses to display it), or all keys. In either case, only completed keys are removed; any record indicating that a key has not yet finished signing the zone will be retained.
377 \fBrndc signing \-nsec3param\fR
378 sets the NSEC3 parameters for a zone. This is the only supported mechanism for using NSEC3 with
379 \fBinline\-signing\fR
380 zones. Parameters are specified in the same format as an NSEC3PARAM resource record: hash algorithm, flags, iterations, and salt, in that order.
382 Currently, the only defined value for hash algorithm is
383 1, representing SHA\-1. The
388 1, depending on whether you wish to set the opt\-out bit in the NSEC3 chain.
390 defines the number of additional times to apply the algorithm when generating an NSEC3 hash. The
392 is a string of data expressed in hexadecimal, or a hyphen (`\-') if no salt is to be used.
394 So, for example, to create an NSEC3 chain using the SHA\-1 hash algorithm, no opt\-out flag, 10 iterations, and a salt value of "FFFF", use:
395 \fBrndc signing \-nsec3param 1 0 10 FFFF \fR\fB\fIzone\fR\fR. To set the opt\-out flag, 15 iterations, and no salt, use:
396 \fBrndc signing \-nsec3param 1 1 15 \- \fR\fB\fIzone\fR\fR.
398 \fBrndc signing \-nsec3param none\fR
399 removes an existing NSEC3 chain and replaces it with NSEC.
403 There is currently no way to provide the shared secret for a
405 without using the configuration file.
407 Several error messages could be clearer.
411 \fBrndc\-confgen\fR(8),
415 BIND 9 Administrator Reference Manual.
418 Internet Systems Consortium
420 Copyright \(co 2004, 2005, 2007, 2013 Internet Systems Consortium, Inc. ("ISC")
422 Copyright \(co 2000, 2001 Internet Software Consortium.