man.rndc.html revision 605b07cadd58ff1d8f89ddf277451ee87a542f9b
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC")
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - Copyright (C) 2000-2003 Internet Software Consortium.
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - Permission to use, copy, modify, and distribute this software for any
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - purpose with or without fee is hereby granted, provided that the above
7c2fbfb345896881c631598ee3852ce9ce33fb07April Chin - copyright notice and this permission notice appear in all copies.
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin - PERFORMANCE OF THIS SOFTWARE.
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<!-- $Id: man.rndc.html,v 1.17 2006/01/29 22:57:16 marka Exp $ -->
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<link rel="next" href="man.rndc.conf.html" title="rndc.conf">
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<tr><th colspan="3" align="center"><span class="application">rndc</span></th></tr>
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<td width="20%" align="right">�<a accesskey="n" href="man.rndc.conf.html">Next</a>
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<p><span class="application">rndc</span> — name server control utility</p>
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<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">-V</code>] [<code class="option">-y <em class="replaceable"><code>key_id</code></em></code>] {command}</p></div>
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin controls the operation of a name
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin server. It supersedes the <span><strong class="command">ndc</strong></span> utility
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin that was provided in old BIND releases. If
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin <span><strong class="command">rndc</strong></span> is invoked with no command line
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin options or arguments, it prints a short summary of the
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin supported commands and the available options and their
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin arguments.
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin communicates with the name server
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin over a TCP connection, sending commands authenticated with
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin digital signatures. In the current versions of
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin <span><strong class="command">rndc</strong></span> and <span><strong class="command">named</strong></span> named
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin the only supported authentication algorithm is HMAC-MD5,
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin which uses a shared secret on each end of the connection.
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin This provides TSIG-style authentication for the command
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin request and the name server's response. All commands sent
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin over the channel must be signed by a key_id known to the
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin reads a configuration file to
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin determine how to contact the name server and decide what
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin algorithm and key it should use.
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<dt><span class="term">-b <em class="replaceable"><code>source-address</code></em></span></dt>
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin Use <em class="replaceable"><code>source-address</code></em>
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin as the source address for the connection to the server.
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin Multiple instances are permitted to allow setting of both
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin the IPv4 and IPv6 source addresses.
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin<dt><span class="term">-c <em class="replaceable"><code>config-file</code></em></span></dt>
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin Use <em class="replaceable"><code>config-file</code></em>
da2e3ebdc1edfbc5028edf1354e7dd2fa69a7968chin as the configuration file instead of the default,