4501N/A - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC") 4501N/A - Copyright (C) 2000-2003 Internet Software Consortium. 4501N/A - Permission to use, copy, modify, and/or distribute this software for any 4501N/A - purpose with or without fee is hereby granted, provided that the above 4501N/A - copyright notice and this permission notice appear in all copies. 4501N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 4501N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 4501N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 4501N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 4501N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 4501N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 4501N/A - PERFORMANCE OF THIS SOFTWARE. 4501N/A<
meta http-
equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4501N/A<
meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
4501N/A<
link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
4501N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
4501N/A<
table width="100%" summary="Navigation header">
4501N/A<
tr><
th colspan="3" align="center"><
span class="application">rndc</
span></
th></
tr>
4501N/A<
td width="20%" align="left">
4501N/A<
th width="60%" align="center">Manual pages</
th>
4501N/A<
div class="refentry" lang="en">
4501N/A<
p><
span class="application">rndc</
span> — name server control utility</
p>
4501N/A<
div class="refsynopsisdiv">
4501N/A<
div class="cmdsynopsis"><
p><
code class="command">rndc</
code> [<
code class="option">-b <
em class="replaceable"><
code>source-address</
code></
em></
code>] [<
code class="option">-c <
em class="replaceable"><
code>config-file</
code></
em></
code>] [<
code class="option">-k <
em class="replaceable"><
code>key-file</
code></
em></
code>] [<
code class="option">-s <
em class="replaceable"><
code>server</
code></
em></
code>] [<
code class="option">-p <
em class="replaceable"><
code>port</
code></
em></
code>] [<
code class="option">-q</
code>] [<
code class="option">-r</
code>] [<
code class="option">-V</
code>] [<
code class="option">-y <
em class="replaceable"><
code>key_id</
code></
em></
code>] {command}</
p></
div>
4501N/A<
div class="refsect1" lang="en">
4501N/A<
a name="id2661219"></
a><
h2>DESCRIPTION</
h2>
4501N/A<
p><
span><
strong class="command">rndc</
strong></
span>
4501N/A controls the operation of a name
4501N/A server. It supersedes the <
span><
strong class="command">ndc</
strong></
span> utility
4501N/A that was provided in old BIND releases. If
4501N/A <
span><
strong class="command">rndc</
strong></
span> is invoked with no command line
4501N/A options or arguments, it prints a short summary of the
4501N/A supported commands and the available options and their
4501N/A<
p><
span><
strong class="command">rndc</
strong></
span>
4501N/A communicates with the name server over a TCP connection, sending
4501N/A commands authenticated with digital signatures. In the current
4501N/A <
span><
strong class="command">rndc</
strong></
span> and <
span><
strong class="command">named</
strong></
span>,
4501N/A the only supported authentication algorithms are HMAC-MD5
4501N/A (for compatibility), HMAC-SHA1, HMAC-SHA224, HMAC-SHA256
4501N/A (default), HMAC-SHA384 and HMAC-SHA512.
4501N/A They use a shared secret on each end of the connection.
4501N/A This provides TSIG-style authentication for the command
4501N/A request and the name server's response. All commands sent
4501N/A over the channel must be signed by a key_id known to the
4501N/A<
p><
span><
strong class="command">rndc</
strong></
span>
4501N/A reads a configuration file to
4501N/A determine how to contact the name server and decide what
4501N/A algorithm and key it should use.
5031N/A<
div class="refsect1" lang="en">
4501N/A<
a name="id2661269"></
a><
h2>OPTIONS</
h2>
4501N/A<
div class="variablelist"><
dl>
4501N/A<
dt><
span class="term">-b <
em class="replaceable"><
code>source-address</
code></
em></
span></
dt>
4501N/A Use <
em class="replaceable"><
code>source-address</
code></
em>
4501N/A as the source address for the connection to the server.
4501N/A Multiple instances are permitted to allow setting of both
4501N/A the IPv4 and IPv6 source addresses.
4501N/A<
dt><
span class="term">-c <
em class="replaceable"><
code>config-file</
code></
em></
span></
dt>
4501N/A Use <
em class="replaceable"><
code>config-file</
code></
em>
4501N/A as the configuration file instead of the default,
4501N/A<
dt><
span class="term">-k <
em class="replaceable"><
code>key-file</
code></
em></
span></
dt>
4501N/A Use <
em class="replaceable"><
code>key-file</
code></
em>
4501N/A as the key file instead of the default,
4501N/A commands sent to the server if the <
em class="replaceable"><
code>config-file</
code></
em>
4501N/A<
dt><
span class="term">-s <
em class="replaceable"><
code>server</
code></
em></
span></
dt>
4501N/A<
dd><
p><
em class="replaceable"><
code>server</
code></
em> is
4501N/A the name or address of the server which matches a
4501N/A server statement in the configuration file for
4501N/A <
span><
strong class="command">rndc</
strong></
span>. If no server is supplied on the
4501N/A command line, the host named by the default-server clause
4501N/A in the options statement of the <
span><
strong class="command">rndc</
strong></
span>
4501N/A configuration file will be used.
4501N/A<
dt><
span class="term">-p <
em class="replaceable"><
code>port</
code></
em></
span></
dt>
4501N/A <
em class="replaceable"><
code>port</
code></
em>
4501N/A of BIND 9's default control channel port, 953.
4501N/A<
dt><
span class="term">-q</
span></
dt>
4501N/A Quiet mode: Message text returned by the server
4501N/A will not be printed except when there is an error.
4501N/A<
dt><
span class="term">-r</
span></
dt>
4501N/A Instructs <
span><
strong class="command">rndc</
strong></
span> to print the result code
4501N/A returned by <
span><
strong class="command">named</
strong></
span> after executing the
4501N/A requested command (
e.g., ISC_R_SUCCESS, ISC_R_FAILURE, etc).
4501N/A<
dt><
span class="term">-V</
span></
dt>
4501N/A<
dt><
span class="term">-y <
em class="replaceable"><
code>key_id</
code></
em></
span></
dt>
4501N/A Use the key <
em class="replaceable"><
code>key_id</
code></
em>
4501N/A from the configuration file.
4501N/A <
em class="replaceable"><
code>key_id</
code></
em>
4501N/A known by <
span><
strong class="command">named</
strong></
span> with the same algorithm and secret string
4501N/A in order for control message validation to succeed.
4501N/A If no <
em class="replaceable"><
code>key_id</
code></
em>
4501N/A is specified, <
span><
strong class="command">rndc</
strong></
span> will first look
4501N/A for a key clause in the server statement of the server
4501N/A being used, or if no server statement is present for that
4501N/A host, then the default-key clause of the options statement.
4501N/A Note that the configuration file contains shared secrets
4501N/A which are used to send authenticated control commands
4501N/A to name servers. It should therefore not have general read
4501N/A<
div class="refsect1" lang="en">
4501N/A<
a name="id2662341"></
a><
h2>COMMANDS</
h2>
4501N/A A list of commands supported by <
span><
strong class="command">rndc</
strong></
span> can
4501N/A be seen by running <
span><
strong class="command">rndc</
strong></
span> without arguments.
4501N/A Currently supported commands are:
4501N/A<
div class="variablelist"><
dl>
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>addzone <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>] <
em class="replaceable"><
code>configuration</
code></
em> </
code></
strong></
span></
dt>
4501N/A Add a zone while the server is running. This
4501N/A <
span><
strong class="command">allow-new-zones</
strong></
span> option to be set
4501N/A to <
strong class="userinput"><
code>yes</
code></
strong>. The
4501N/A <
em class="replaceable"><
code>configuration</
code></
em> string
4501N/A specified on the command line is the zone
4501N/A configuration text that would ordinarily be
4501N/A The configuration is saved in a file called
4501N/A <
code class="filename"><
em class="replaceable"><
code>name</
code></
em>.nzf</
code>,
4501N/A where <
em class="replaceable"><
code>name</
code></
em> is the
4501N/A name of the view, or if it contains characters
4501N/A that are incompatible with use as a file name, a
4501N/A cryptographic hash generated from the name
4501N/A When <
span><
strong class="command">named</
strong></
span> is
4501N/A restarted, the file will be loaded into the view
4501N/A configuration, so that zones that were added
4501N/A can persist after a restart.
4501N/A This sample <
span><
strong class="command">addzone</
strong></
span> command
4501N/A (Note the brackets and semi-colon around the zone
4641N/A See also <
span><
strong class="command">rndc delzone</
strong></
span> and <
span><
strong class="command">rndc modzone</
strong></
span>.
4641N/A<
dt><
span class="term"><
strong class="userinput"><
code>delzone [<
span class="optional">-clean</
span>] <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>] </
code></
strong></
span></
dt>
4501N/A Delete a zone while the server is running.
4501N/A If the <
code class="option">-clean</
code> argument is specified,
4501N/A the zone's master file (and journal file, if any)
4501N/A will be deleted along with the zone. Without the
4501N/A <
code class="option">-clean</
code> option, zone files must
4501N/A be cleaned up by hand. (If the zone is of
4501N/A type "slave" or "stub", the files needing to
4501N/A be cleaned up will be reported in the output
4501N/A of the <
span><
strong class="command">rndc delzone</
strong></
span> command.)
4501N/A If the zone was originally added via
4501N/A <
span><
strong class="command">rndc addzone</
strong></
span>, then it will be
4501N/A removed permanently. However, if it was originally
4501N/A that original configuration is still in place; when
4501N/A the server is restarted or reconfigured, the zone will
4501N/A come back. To remove it permanently, it must also be
4501N/A See also <
span><
strong class="command">rndc addzone</
strong></
span> and <
span><
strong class="command">rndc modzone</
strong></
span>.
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>dumpdb [<
span class="optional">-all|-cache|-zone</
span>] [<
span class="optional"><
em class="replaceable"><
code>view ...</
code></
em></
span>]</
code></
strong></
span></
dt>
4501N/A dump file for the specified views. If no view is
4501N/A (See the <
span><
strong class="command">dump-file</
strong></
span> option in
4501N/A the BIND 9 Administrator Reference Manual.)
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>flush</
code></
strong></
span></
dt>
4501N/A Flushes the server's cache.
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>flushname</
code></
strong> <
em class="replaceable"><
code>name</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>] </
span></
dt>
4501N/A Flushes the given name from the view's DNS cache
4501N/A and, if applicable, from the view's nameserver address
4501N/A database, bad server cache and SERVFAIL cache.
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>flushtree</
code></
strong> <
em class="replaceable"><
code>name</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>] </
span></
dt>
4501N/A Flushes the given name, and all of its subdomains,
4501N/A from the view's DNS cache, address database,
4501N/A bad server cache, and SERVFAIL cache.
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>freeze [<
span class="optional"><
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
span>]</
code></
strong></
span></
dt>
4501N/A Suspend updates to a dynamic zone. If no zone is
4501N/A specified, then all zones are suspended. This allows
4501N/A manual edits to be made to a zone normally updated by
4501N/A dynamic update. It also causes changes in the
4501N/A journal file to be synced into the master file.
4501N/A All dynamic update attempts will be refused while
4501N/A See also <
span><
strong class="command">rndc thaw</
strong></
span>.
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>halt [<
span class="optional">-p</
span>]</
code></
strong></
span></
dt>
4501N/A Stop the server immediately. Recent changes
4501N/A made through dynamic update or IXFR are not saved to
4501N/A the master files, but will be rolled forward from the
4501N/A journal files when the server is restarted.
4501N/A If <
code class="option">-p</
code> is specified <
span><
strong class="command">named</
strong></
span>'s process id is returned.
4501N/A This allows an external process to determine when <
span><
strong class="command">named</
strong></
span>
4501N/A See also <
span><
strong class="command">rndc stop</
strong></
span>.
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>loadkeys <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
code></
strong></
span></
dt>
4501N/A Fetch all DNSSEC keys for the given zone
4501N/A from the key directory. If they are within
4501N/A their publication period, merge them into the
4501N/A zone's DNSKEY RRset. Unlike <
span><
strong class="command">rndc
4501N/A sign</
strong></
span>, however, the zone is not
4501N/A immediately re-signed by the new keys, but is
4501N/A allowed to incrementally re-sign over time.
4501N/A This command requires that the
4501N/A <
span><
strong class="command">auto-dnssec</
strong></
span> zone option
4501N/A be set to <
code class="literal">maintain</
code>,
4501N/A and also requires the zone to be configured to
4501N/A (See "Dynamic Update Policies" in the Administrator
4501N/A Reference Manual for more details.)
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>managed-keys <
em class="replaceable"><
code>(status | refresh | sync)</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
code></
strong></
span></
dt>
4501N/A When run with the "status" keyword, print the current
4501N/A status of the managed-keys database for the specified
4501N/A view, or for all views if none is specified. When run
4501N/A with the "refresh" keyword, force an immediate refresh
4501N/A of all the managed-keys in the specified view, or all
4501N/A views. When run with the "sync" keyword, force an
4501N/A immediate dump of the managed-keys database to disk (in
4501N/A (<
code class="filename"><
em class="replaceable"><
code>viewname</
code></
em>.mkeys</
code>).
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>modzone <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>] <
em class="replaceable"><
code>configuration</
code></
em> </
code></
strong></
span></
dt>
4501N/A Modify the configuration of a zone while the server
4501N/A is running. This command requires the
4501N/A <
span><
strong class="command">allow-new-zones</
strong></
span> option to be
4501N/A set to <
strong class="userinput"><
code>yes</
code></
strong>. As with
4501N/A <
span><
strong class="command">addzone</
strong></
span>, the
4501N/A <
em class="replaceable"><
code>configuration</
code></
em> string
4501N/A specified on the command line is the zone
4501N/A configuration text that would ordinarily be
4501N/A If the zone was originally added via
4501N/A <
span><
strong class="command">rndc addzone</
strong></
span>, the configuration
4501N/A changes will be recorded permanently and will still be
4501N/A in effect after the server is restarted or reconfigured.
4501N/A However, if it was originally configured in
4501N/A configuration is still in place; when the server is
4501N/A restarted or reconfigured, the zone will revert to
4501N/A its original configuration. To make the changes
4501N/A permanent, it must also be modified in
4501N/A See also <
span><
strong class="command">rndc addzone</
strong></
span> and <
span><
strong class="command">rndc delzone</
strong></
span>.
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>notify <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
code></
strong></
span></
dt>
4501N/A Resend NOTIFY messages for the zone.
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>notrace</
code></
strong></
span></
dt>
4501N/A Sets the server's debugging level to 0.
4501N/A See also <
span><
strong class="command">rndc trace</
strong></
span>.
4501N/A<
dt><
span class="term"><
strong class="userinput"><
code>nta
4501N/A [<
span class="optional">( -d | -f | -r | -l <
em class="replaceable"><
code>duration</
code></
em>)</
span>]
4501N/A <
em class="replaceable"><
code>domain</
code></
em>
4501N/A [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]
4501N/A </
code></
strong></
span></
dt>
4501N/A Sets a DNSSEC negative trust anchor (NTA)
4501N/A for <
code class="option">domain</
code>, with a lifetime of
4501N/A <
code class="option">duration</
code>. The default lifetime is
4501N/A <
code class="option">nta-lifetime</
code> option, and defaults to
4501N/A one hour. The lifetime cannot exceed one week.
4501N/A A negative trust anchor selectively disables
4501N/A DNSSEC validation for zones that are known to be
4501N/A failing because of misconfiguration rather than
4501N/A an attack. When data to be validated is
4501N/A at or below an active NTA (and above any other
4501N/A configured trust anchors), <
span><
strong class="command">named</
strong></
span> will
4501N/A abort the DNSSEC validation process and treat the data as
4501N/A insecure rather than bogus. This continues until the
4501N/A NTAs persist across restarts of the <
span><
strong class="command">named</
strong></
span> server.
4501N/A The NTAs for a view are saved in a file called
4501N/A <
code class="filename"><
em class="replaceable"><
code>name</
code></
em>.nta</
code>,
4501N/A where <
em class="replaceable"><
code>name</
code></
em> is the
4501N/A name of the view, or if it contains characters
4501N/A that are incompatible with use as a file name, a
4501N/A cryptographic hash generated from the name
4501N/A An existing NTA can be removed by using the
4501N/A <
code class="option">-remove</
code> option.
4501N/A An NTA's lifetime can be specified with the
4501N/A <
code class="option">-lifetime</
code> option. TTL-style
4501N/A suffixes can be used to specify the lifetime in
4501N/A seconds, minutes, or hours. If the specified NTA
4501N/A already exists, its lifetime will be updated to the
4501N/A new value. Setting <
code class="option">lifetime</
code> to zero
4501N/A is equivalent to <
code class="option">-remove</
code>.
4501N/A If <
code class="option">-dump</
code> is used, any other arguments
4501N/A are ignored, and a list of existing NTAs is printed
4501N/A (note that this may include NTAs that are expired but
4501N/A have not yet been cleaned up).
4501N/A Normally, <
span><
strong class="command">named</
strong></
span> will periodically
4501N/A test to see whether data below an NTA can now be
4501N/A validated (see the <
code class="option">nta-recheck</
code> option
4501N/A in the Administrator Reference Manual for details).
4501N/A If data can be validated, then the NTA is regarded as
4501N/A no longer necessary, and will be allowed to expire
4501N/A early. The <
code class="option">-force</
code> overrides this
4501N/A behavior and forces an NTA to persist for its entire
4501N/A lifetime, regardless of whether data could be
4501N/A validated if the NTA were not present.
4501N/A All of these options can be shortened,
i.e., to
<
code class="option">-l</
code>, <
code class="option">-r</
code>, <
code class="option">-d</
code>,
and <
code class="option">-f</
code>.
<
dt><
span class="term"><
strong class="userinput"><
code>querylog</
code></
strong> [<
span class="optional">on|off</
span>] </
span></
dt>
Enable or disable query logging. (For backward
compatibility, this command can also be used without
an argument to toggle query logging on and off.)
Query logging can also be enabled
by explicitly directing the <
span><
strong class="command">queries</
strong></
span>
<
span><
strong class="command">category</
strong></
span> to a
<
span><
strong class="command">channel</
strong></
span> in the
<
span><
strong class="command">logging</
strong></
span> section of
<
code class="filename">
named.conf</
code> or by specifying
<
span><
strong class="command">querylog yes;</
strong></
span> in the
<
span><
strong class="command">options</
strong></
span> section of
<
dt><
span class="term"><
strong class="userinput"><
code>reconfig</
code></
strong></
span></
dt>
Reload the configuration file and load new zones,
but do not reload existing zone files even if they
This is faster than a full <
span><
strong class="command">reload</
strong></
span> when there
is a large number of zones because it avoids the need
modification times of the zones files.
<
dt><
span class="term"><
strong class="userinput"><
code>recursing</
code></
strong></
span></
dt>
Dump the list of queries <
span><
strong class="command">named</
strong></
span> is currently recursing
<
dt><
span class="term"><
strong class="userinput"><
code>refresh <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
code></
strong></
span></
dt>
Schedule zone maintenance for the given zone.
<
dt><
span class="term"><
strong class="userinput"><
code>reload</
code></
strong></
span></
dt>
Reload configuration file and zones.
<
dt><
span class="term"><
strong class="userinput"><
code>reload <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
code></
strong></
span></
dt>
<
dt><
span class="term"><
strong class="userinput"><
code>retransfer <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
code></
strong></
span></
dt>
Retransfer the given slave zone from the master server.
If the zone is configured to use
<
span><
strong class="command">inline-signing</
strong></
span>, 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
<
dt><
span class="term"><
strong class="userinput"><
code>scan</
code></
strong></
span></
dt>
Scan the list of available network interfaces
for changes, without performing a full
<
span><
strong class="command">reconfig</
strong></
span> or waiting for the
<
span><
strong class="command">interface-interval</
strong></
span> timer.
<
dt><
span class="term"><
strong class="userinput"><
code>secroots [<
span class="optional">-</
span>] [<
span class="optional"><
em class="replaceable"><
code>view ...</
code></
em></
span>]</
code></
strong></
span></
dt>
Dump the server's security roots and negative trust anchors
for the specified views. If no view is specified, all views
If the first argument is "-", then the output is
returned via the <
span><
strong class="command">rndc</
strong></
span> response channel
and printed to the standard output.
Otherwise, it is written to the secroots dump file, which
overridden via the <
code class="option">secroots-file</
code> option in
See also <
span><
strong class="command">rndc managed-keys</
strong></
span>.
<
dt><
span class="term"><
strong class="userinput"><
code>showzone <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>] </
code></
strong></
span></
dt>
Print the configuration of a running zone.
See also <
span><
strong class="command">rndc zonestatus</
strong></
span>.
<
dt><
span class="term"><
strong class="userinput"><
code>sign <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
code></
strong></
span></
dt>
Fetch all DNSSEC keys for the given zone
from the key directory (see the
<
span><
strong class="command">key-directory</
strong></
span> 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.
This command requires that the
<
span><
strong class="command">auto-dnssec</
strong></
span> zone option be set
to <
code class="literal">allow</
code> or
<
code class="literal">maintain</
code>,
and also requires the zone to be configured to
(See "Dynamic Update Policies" in the Administrator
Reference Manual for more details.)
See also <
span><
strong class="command">rndc loadkeys</
strong></
span>.
<
dt><
span class="term"><
strong class="userinput"><
code>signing [<
span class="optional">( -list | -clear <
em class="replaceable"><
code>
keyid/
algorithm</
code></
em> | -clear <
code class="literal">all</
code> | -nsec3param ( <
em class="replaceable"><
code>parameters</
code></
em> | <
code class="literal">none</
code> ) | -serial <
em class="replaceable"><
code>value</
code></
em> ) </
span>] <
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>] </
code></
strong></
span></
dt>
List, edit, or remove the DNSSEC signing state records
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
<
span><
strong class="command">sig-signing-type</
strong></
span>.
<
span><
strong class="command">rndc signing -list</
strong></
span> 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.
<
span><
strong class="command">rndc signing -clear</
strong></
span> can remove
a single key (specified in the same format that
<
span><
strong class="command">rndc signing -list</
strong></
span> 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
<
span><
strong class="command">rndc signing -nsec3param</
strong></
span> sets
the NSEC3 parameters for a zone. This is the
only supported mechanism for using NSEC3 with
<
span><
strong class="command">inline-signing</
strong></
span> zones.
Parameters are specified in the same format as
an NSEC3PARAM resource record: hash algorithm,
flags, iterations, and salt, in that order.
Currently, the only defined value for hash algorithm
is <
code class="literal">1</
code>, representing SHA-1.
The <
code class="option">flags</
code> may be set to
<
code class="literal">0</
code> or <
code class="literal">1</
code>,
depending on whether you wish to set the opt-out
bit in the NSEC3 chain. <
code class="option">iterations</
code>
defines the number of additional times to apply
the algorithm when generating an NSEC3 hash. The
<
code class="option">salt</
code> is a string of data expressed
in hexadecimal, a hyphen (`-') if no salt is
to be used, or the keyword <
code class="literal">auto</
code>,
which causes <
span><
strong class="command">named</
strong></
span> to generate a
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:
<
span><
strong class="command">rndc signing -nsec3param 1 0 10 FFFF <
em class="replaceable"><
code>zone</
code></
em></
strong></
span>.
To set the opt-out flag, 15 iterations, and no
<
span><
strong class="command">rndc signing -nsec3param 1 1 15 - <
em class="replaceable"><
code>zone</
code></
em></
strong></
span>.
<
span><
strong class="command">rndc signing -nsec3param none</
strong></
span>
removes an existing NSEC3 chain and replaces it
<
span><
strong class="command">rndc signing -serial value</
strong></
span> sets
the serial number of the zone to value. If the value
would cause the serial number to go backwards it will
be rejected. The primary use is to set the serial on
<
dt><
span class="term"><
strong class="userinput"><
code>stats</
code></
strong></
span></
dt>
Write server statistics to the statistics file.
(See the <
span><
strong class="command">statistics-file</
strong></
span> option in
the BIND 9 Administrator Reference Manual.)
<
dt><
span class="term"><
strong class="userinput"><
code>status</
code></
strong></
span></
dt>
Display status of the server.
Note that the number of zones includes the internal <
span><
strong class="command">
bind/
CH</
strong></
span> zone
and the default <
span><
strong class="command">/
IN</
strong></
span>
hint zone if there is not an
explicit root zone configured.
<
dt><
span class="term"><
strong class="userinput"><
code>stop [<
span class="optional">-p</
span>]</
code></
strong></
span></
dt>
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 <
code class="option">-p</
code> is specified <
span><
strong class="command">named</
strong></
span>'s process id is returned.
This allows an external process to determine when <
span><
strong class="command">named</
strong></
span>
<
p>See also <
span><
strong class="command">rndc halt</
strong></
span>.</
p>
<
dt><
span class="term"><
strong class="userinput"><
code>sync [<
span class="optional">-clean</
span>] [<
span class="optional"><
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
span>]</
code></
strong></
span></
dt>
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.
<
dt><
span class="term"><
strong class="userinput"><
code>thaw [<
span class="optional"><
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
span>]</
code></
strong></
span></
dt>
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
<
span><
strong class="command">ixfr-from-differences</
strong></
span> 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
<
p>See also <
span><
strong class="command">rndc freeze</
strong></
span>.</
p>
<
dt><
span class="term"><
strong class="userinput"><
code>trace</
code></
strong></
span></
dt>
Increment the servers debugging level by one.
<
dt><
span class="term"><
strong class="userinput"><
code>trace <
em class="replaceable"><
code>level</
code></
em></
code></
strong></
span></
dt>
Sets the server's debugging level to an explicit
See also <
span><
strong class="command">rndc notrace</
strong></
span>.
<
dt><
span class="term"><
strong class="userinput"><
code>tsig-delete</
code></
strong> <
em class="replaceable"><
code>keyname</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span></
dt>
Delete a given TKEY-negotiated key from the server.
(This does not apply to statically configured TSIG
<
dt><
span class="term"><
strong class="userinput"><
code>tsig-list</
code></
strong></
span></
dt>
List the names of all TSIG keys currently configured
for use by <
span><
strong class="command">named</
strong></
span> in each view. The
list both statically configured keys and dynamic
<
dt><
span class="term"><
strong class="userinput"><
code>validation ( on | off | check ) [<
span class="optional"><
em class="replaceable"><
code>view ...</
code></
em></
span>] </
code></
strong></
span></
dt>
Enable, disable, or check the current status of
Note <
span><
strong class="command">dnssec-enable</
strong></
span> also needs to be
set to <
strong class="userinput"><
code>yes</
code></
strong> or
<
strong class="userinput"><
code>auto</
code></
strong> to be effective.
<
dt><
span class="term"><
strong class="userinput"><
code>zonestatus [<
span class="optional"><
em class="replaceable"><
code>zone</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>class</
code></
em> [<
span class="optional"><
em class="replaceable"><
code>view</
code></
em></
span>]</
span>]</
span>]</
code></
strong></
span></
dt>
Displays the current status of the given zone,
including the master file name and any include
files from which it was loaded, when it was most
recently loaded, the current serial number, the
number of nodes, whether the zone supports
dynamic updates, whether the zone is DNSSEC
signed, whether it uses automatic DNSSEC key
management or inline signing, and the scheduled
refresh or expiry times for the zone.
See also <
span><
strong class="command">rndc showzone</
strong></
span>.
<
div class="refsect1" lang="en">
<
a name="id2690824"></
a><
h2>LIMITATIONS</
h2>
There is currently no way to provide the shared secret for a
<
code class="option">key_id</
code> without using the configuration file.
Several error messages could be clearer.
<
div class="refsect1" lang="en">
<
a name="id2690842"></
a><
h2>SEE ALSO</
h2>
<
p><
span class="citerefentry"><
span class="refentrytitle">
rndc.conf</
span>(5)</
span>,
<
span class="citerefentry"><
span class="refentrytitle">rndc-confgen</
span>(8)</
span>,
<
span class="citerefentry"><
span class="refentrytitle">named</
span>(8)</
span>,
<
span class="citerefentry"><
span class="refentrytitle">
named.conf</
span>(5)</
span>,
<
span class="citerefentry"><
span class="refentrytitle">ndc</
span>(8)</
span>,
<
em class="citetitle">BIND 9 Administrator Reference Manual</
em>.
<
div class="refsect1" lang="en">
<
a name="id2690966"></
a><
h2>AUTHOR</
h2>
<
p><
span class="corpauthor">Internet Systems Consortium</
span>
<
table width="100%" summary="Navigation footer">
<
td width="40%" align="left">
<
td width="20%" align="center"><
a accesskey="u" href="Bv9ARM.ch13.html">Up</
a></
td>
<
td width="40%" align="left" valign="top">
<
span class="application">nsupdate</
span>�</
td>
<
td width="20%" align="center"><
a accesskey="h" href="Bv9ARM.html">Home</
a></
td>
<
td width="40%" align="right" valign="top">�<
code class="filename">
rndc.conf</
code>
<
p style="text-align: center;">BIND 9.11.0pre-alpha</
p>