1N/A - Copyright (C) 2004-2014 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">
1N/A<
title>nsupdate</
title>
1N/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">
1N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
1N/A<
div class="navheader">
1N/A<
table width="100%" summary="Navigation header">
1N/A<
tr><
th colspan="3" align="center"><
span class="application">nsupdate</
span></
th></
tr>
1N/A<
td width="20%" align="left">
1N/A<
th width="60%" align="center">Manual pages</
th>
1N/A<
div class="refentry" lang="en">
1N/A<
div class="refnamediv">
1N/A<
p><
span class="application">nsupdate</
span> — Dynamic DNS update utility</
p>
1N/A<
div class="refsynopsisdiv">
1N/A<
div class="cmdsynopsis"><
p><
code class="command">nsupdate</
code> [<
code class="option">-d</
code>] [<
code class="option">-D</
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>
1N/A<
div class="refsect1" lang="en">
1N/A<
a name="id2655941"></
a><
h2>DESCRIPTION</
h2>
1N/A<
p><
span><
strong class="command">nsupdate</
strong></
span>
1N/A is used to submit Dynamic DNS Update requests as defined in RFC 2136
1N/A This allows resource records to be added or removed from a zone
1N/A without manually editing the zone file.
1N/A A single update request can contain requests to add or remove more than
1N/A Zones that are under dynamic control via
1N/A <
span><
strong class="command">nsupdate</
strong></
span>
1N/A or a DHCP server should not be edited by hand.
1N/A conflict with dynamic updates and cause data to be lost.
1N/A The resource records that are dynamically added or removed with
1N/A <
span><
strong class="command">nsupdate</
strong></
span>
1N/A have to be in the same zone.
1N/A Requests are sent to the zone's master server.
1N/A This is identified by the MNAME field of the zone's SOA record.
1N/A <
code class="option">-d</
code>
1N/A <
span><
strong class="command">nsupdate</
strong></
span>
1N/A operate in debug mode.
1N/A This provides tracing information about the update requests that are
1N/A made and the replies received from the name server.
1N/A The <
code class="option">-D</
code> option makes <
span><
strong class="command">nsupdate</
strong></
span>
1N/A report additional debugging information to <
code class="option">-d</
code>.
1N/A The <
code class="option">-L</
code> option with an integer argument of zero or
1N/A higher sets the logging debug level. If zero, logging is disabled.
1N/A Transaction signatures can be used to authenticate the Dynamic
1N/A DNS updates. These use the TSIG resource record type described
1N/A in RFC 2845 or the SIG(0) record described in RFC 2535 and
1N/A RFC 2931 or GSS-TSIG as described in RFC 3645. TSIG relies on
1N/A a shared secret that should only be known to
1N/A <
span><
strong class="command">nsupdate</
strong></
span> and the name server. Currently,
1N/A the only supported encryption algorithm for TSIG is HMAC-MD5,
1N/A which is defined in RFC 2104. Once other algorithms are
1N/A defined for TSIG, applications will need to ensure they select
1N/A the appropriate algorithm as well as the key when authenticating
1N/A each other. For instance, suitable <
span class="type">key</
span> and
1N/A <
span class="type">server</
span> statements would be added to
1N/A can associate the appropriate secret key and algorithm with
1N/A the IP address of the client application that will be using
1N/A TSIG authentication. SIG(0) uses public key cryptography.
1N/A To use a SIG(0) key, the public key must be stored in a KEY
1N/A record in a zone served by the name server.
1N/A <
span><
strong class="command">nsupdate</
strong></
span> does not read
1N/A GSS-TSIG uses Kerberos credentials. Standard GSS-TSIG mode
1N/A is switched on with the <
code class="option">-g</
code> flag. A
1N/A non-standards-compliant variant of GSS-TSIG used by Windows
1N/A 2000 can be switched on with the <
code class="option">-o</
code> flag.
1N/A<
p><
span><
strong class="command">nsupdate</
strong></
span>
1N/A uses the <
code class="option">-y</
code> or <
code class="option">-k</
code> option
1N/A to provide the shared secret needed to generate a TSIG record
1N/A for authenticating Dynamic DNS update requests, default type
1N/A HMAC-MD5. These options are mutually exclusive.
1N/A When the <
code class="option">-y</
code> option is used, a signature is
1N/A [<
span class="optional"><
em class="parameter"><
code>hmac:</
code></
em></
span>]<
em class="parameter"><
code>keyname:secret.</
code></
em>
1N/A <
em class="parameter"><
code>keyname</
code></
em> is the name of the key, and
1N/A <
em class="parameter"><
code>secret</
code></
em> is the base64 encoded shared secret.
1N/A <
em class="parameter"><
code>hmac</
code></
em> is the name of the key algorithm;
1N/A valid choices are <
code class="literal">hmac-md5</
code>,
1N/A <
code class="literal">hmac-sha1</
code>, <
code class="literal">hmac-sha224</
code>,
1N/A <
code class="literal">hmac-sha256</
code>, <
code class="literal">hmac-sha384</
code>, or
1N/A <
code class="literal">hmac-sha512</
code>. If <
em class="parameter"><
code>hmac</
code></
em>
1N/A is not specified, the default is <
code class="literal">hmac-md5</
code>.
1N/A NOTE: Use of the <
code class="option">-y</
code> option is discouraged because the
1N/A shared secret is supplied as a command line argument in clear text.
1N/A This may be visible in the output from
1N/A <
span class="citerefentry"><
span class="refentrytitle">ps</
span>(1)</
span>
1N/A or in a history file maintained by the user's shell.
1N/A <
code class="option">-k</
code> option, <
span><
strong class="command">nsupdate</
strong></
span> reads
1N/A the shared secret from the file <
em class="parameter"><
code>keyfile</
code></
em>.
1N/A Keyfiles may be in two formats: a single file containing
1N/A a <
code class="filename">
named.conf</
code>-format <
span><
strong class="command">key</
strong></
span>
1N/A statement, which may be generated automatically by
1N/A <
span><
strong class="command">ddns-confgen</
strong></
span>, or a pair of files whose names are
1N/A of the format <
code class="filename">K{name}.+157.+{random}.key</
code> and
1N/A <
code class="filename">K{name}.+157.+{random}.private</
code>, which can be
1N/A generated by <
span><
strong class="command">dnssec-keygen</
strong></
span>.
1N/A The <
code class="option">-k</
code> may also be used to specify a SIG(0) key used
1N/A to authenticate Dynamic DNS update requests. In this case, the key
1N/A specified is not an HMAC-MD5 key.
1N/A <
span><
strong class="command">nsupdate</
strong></
span> can be run in a local-host only mode
1N/A using the <
code class="option">-l</
code> flag. This sets the server address to
1N/A localhost (disabling the <
span><
strong class="command">server</
strong></
span> so that the server
1N/A address cannot be overridden). Connections to the local server will
1N/A which is automatically generated by <
span><
strong class="command">named</
strong></
span> if any
1N/A local master zone has set <
span><
strong class="command">update-policy</
strong></
span> to
1N/A <
span><
strong class="command">local</
strong></
span>. The location of this key file can be
1N/A overridden with the <
code class="option">-k</
code> option.
1N/A By default, <
span><
strong class="command">nsupdate</
strong></
span>
1N/A uses UDP to send update requests to the name server unless they are too
1N/A large to fit in a UDP request in which case TCP will be used.
1N/A <
code class="option">-v</
code>
1N/A <
span><
strong class="command">nsupdate</
strong></
span>
1N/A use a TCP connection.
1N/A This may be preferable when a batch of update requests is made.
1N/A The <
code class="option">-p</
code> sets the default port number to use for
1N/A connections to a name server. The default is 53.
1N/A The <
code class="option">-t</
code> option sets the maximum time an update request
1N/A take before it is aborted. The default is 300 seconds. Zero can be
1N/A to disable the timeout.
1N/A The <
code class="option">-u</
code> option sets the UDP retry interval. The default
1N/A 3 seconds. If zero, the interval will be computed from the timeout
1N/A and number of UDP retries.
1N/A The <
code class="option">-r</
code> option sets the number of UDP retries. The
1N/A 3. If zero, only one update request will be made.
1N/A The <
code class="option">-R <
em class="replaceable"><
code>randomdev</
code></
em></
code> option
1N/A specifies a source of randomness. If the operating system
1N/A does not provide a <
code class="filename">/
dev/
random</
code> or
1N/A equivalent device, the default source of randomness is keyboard
1N/A input. <
code class="filename">randomdev</
code> specifies the name of
1N/A a character device or file containing random data to be used
1N/A instead of the default. The special value
1N/A <
code class="filename">keyboard</
code> indicates that keyboard input
1N/A should be used. This option may be specified multiple times.
1N/A Other types can be entered using "TYPEXXXXX" where "XXXXX" is the
1N/A decimal value of the type with no leading zeros. The rdata,
1N/A if present, will be parsed using the UNKNOWN rdata format,
1N/A (<backslash> <hash> <space> <length>
1N/A <space> <hexstring>).
1N/A The <
code class="option">-T</
code> and <
code class="option">-P</
code> options print out
1N/A lists of non-meta types for which the type-specific presentation
1N/A formats are known. <
code class="option">-T</
code> prints out the list of
1N/A IANA-assigned types. <
code class="option">-P</
code> prints out the list of
1N/A private types specific to <
span><
strong class="command">named</
strong></
span>. These options
1N/A may be combined. <
span><
strong class="command">nsupdate</
strong></
span> will exit after the
1N/A The -V option causes <
span><
strong class="command">nsupdate</
strong></
span> to print the
1N/A version number and exit.
1N/A<
div class="refsect1" lang="en">
1N/A<
a name="id2681491"></
a><
h2>INPUT FORMAT</
h2>
1N/A<
p><
span><
strong class="command">nsupdate</
strong></
span>
1N/A <
em class="parameter"><
code>filename</
code></
em>
1N/A Each command is supplied on exactly one line of input.
1N/A Some commands are for administrative purposes.
1N/A The others are either update instructions or prerequisite checks on the
1N/A contents of the zone.
1N/A These checks set conditions that some name or set of
1N/A resource records (RRset) either exists or is absent from the zone.
1N/A These conditions must be met if the entire update request is to succeed.
1N/A Updates will be rejected if the tests for the prerequisite conditions
1N/A Every update request consists of zero or more prerequisites
1N/A and zero or more updates.
1N/A This allows a suitably authenticated update request to proceed if some
1N/A specified resource records are present or missing from the zone.
1N/A A blank input line (or the <
span><
strong class="command">send</
strong></
span> command)
1N/A accumulated commands to be sent as one Dynamic DNS update request to the
1N/A The command formats and their meaning are as follows:
1N/A<
div class="variablelist"><
dl>
1N/A<
dt><
span class="term">
1N/A <
span><
strong class="command">server</
strong></
span>
1N/A Sends all dynamic update requests to the name server
1N/A <
em class="parameter"><
code>servername</
code></
em>.
1N/A When no server statement is provided,
1N/A <
span><
strong class="command">nsupdate</
strong></
span>
1N/A will send updates to the master server of the correct zone.
1N/A The MNAME field of that zone's SOA record will identify the
1N/A server for that zone.
1N/A <
em class="parameter"><
code>port</
code></
em>
1N/A is the port number on
1N/A <
em class="parameter"><
code>servername</
code></
em>
1N/A where the dynamic update requests get sent.
1N/A If no port number is specified, the default DNS port number of
1N/A<
dt><
span class="term">
1N/A <
span><
strong class="command">local</
strong></
span>
1N/A Sends all dynamic update requests using the local
1N/A <
em class="parameter"><
code>address</
code></
em>.
1N/A When no local statement is provided,
1N/A <
span><
strong class="command">nsupdate</
strong></
span>
1N/A will send updates using an address and port chosen by the
1N/A <
em class="parameter"><
code>port</
code></
em>
1N/A can additionally be used to make requests come from a specific
1N/A If no port number is specified, the system will assign one.
1N/A<
dt><
span class="term">
1N/A <
span><
strong class="command">zone</
strong></
span>
1N/A Specifies that all updates are to be made to the zone
1N/A <
em class="parameter"><
code>zonename</
code></
em>.
1N/A <
em class="parameter"><
code>zone</
code></
em>
1N/A statement is provided,
1N/A <
span><
strong class="command">nsupdate</
strong></
span>
1N/A will attempt determine the correct zone to update based on the
1N/A<
dt><
span class="term">
1N/A <
span><
strong class="command">class</
strong></
span>
Specify the default class.
If no <
em class="parameter"><
code>class</
code></
em> is specified, the
<
em class="parameter"><
code>IN</
code></
em>.
<
span><
strong class="command">ttl</
strong></
span>
Specify the default time to live for records to be added.
The value <
em class="parameter"><
code>none</
code></
em> will clear the default
<
span><
strong class="command">key</
strong></
span>
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><
strong class="command">key</
strong></
span>
command overrides any key specified on the command line via
<
code class="option">-y</
code> or <
code class="option">-k</
code>.
<
span><
strong class="command">gsstsig</
strong></
span>
Use GSS-TSIG to sign the updated. This is equivalent to
specifying <
code class="option">-g</
code> on the commandline.
<
span><
strong class="command">oldgsstsig</
strong></
span>
Use the Windows 2000 version of GSS-TSIG to sign the updated.
This is equivalent to specifying <
code class="option">-o</
code> on the
<
span><
strong class="command">realm</
strong></
span>
{[<
span class="optional">realm_name</
span>]}
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.
<
span><
strong class="command">check-names</
strong></
span>
{[<
span class="optional">yes_or_no</
span>]}
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.
<
span><
strong class="command">[<
span class="optional">prereq</
span>] nxdomain</
strong></
span>
Requires that no resource record of any type exists with name
<
em class="parameter"><
code>domain-name</
code></
em>.
<
span><
strong class="command">[<
span class="optional">prereq</
span>] yxdomain</
strong></
span>
<
em class="parameter"><
code>domain-name</
code></
em>
exists (has as at least one resource record, of any type).
<
span><
strong class="command">[<
span class="optional">prereq</
span>] nxrrset</
strong></
span>
Requires that no resource record exists of the specified
<
em class="parameter"><
code>type</
code></
em>,
<
em class="parameter"><
code>class</
code></
em>
<
em class="parameter"><
code>domain-name</
code></
em>.
<
em class="parameter"><
code>class</
code></
em>
is omitted, IN (internet) is assumed.
<
span><
strong class="command">[<
span class="optional">prereq</
span>] yxrrset</
strong></
span>
This requires that a resource record of the specified
<
em class="parameter"><
code>type</
code></
em>,
<
em class="parameter"><
code>class</
code></
em>
<
em class="parameter"><
code>domain-name</
code></
em>
<
em class="parameter"><
code>class</
code></
em>
is omitted, IN (internet) is assumed.
<
span><
strong class="command">[<
span class="optional">prereq</
span>] yxrrset</
strong></
span>
<
em class="parameter"><
code>data</
code></
em>
from each set of prerequisites of this form
<
em class="parameter"><
code>type</
code></
em>,
<
em class="parameter"><
code>class</
code></
em>,
<
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
<
em class="parameter"><
code>type</
code></
em>,
<
em class="parameter"><
code>class</
code></
em>,
<
em class="parameter"><
code>domain-name</
code></
em>.
<
em class="parameter"><
code>data</
code></
em>
are written in the standard text representation of the resource
<
span><
strong class="command">[<
span class="optional">update</
span>] del[<
span class="optional">ete</
span>]</
strong></
span>
Deletes any resource records named
<
em class="parameter"><
code>domain-name</
code></
em>.
<
em class="parameter"><
code>type</
code></
em>
<
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>
<
em class="parameter"><
code>ttl</
code></
em>
is ignored, and is only allowed for compatibility.
<
span><
strong class="command">[<
span class="optional">update</
span>] add</
strong></
span>
Adds a new resource record with the specified
<
em class="parameter"><
code>ttl</
code></
em>,
<
em class="parameter"><
code>class</
code></
em>
<
em class="parameter"><
code>data</
code></
em>.
<
span><
strong class="command">show</
strong></
span>
Displays the current message, containing all of the
updates specified since the last send.
<
span><
strong class="command">send</
strong></
span>
Sends the current message. This is equivalent to entering a
<
span><
strong class="command">answer</
strong></
span>
<
span><
strong class="command">debug</
strong></
span>
<
span><
strong class="command">version</
strong></
span>
<
span><
strong class="command">help</
strong></
span>
Print a list of commands.
Lines beginning with a semicolon are comments and are ignored.
<
div class="refsect1" lang="en">
<
a name="id2682638"></
a><
h2>EXAMPLES</
h2>
The examples below show how
<
span><
strong class="command">nsupdate</
strong></
span>
could be used to insert and delete resource records from the
Notice that the input in each example contains a trailing blank line so
a group of commands are sent as one dynamic update request to the
<
pre class="programlisting">
with IP address 172.16.1.1 is added.
The newly-added record has a 1 day TTL (86400 seconds).
<
pre class="programlisting">
The prerequisite condition gets the name server to check that there
are no resource records of any type for
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.)
<
div class="refsect1" lang="en">
<
a name="id2682689"></
a><
h2>FILES</
h2>
<
div class="variablelist"><
dl>
<
dt><
span class="term"><
code class="constant">/
etc/
resolv.conf</
code></
span></
dt>
used to identify default name server
sets the default TSIG key for use in local-only mode
<
dt><
span class="term"><
code class="constant">K{name}.+157.+{random}.key</
code></
span></
dt>
base-64 encoding of HMAC-MD5 key created by
<
span class="citerefentry"><
span class="refentrytitle">dnssec-keygen</
span>(8)</
span>.
<
dt><
span class="term"><
code class="constant">K{name}.+157.+{random}.private</
code></
span></
dt>
base-64 encoding of HMAC-MD5 key created by
<
span class="citerefentry"><
span class="refentrytitle">dnssec-keygen</
span>(8)</
span>.
<
div class="refsect1" lang="en">
<
a name="id2682840"></
a><
h2>SEE ALSO</
h2>
<
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>.
<
div class="refsect1" lang="en">
<
a name="id2682966"></
a><
h2>BUGS</
h2>
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
<
table width="100%" summary="Navigation footer">
<
td width="40%" align="left">
<
td width="20%" align="center"><
a accesskey="u" href="Bv9ARM.ch10.html">Up</
a></
td>
<
td width="40%" align="right">�<
a accesskey="n" href="man.rndc.html">Next</
a>
<
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>
<
p style="text-align: center;">BIND 9.11.0pre-alpha</
p>