man.nsupdate.html revision 1e9517ea2156b990be21f44676d3370318eacf17
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<!--
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster - Copyright (C) 2000-2015 Internet Systems Consortium, Inc. ("ISC")
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster -
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster - This Source Code Form is subject to the terms of the Mozilla Public
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster - License, v. 2.0. If a copy of the MPL was not distributed with this
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster - file, You can obtain one at http://mozilla.org/MPL/2.0/.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster-->
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<html>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<head>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<title>nsupdate</title>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<link rel="prev" href="man.named-rrchecker.html" title="named-rrchecker">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<link rel="next" href="man.rndc.html" title="rndc">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster</head>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<div class="navheader">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<table width="100%" summary="Navigation header">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<tr><th colspan="3" align="center"><span class="application">nsupdate</span></th></tr>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<tr>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<td width="20%" align="left">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<a accesskey="p" href="man.named-rrchecker.html">Prev</a>�</td>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<th width="60%" align="center">Manual pages</th>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<td width="20%" align="right">�<a accesskey="n" href="man.rndc.html">Next</a>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster</td>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster</tr>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster</table>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<hr>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster</div>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<div class="refentry">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<a name="man.nsupdate"></a><div class="titlepage"></div>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<div class="refnamediv">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<h2>Name</h2>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<p><span class="application">nsupdate</span> &#8212; Dynamic DNS update utility</p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster</div>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<div class="refsynopsisdiv">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<h2>Synopsis</h2>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<div class="cmdsynopsis"><p><code class="command">nsupdate</code> [<code class="option">-d</code>] [<code class="option">-D</code>] [<code class="option">-L <em class="replaceable"><code>level</code></em></code>] [[<code class="option">-g</code>] | [<code class="option">-o</code>] | [<code class="option">-l</code>] | [<code class="option">-y <em class="replaceable"><code>[<span class="optional">hmac:</span>]keyname:secret</code></em></code>] | [<code class="option">-k <em class="replaceable"><code>keyfile</code></em></code>]] [<code class="option">-t <em class="replaceable"><code>timeout</code></em></code>] [<code class="option">-u <em class="replaceable"><code>udptimeout</code></em></code>] [<code class="option">-r <em class="replaceable"><code>udpretries</code></em></code>] [<code class="option">-R <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-v</code>] [<code class="option">-T</code>] [<code class="option">-P</code>] [<code class="option">-V</code>] [filename]</p></div>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster</div>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<div class="refsection">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<a name="id-1.14.24.7"></a><h2>DESCRIPTION</h2>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<p><span class="command"><strong>nsupdate</strong></span>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster is used to submit Dynamic DNS Update requests as defined in RFC 2136
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster to a name server.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster This allows resource records to be added or removed from a zone
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster without manually editing the zone file.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster A single update request can contain requests to add or remove more than
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster one
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster resource record.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster </p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster Zones that are under dynamic control via
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster <span class="command"><strong>nsupdate</strong></span>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster or a DHCP server should not be edited by hand.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster Manual edits could
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster conflict with dynamic updates and cause data to be lost.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster </p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster The resource records that are dynamically added or removed with
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster <span class="command"><strong>nsupdate</strong></span>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster have to be in the same zone.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster Requests are sent to the zone's master server.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster This is identified by the MNAME field of the zone's SOA record.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster </p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster Transaction signatures can be used to authenticate the Dynamic
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster DNS updates. These use the TSIG resource record type described
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster in RFC 2845 or the SIG(0) record described in RFC 2535 and
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster RFC 2931 or GSS-TSIG as described in RFC 3645.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster </p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster TSIG relies on
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster a shared secret that should only be known to
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster <span class="command"><strong>nsupdate</strong></span> and the name server.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster For instance, suitable <span class="type">key</span> and
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster <span class="type">server</span> statements would be added to
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster <code class="filename">/etc/named.conf</code> so that the name server
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster can associate the appropriate secret key and algorithm with
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster the IP address of the client application that will be using
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster TSIG authentication. You can use <span class="command"><strong>ddns-confgen</strong></span>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster to generate suitable configuration fragments.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster <span class="command"><strong>nsupdate</strong></span>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster uses the <code class="option">-y</code> or <code class="option">-k</code> options
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster to provide the TSIG shared secret. These options are mutually exclusive.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster </p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster SIG(0) uses public key cryptography.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster To use a SIG(0) key, the public key must be stored in a KEY
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster record in a zone served by the name server.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster </p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster GSS-TSIG uses Kerberos credentials. Standard GSS-TSIG mode
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster is switched on with the <code class="option">-g</code> flag. A
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster non-standards-compliant variant of GSS-TSIG used by Windows
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster 2000 can be switched on with the <code class="option">-o</code> flag.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster </p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster</div>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<div class="refsection">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<a name="id-1.14.24.8"></a><h2>OPTIONS</h2>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<div class="variablelist"><dl class="variablelist">
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<dt><span class="term">-d</span></dt>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<dd><p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster Debug mode. This provides tracing information about the
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster update requests that are made and the replies received
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster from the name server.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster </p></dd>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<dt><span class="term">-D</span></dt>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<dd><p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster Extra debug mode.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster </p></dd>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<dt><span class="term">-k <em class="replaceable"><code>keyfile</code></em></span></dt>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster<dd><p>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster The file containing the TSIG authentication key.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster Keyfiles may be in two formats: a single file containing
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster a <code class="filename">named.conf</code>-format <span class="command"><strong>key</strong></span>
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster statement, which may be generated automatically by
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster <span class="command"><strong>ddns-confgen</strong></span>, or a pair of files whose names are
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster of the format <code class="filename">K{name}.+157.+{random}.key</code> and
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster <code class="filename">K{name}.+157.+{random}.private</code>, which can be
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster generated by <span class="command"><strong>dnssec-keygen</strong></span>.
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster The <code class="option">-k</code> may also be used to specify a SIG(0) key used
a688bcbb4bcff5398fdd29b86f83450257dc0df4Allan Foster to authenticate Dynamic DNS update requests. In this case, the key
specified is not an HMAC-MD5 key.
</p></dd>
<dt><span class="term">-l</span></dt>
<dd><p>
Local-host only mode. This sets the server address to
localhost (disabling the <span class="command"><strong>server</strong></span> so that the server
address cannot be overridden). Connections to the local server will
use a TSIG key found in <code class="filename">/var/run/named/session.key</code>,
which is automatically generated by <span class="command"><strong>named</strong></span> if any
local master zone has set <span class="command"><strong>update-policy</strong></span> to
<span class="command"><strong>local</strong></span>. The location of this key file can be
overridden with the <code class="option">-k</code> option.
</p></dd>
<dt><span class="term">-L <em class="replaceable"><code>level</code></em></span></dt>
<dd><p>
Set the logging debug level. If zero, logging is disabled.
</p></dd>
<dt><span class="term">-p <em class="replaceable"><code>port</code></em></span></dt>
<dd><p>
Set the port to use for connections to a name server. The
default is 53.
</p></dd>
<dt><span class="term">-P</span></dt>
<dd><p>
Print the list of private BIND-specific resource record
types whose format is understood
by <span class="command"><strong>nsupdate</strong></span>. See also
the <code class="option">-T</code> option.
</p></dd>
<dt><span class="term">-r <em class="replaceable"><code>udpretries</code></em></span></dt>
<dd><p>
The number of UDP retries. The default is 3. If zero, only
one update request will be made.
</p></dd>
<dt><span class="term">-R <em class="replaceable"><code>randomdev</code></em></span></dt>
<dd><p>
Where to obtain randomness. If the operating system
does not provide a <code class="filename">/dev/random</code> or
equivalent device, the default source of randomness is keyboard
input. <code class="filename">randomdev</code> specifies the name of
a character device or file containing random data to be used
instead of the default. The special value
<code class="filename">keyboard</code> indicates that keyboard input
should be used. This option may be specified multiple times.
</p></dd>
<dt><span class="term">-t <em class="replaceable"><code>timeout</code></em></span></dt>
<dd><p>
The maximum time an update request can take before it is
aborted. The default is 300 seconds. Zero can be used to
disable the timeout.
</p></dd>
<dt><span class="term">-T</span></dt>
<dd>
<p>
Print the list of IANA standard resource record types
whose format is understood by <span class="command"><strong>nsupdate</strong></span>.
<span class="command"><strong>nsupdate</strong></span> will exit after the lists are
printed. The <code class="option">-T</code> option can be combined
with the <code class="option">-P</code> option.
</p>
<p>
Other types can be entered using "TYPEXXXXX" where "XXXXX" is the
decimal value of the type with no leading zeros. The rdata,
if present, will be parsed using the UNKNOWN rdata format,
(&lt;backslash&gt; &lt;hash&gt; &lt;space&gt; &lt;length&gt;
&lt;space&gt; &lt;hexstring&gt;).
</p>
</dd>
<dt><span class="term">-u <em class="replaceable"><code>udptimeout</code></em></span></dt>
<dd><p>
The UDP retry interval. The default is 3 seconds. If zero,
the interval will be computed from the timeout interval and
number of UDP retries.
</p></dd>
<dt><span class="term">-v</span></dt>
<dd><p>
Use TCP even for small update requests.
By default, <span class="command"><strong>nsupdate</strong></span>
uses UDP to send update requests to the name server unless they are too
large to fit in a UDP request in which case TCP will be used.
TCP may be preferable when a batch of update requests is made.
</p></dd>
<dt><span class="term">-V</span></dt>
<dd><p>
Print the version number and exit.
</p></dd>
<dt><span class="term">-y <em class="replaceable"><code>[<span class="optional">hmac:</span>]keyname:secret</code></em></span></dt>
<dd>
<p>
Literal TSIG authentication key.
<em class="parameter"><code>keyname</code></em> is the name of the key, and
<em class="parameter"><code>secret</code></em> is the base64 encoded shared secret.
<em class="parameter"><code>hmac</code></em> is the name of the key algorithm;
valid choices are <code class="literal">hmac-md5</code>,
<code class="literal">hmac-sha1</code>, <code class="literal">hmac-sha224</code>,
<code class="literal">hmac-sha256</code>, <code class="literal">hmac-sha384</code>, or
<code class="literal">hmac-sha512</code>. If <em class="parameter"><code>hmac</code></em>
is not specified, the default is <code class="literal">hmac-md5</code>.
</p>
<p>
NOTE: Use of the <code class="option">-y</code> option is discouraged because the
shared secret is supplied as a command line argument in clear text.
This may be visible in the output from
<span class="citerefentry"><span class="refentrytitle">ps</span>(1)</span>
or in a history file maintained by the user's shell.
</p>
</dd>
</dl></div>
</div>
<div class="refsection">
<a name="id-1.14.24.9"></a><h2>INPUT FORMAT</h2>
<p><span class="command"><strong>nsupdate</strong></span>
reads input from
<em class="parameter"><code>filename</code></em>
or standard input.
Each command is supplied on exactly one line of input.
Some commands are for administrative purposes.
The others are either update instructions or prerequisite checks on the
contents of the zone.
These checks set conditions that some name or set of
resource records (RRset) either exists or is absent from the zone.
These conditions must be met if the entire update request is to succeed.
Updates will be rejected if the tests for the prerequisite conditions
fail.
</p>
<p>
Every update request consists of zero or more prerequisites
and zero or more updates.
This allows a suitably authenticated update request to proceed if some
specified resource records are present or missing from the zone.
A blank input line (or the <span class="command"><strong>send</strong></span> command)
causes the
accumulated commands to be sent as one Dynamic DNS update request to the
name server.
</p>
<p>
The command formats and their meaning are as follows:
</p>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term">
<span class="command"><strong>server</strong></span>
{servername}
[port]
</span></dt>
<dd><p>
Sends all dynamic update requests to the name server
<em class="parameter"><code>servername</code></em>.
When no server statement is provided,
<span class="command"><strong>nsupdate</strong></span>
will send updates to the master server of the correct zone.
The MNAME field of that zone's SOA record will identify the
master
server for that zone.
<em class="parameter"><code>port</code></em>
is the port number on
<em class="parameter"><code>servername</code></em>
where the dynamic update requests get sent.
If no port number is specified, the default DNS port number of
53 is
used.
</p></dd>
<dt><span class="term">
<span class="command"><strong>local</strong></span>
{address}
[port]
</span></dt>
<dd><p>
Sends all dynamic update requests using the local
<em class="parameter"><code>address</code></em>.
When no local statement is provided,
<span class="command"><strong>nsupdate</strong></span>
will send updates using an address and port chosen by the
system.
<em class="parameter"><code>port</code></em>
can additionally be used to make requests come from a specific
port.
If no port number is specified, the system will assign one.
</p></dd>
<dt><span class="term">
<span class="command"><strong>zone</strong></span>
{zonename}
</span></dt>
<dd><p>
Specifies that all updates are to be made to the zone
<em class="parameter"><code>zonename</code></em>.
If no
<em class="parameter"><code>zone</code></em>
statement is provided,
<span class="command"><strong>nsupdate</strong></span>
will attempt determine the correct zone to update based on the
rest of the input.
</p></dd>
<dt><span class="term">
<span class="command"><strong>class</strong></span>
{classname}
</span></dt>
<dd><p>
Specify the default class.
If no <em class="parameter"><code>class</code></em> is specified, the
default class is
<em class="parameter"><code>IN</code></em>.
</p></dd>
<dt><span class="term">
<span class="command"><strong>ttl</strong></span>
{seconds}
</span></dt>
<dd><p>
Specify the default time to live for records to be added.
The value <em class="parameter"><code>none</code></em> will clear the default
ttl.
</p></dd>
<dt><span class="term">
<span class="command"><strong>key</strong></span>
[hmac:] {keyname}
{secret}
</span></dt>
<dd><p>
Specifies that all updates are to be TSIG-signed using the
<em class="parameter"><code>keyname</code></em> <em class="parameter"><code>secret</code></em> pair.
If <em class="parameter"><code>hmac</code></em> is specified, then it sets the
signing algorithm in use; the default is
<code class="literal">hmac-md5</code>. The <span class="command"><strong>key</strong></span>
command overrides any key specified on the command line via
<code class="option">-y</code> or <code class="option">-k</code>.
</p></dd>
<dt><span class="term">
<span class="command"><strong>gsstsig</strong></span>
</span></dt>
<dd><p>
Use GSS-TSIG to sign the updated. This is equivalent to
specifying <code class="option">-g</code> on the command line.
</p></dd>
<dt><span class="term">
<span class="command"><strong>oldgsstsig</strong></span>
</span></dt>
<dd><p>
Use the Windows 2000 version of GSS-TSIG to sign the updated.
This is equivalent to specifying <code class="option">-o</code> on the
command line.
</p></dd>
<dt><span class="term">
<span class="command"><strong>realm</strong></span>
{[<span class="optional">realm_name</span>]}
</span></dt>
<dd><p>
When using GSS-TSIG use <em class="parameter"><code>realm_name</code></em> rather
than the default realm in <code class="filename">krb5.conf</code>. If no
realm is specified the saved realm is cleared.
</p></dd>
<dt><span class="term">
<span class="command"><strong>check-names</strong></span>
{[<span class="optional">yes_or_no</span>]}
</span></dt>
<dd><p>
Turn on or off check-names processing on records to
be added. Check-names has no effect on prerequisites
or records to be deleted. By default check-names
processing is on. If check-names processing fails
the record will not be added to the UPDATE message.
</p></dd>
<dt><span class="term">
<span class="command"><strong>[<span class="optional">prereq</span>] nxdomain</strong></span>
{domain-name}
</span></dt>
<dd><p>
Requires that no resource record of any type exists with name
<em class="parameter"><code>domain-name</code></em>.
</p></dd>
<dt><span class="term">
<span class="command"><strong>[<span class="optional">prereq</span>] yxdomain</strong></span>
{domain-name}
</span></dt>
<dd><p>
Requires that
<em class="parameter"><code>domain-name</code></em>
exists (has as at least one resource record, of any type).
</p></dd>
<dt><span class="term">
<span class="command"><strong>[<span class="optional">prereq</span>] nxrrset</strong></span>
{domain-name}
[class]
{type}
</span></dt>
<dd><p>
Requires that no resource record exists of the specified
<em class="parameter"><code>type</code></em>,
<em class="parameter"><code>class</code></em>
and
<em class="parameter"><code>domain-name</code></em>.
If
<em class="parameter"><code>class</code></em>
is omitted, IN (internet) is assumed.
</p></dd>
<dt><span class="term">
<span class="command"><strong>[<span class="optional">prereq</span>] yxrrset</strong></span>
{domain-name}
[class]
{type}
</span></dt>
<dd><p>
This requires that a resource record of the specified
<em class="parameter"><code>type</code></em>,
<em class="parameter"><code>class</code></em>
and
<em class="parameter"><code>domain-name</code></em>
must exist.
If
<em class="parameter"><code>class</code></em>
is omitted, IN (internet) is assumed.
</p></dd>
<dt><span class="term">
<span class="command"><strong>[<span class="optional">prereq</span>] yxrrset</strong></span>
{domain-name}
[class]
{type}
{data...}
</span></dt>
<dd><p>
The
<em class="parameter"><code>data</code></em>
from each set of prerequisites of this form
sharing a common
<em class="parameter"><code>type</code></em>,
<em class="parameter"><code>class</code></em>,
and
<em class="parameter"><code>domain-name</code></em>
are combined to form a set of RRs. This set of RRs must
exactly match the set of RRs existing in the zone at the
given
<em class="parameter"><code>type</code></em>,
<em class="parameter"><code>class</code></em>,
and
<em class="parameter"><code>domain-name</code></em>.
The
<em class="parameter"><code>data</code></em>
are written in the standard text representation of the resource
record's
RDATA.
</p></dd>
<dt><span class="term">
<span class="command"><strong>[<span class="optional">update</span>] del[<span class="optional">ete</span>]</strong></span>
{domain-name}
[ttl]
[class]
[type [data...]]
</span></dt>
<dd><p>
Deletes any resource records named
<em class="parameter"><code>domain-name</code></em>.
If
<em class="parameter"><code>type</code></em>
and
<em class="parameter"><code>data</code></em>
is provided, only matching resource records will be removed.
The internet class is assumed if
<em class="parameter"><code>class</code></em>
is not supplied. The
<em class="parameter"><code>ttl</code></em>
is ignored, and is only allowed for compatibility.
</p></dd>
<dt><span class="term">
<span class="command"><strong>[<span class="optional">update</span>] add</strong></span>
{domain-name}
{ttl}
[class]
{type}
{data...}
</span></dt>
<dd><p>
Adds a new resource record with the specified
<em class="parameter"><code>ttl</code></em>,
<em class="parameter"><code>class</code></em>
and
<em class="parameter"><code>data</code></em>.
</p></dd>
<dt><span class="term">
<span class="command"><strong>show</strong></span>
</span></dt>
<dd><p>
Displays the current message, containing all of the
prerequisites and
updates specified since the last send.
</p></dd>
<dt><span class="term">
<span class="command"><strong>send</strong></span>
</span></dt>
<dd><p>
Sends the current message. This is equivalent to entering a
blank line.
</p></dd>
<dt><span class="term">
<span class="command"><strong>answer</strong></span>
</span></dt>
<dd><p>
Displays the answer.
</p></dd>
<dt><span class="term">
<span class="command"><strong>debug</strong></span>
</span></dt>
<dd><p>
Turn on debugging.
</p></dd>
<dt><span class="term">
<span class="command"><strong>version</strong></span>
</span></dt>
<dd><p>
Print version number.
</p></dd>
<dt><span class="term">
<span class="command"><strong>help</strong></span>
</span></dt>
<dd><p>
Print a list of commands.
</p></dd>
</dl></div>
<p>
</p>
<p>
Lines beginning with a semicolon are comments and are ignored.
</p>
</div>
<div class="refsection">
<a name="id-1.14.24.10"></a><h2>EXAMPLES</h2>
<p>
The examples below show how
<span class="command"><strong>nsupdate</strong></span>
could be used to insert and delete resource records from the
<span class="type">example.com</span>
zone.
Notice that the input in each example contains a trailing blank line so
that
a group of commands are sent as one dynamic update request to the
master name server for
<span class="type">example.com</span>.
</p>
<pre class="programlisting">
# nsupdate
&gt; update delete oldhost.example.com A
&gt; update add newhost.example.com 86400 A 172.16.1.1
&gt; send
</pre>
<p>
</p>
<p>
Any A records for
<span class="type">oldhost.example.com</span>
are deleted.
And an A record for
<span class="type">newhost.example.com</span>
with IP address 172.16.1.1 is added.
The newly-added record has a 1 day TTL (86400 seconds).
</p>
<pre class="programlisting">
# nsupdate
&gt; prereq nxdomain nickname.example.com
&gt; update add nickname.example.com 86400 CNAME somehost.example.com
&gt; send
</pre>
<p>
</p>
<p>
The prerequisite condition gets the name server to check that there
are no resource records of any type for
<span class="type">nickname.example.com</span>.
If there are, the update request fails.
If this name does not exist, a CNAME for it is added.
This ensures that when the CNAME is added, it cannot conflict with the
long-standing rule in RFC 1034 that a name must not exist as any other
record type if it exists as a CNAME.
(The rule has been updated for DNSSEC in RFC 2535 to allow CNAMEs to have
RRSIG, DNSKEY and NSEC records.)
</p>
</div>
<div class="refsection">
<a name="id-1.14.24.11"></a><h2>FILES</h2>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="constant">/etc/resolv.conf</code></span></dt>
<dd><p>
used to identify default name server
</p></dd>
<dt><span class="term"><code class="constant">/var/run/named/session.key</code></span></dt>
<dd><p>
sets the default TSIG key for use in local-only mode
</p></dd>
<dt><span class="term"><code class="constant">K{name}.+157.+{random}.key</code></span></dt>
<dd><p>
base-64 encoding of HMAC-MD5 key created by
<span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
</p></dd>
<dt><span class="term"><code class="constant">K{name}.+157.+{random}.private</code></span></dt>
<dd><p>
base-64 encoding of HMAC-MD5 key created by
<span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
</p></dd>
</dl></div>
</div>
<div class="refsection">
<a name="id-1.14.24.12"></a><h2>SEE ALSO</h2>
<p>
<em class="citetitle">RFC 2136</em>,
<em class="citetitle">RFC 3007</em>,
<em class="citetitle">RFC 2104</em>,
<em class="citetitle">RFC 2845</em>,
<em class="citetitle">RFC 1034</em>,
<em class="citetitle">RFC 2535</em>,
<em class="citetitle">RFC 2931</em>,
<span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
<span class="citerefentry"><span class="refentrytitle">ddns-confgen</span>(8)</span>,
<span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
</p>
</div>
<div class="refsection">
<a name="id-1.14.24.13"></a><h2>BUGS</h2>
<p>
The TSIG key is redundantly stored in two separate files.
This is a consequence of nsupdate using the DST library
for its cryptographic operations, and may change in future
releases.
</p>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="man.named-rrchecker.html">Prev</a>�</td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
<td width="40%" align="right">�<a accesskey="n" href="man.rndc.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">named-rrchecker</span>�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�<span class="application">rndc</span>
</td>
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0b3</p>
</body>
</html>