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