man.nsupdate.html revision 610cd6f8458d88d5696e131aee310dcbcebac8fd
3853N/A<!--
3853N/A - Copyright (C) 2004-2011 Internet Systems Consortium, Inc. ("ISC")
3853N/A - Copyright (C) 2000-2003 Internet Software Consortium.
3853N/A -
3853N/A - Permission to use, copy, modify, and/or distribute this software for any
3853N/A - purpose with or without fee is hereby granted, provided that the above
3853N/A - copyright notice and this permission notice appear in all copies.
3853N/A -
3853N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
3853N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
3853N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
3853N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
3853N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
3853N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
3853N/A - PERFORMANCE OF THIS SOFTWARE.
3853N/A-->
3853N/A<!-- $Id: man.nsupdate.html,v 1.108 2011/01/07 01:13:02 tbox Exp $ -->
3853N/A<html>
3853N/A<head>
3853N/A<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
3853N/A<title>nsupdate</title>
3853N/A<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
3853N/A<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
3853N/A<link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
5035N/A<link rel="prev" href="man.named-journalprint.html" title="named-journalprint">
3853N/A<link rel="next" href="man.rndc.html" title="rndc">
3853N/A</head>
3853N/A<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
3853N/A<div class="navheader">
3853N/A<table width="100%" summary="Navigation header">
4803N/A<tr><th colspan="3" align="center"><span class="application">nsupdate</span></th></tr>
3853N/A<tr>
3853N/A<td width="20%" align="left">
3853N/A<a accesskey="p" href="man.named-journalprint.html">Prev</a>�</td>
4141N/A<th width="60%" align="center">Manual pages</th>
3853N/A<td width="20%" align="right">�<a accesskey="n" href="man.rndc.html">Next</a>
3853N/A</td>
3853N/A</tr>
3853N/A</table>
3853N/A<hr>
4141N/A</div>
3898N/A<div class="refentry" lang="en">
3898N/A<a name="man.nsupdate"></a><div class="titlepage"></div>
4920N/A<div class="refnamediv">
4518N/A<h2>Name</h2>
3853N/A<p><span class="application">nsupdate</span> &#8212; Dynamic DNS update utility</p>
3853N/A</div>
3853N/A<div class="refsynopsisdiv">
3853N/A<h2>Synopsis</h2>
4803N/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>] [filename]</p></div>
3853N/A</div>
3853N/A<div class="refsect1" lang="en">
3853N/A<a name="id2638403"></a><h2>DESCRIPTION</h2>
3853N/A<p><span><strong class="command">nsupdate</strong></span>
3853N/A is used to submit Dynamic DNS Update requests as defined in RFC 2136
3853N/A to a name server.
3853N/A This allows resource records to be added or removed from a zone
3853N/A without manually editing the zone file.
3853N/A A single update request can contain requests to add or remove more than
3853N/A one
3853N/A resource record.
3853N/A </p>
3853N/A<p>
3853N/A Zones that are under dynamic control via
3853N/A <span><strong class="command">nsupdate</strong></span>
4803N/A or a DHCP server should not be edited by hand.
4803N/A Manual edits could
3853N/A conflict with dynamic updates and cause data to be lost.
3853N/A </p>
3853N/A<p>
3853N/A The resource records that are dynamically added or removed with
3853N/A <span><strong class="command">nsupdate</strong></span>
3853N/A have to be in the same zone.
3853N/A Requests are sent to the zone's master server.
3853N/A This is identified by the MNAME field of the zone's SOA record.
4141N/A </p>
4141N/A<p>
4141N/A The
4141N/A <code class="option">-d</code>
4141N/A option makes
4141N/A <span><strong class="command">nsupdate</strong></span>
4141N/A operate in debug mode.
4141N/A This provides tracing information about the update requests that are
4141N/A made and the replies received from the name server.
4141N/A </p>
4518N/A<p>
4518N/A The <code class="option">-D</code> option makes <span><strong class="command">nsupdate</strong></span>
4141N/A report additional debugging information to <code class="option">-d</code>.
4141N/A </p>
3853N/A<p>
3853N/A The <code class="option">-L</code> option with an integer argument of zero or
4920N/A higher sets the logging debug level. If zero, logging is disabled.
3853N/A </p>
4500N/A<p>
4500N/A Transaction signatures can be used to authenticate the Dynamic
4500N/A DNS updates. These use the TSIG resource record type described
4500N/A in RFC 2845 or the SIG(0) record described in RFC 2535 and
3853N/A RFC 2931 or GSS-TSIG as described in RFC 3645. TSIG relies on
3853N/A a shared secret that should only be known to
3853N/A <span><strong class="command">nsupdate</strong></span> and the name server. Currently,
3853N/A the only supported encryption algorithm for TSIG is HMAC-MD5,
3853N/A which is defined in RFC 2104. Once other algorithms are
3853N/A defined for TSIG, applications will need to ensure they select
3853N/A the appropriate algorithm as well as the key when authenticating
3853N/A each other. For instance, suitable <span class="type">key</span> and
3853N/A <span class="type">server</span> statements would be added to
3853N/A <code class="filename">/etc/named.conf</code> so that the name server
3853N/A can associate the appropriate secret key and algorithm with
3853N/A the IP address of the client application that will be using
3853N/A TSIG authentication. SIG(0) uses public key cryptography.
3853N/A To use a SIG(0) key, the public key must be stored in a KEY
3853N/A record in a zone served by the name server.
3853N/A <span><strong class="command">nsupdate</strong></span> does not read
3853N/A <code class="filename">/etc/named.conf</code>.
3853N/A </p>
3853N/A<p>
3853N/A GSS-TSIG uses Kerberos credentials. Standard GSS-TSIG mode
3853N/A is switched on with the <code class="option">-g</code> flag. A
3853N/A non-standards-compliant variant of GSS-TSIG used by Windows
3853N/A 2000 can be switched on with the <code class="option">-o</code> flag.
4500N/A </p>
4500N/A<p><span><strong class="command">nsupdate</strong></span>
4500N/A uses the <code class="option">-y</code> or <code class="option">-k</code> option
4500N/A to provide the shared secret needed to generate a TSIG record
3853N/A for authenticating Dynamic DNS update requests, default type
3853N/A HMAC-MD5. These options are mutually exclusive.
3853N/A </p>
3853N/A<p>
3853N/A When the <code class="option">-y</code> option is used, a signature is
3853N/A generated from
3853N/A [<span class="optional"><em class="parameter"><code>hmac:</code></em></span>]<em class="parameter"><code>keyname:secret.</code></em>
3853N/A <em class="parameter"><code>keyname</code></em> is the name of the key, and
3853N/A <em class="parameter"><code>secret</code></em> is the base64 encoded shared secret.
3853N/A Use of the <code class="option">-y</code> option is discouraged because the
3853N/A shared secret is supplied as a command line argument in clear text.
3853N/A This may be visible in the output from
3853N/A <span class="citerefentry"><span class="refentrytitle">ps</span>(1)</span>
3853N/A or in a history file maintained by the user's shell.
3853N/A </p>
3853N/A<p>
3853N/A With the
3853N/A <code class="option">-k</code> option, <span><strong class="command">nsupdate</strong></span> reads
3858N/A the shared secret from the file <em class="parameter"><code>keyfile</code></em>.
3853N/A Keyfiles may be in two formats: a single file containing
3853N/A a <code class="filename">named.conf</code>-format <span><strong class="command">key</strong></span>
3853N/A statement, which may be generated automatically by
3853N/A <span><strong class="command">ddns-confgen</strong></span>, or a pair of files whose names are
3853N/A of the format <code class="filename">K{name}.+157.+{random}.key</code> and
3853N/A <code class="filename">K{name}.+157.+{random}.private</code>, which can be
3853N/A generated by <span><strong class="command">dnssec-keygen</strong></span>.
3853N/A The <code class="option">-k</code> may also be used to specify a SIG(0) key used
3858N/A to authenticate Dynamic DNS update requests. In this case, the key
3853N/A specified is not an HMAC-MD5 key.
3853N/A </p>
3853N/A<p>
3853N/A <span><strong class="command">nsupdate</strong></span> can be run in a local-host only mode
3853N/A using the <code class="option">-l</code> flag. This sets the server address to
3853N/A localhost (disabling the <span><strong class="command">server</strong></span> so that the server
3853N/A address cannot be overridden). Connections to the local server will
3853N/A use a TSIG key found in <code class="filename">/var/run/named/session.key</code>,
3853N/A which is automatically generated by <span><strong class="command">named</strong></span> if any
3853N/A local master zone has set <span><strong class="command">update-policy</strong></span> to
3853N/A <span><strong class="command">local</strong></span>. The location of this key file can be
3853N/A overridden with the <code class="option">-k</code> option.
3853N/A </p>
3853N/A<p>
3853N/A By default, <span><strong class="command">nsupdate</strong></span>
3853N/A uses UDP to send update requests to the name server unless they are too
3853N/A large to fit in a UDP request in which case TCP will be used.
3853N/A The
3853N/A <code class="option">-v</code>
3853N/A option makes
3853N/A <span><strong class="command">nsupdate</strong></span>
3853N/A use a TCP connection.
3853N/A This may be preferable when a batch of update requests is made.
4060N/A </p>
4060N/A<p>
4060N/A The <code class="option">-p</code> sets the default port number to use for
4060N/A connections to a name server. The default is 53.
4060N/A </p>
4803N/A<p>
4060N/A The <code class="option">-t</code> option sets the maximum time an update request
4060N/A can
4060N/A take before it is aborted. The default is 300 seconds. Zero can be
4060N/A used
4060N/A to disable the timeout.
4060N/A </p>
4060N/A<p>
4060N/A The <code class="option">-u</code> option sets the UDP retry interval. The default
4060N/A is
4060N/A 3 seconds. If zero, the interval will be computed from the timeout
4803N/A interval
4060N/A and number of UDP retries.
4060N/A </p>
4060N/A<p>
4060N/A The <code class="option">-r</code> option sets the number of UDP retries. The
4060N/A default is
3853N/A 3. If zero, only one update request will be made.
3853N/A </p>
3853N/A<p>
4803N/A The <code class="option">-R <em class="replaceable"><code>randomdev</code></em></code> option
3853N/A specifies a source of randomness. If the operating system
3853N/A does not provide a <code class="filename">/dev/random</code> or
3853N/A equivalent device, the default source of randomness is keyboard
3853N/A input. <code class="filename">randomdev</code> specifies the name of
3853N/A a character device or file containing random data to be used
3853N/A instead of the default. The special value
3853N/A <code class="filename">keyboard</code> indicates that keyboard input
3853N/A should be used. This option may be specified multiple times.
4803N/A </p>
3853N/A</div>
3853N/A<div class="refsect1" lang="en">
3853N/A<a name="id2639488"></a><h2>INPUT FORMAT</h2>
3853N/A<p><span><strong class="command">nsupdate</strong></span>
3853N/A reads input from
4803N/A <em class="parameter"><code>filename</code></em>
4803N/A or standard input.
4803N/A Each command is supplied on exactly one line of input.
4803N/A Some commands are for administrative purposes.
4803N/A The others are either update instructions or prerequisite checks on the
4803N/A contents of the zone.
4803N/A These checks set conditions that some name or set of
4803N/A resource records (RRset) either exists or is absent from the zone.
4803N/A These conditions must be met if the entire update request is to succeed.
4803N/A Updates will be rejected if the tests for the prerequisite conditions
4803N/A fail.
4803N/A </p>
4803N/A<p>
4803N/A Every update request consists of zero or more prerequisites
4803N/A and zero or more updates.
4803N/A This allows a suitably authenticated update request to proceed if some
4803N/A specified resource records are present or missing from the zone.
4803N/A A blank input line (or the <span><strong class="command">send</strong></span> command)
4803N/A causes the
4803N/A accumulated commands to be sent as one Dynamic DNS update request to the
4803N/A name server.
4803N/A </p>
4803N/A<p>
4803N/A The command formats and their meaning are as follows:
4803N/A </p>
4803N/A<div class="variablelist"><dl>
4803N/A<dt><span class="term">
4803N/A <span><strong class="command">server</strong></span>
4803N/A {servername}
4803N/A [port]
4803N/A </span></dt>
4803N/A<dd><p>
4803N/A Sends all dynamic update requests to the name server
4803N/A <em class="parameter"><code>servername</code></em>.
4803N/A When no server statement is provided,
4803N/A <span><strong class="command">nsupdate</strong></span>
4803N/A will send updates to the master server of the correct zone.
3853N/A The MNAME field of that zone's SOA record will identify the
3853N/A master
3853N/A server for that zone.
3853N/A <em class="parameter"><code>port</code></em>
3853N/A is the port number on
3853N/A <em class="parameter"><code>servername</code></em>
3853N/A where the dynamic update requests get sent.
3853N/A If no port number is specified, the default DNS port number of
3853N/A 53 is
3853N/A used.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">local</strong></span>
3853N/A {address}
3853N/A [port]
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Sends all dynamic update requests using the local
3853N/A <em class="parameter"><code>address</code></em>.
3853N/A
3853N/A When no local statement is provided,
3853N/A <span><strong class="command">nsupdate</strong></span>
3853N/A will send updates using an address and port chosen by the
3853N/A system.
3853N/A <em class="parameter"><code>port</code></em>
3853N/A can additionally be used to make requests come from a specific
3853N/A port.
3853N/A If no port number is specified, the system will assign one.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">zone</strong></span>
3853N/A {zonename}
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Specifies that all updates are to be made to the zone
3853N/A <em class="parameter"><code>zonename</code></em>.
3853N/A If no
3853N/A <em class="parameter"><code>zone</code></em>
3853N/A statement is provided,
3853N/A <span><strong class="command">nsupdate</strong></span>
3853N/A will attempt determine the correct zone to update based on the
3853N/A rest of the input.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">class</strong></span>
3853N/A {classname}
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Specify the default class.
3853N/A If no <em class="parameter"><code>class</code></em> is specified, the
3853N/A default class is
3853N/A <em class="parameter"><code>IN</code></em>.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">ttl</strong></span>
3853N/A {seconds}
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Specify the default time to live for records to be added.
3853N/A The value <em class="parameter"><code>none</code></em> will clear the default
3853N/A ttl.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">key</strong></span>
3853N/A {name}
3853N/A {secret}
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Specifies that all updates are to be TSIG-signed using the
3853N/A <em class="parameter"><code>keyname</code></em> <em class="parameter"><code>keysecret</code></em> pair.
3853N/A The <span><strong class="command">key</strong></span> command
3853N/A overrides any key specified on the command line via
4518N/A <code class="option">-y</code> or <code class="option">-k</code>.
4518N/A </p></dd>
4518N/A<dt><span class="term">
4518N/A <span><strong class="command">gsstsig</strong></span>
4518N/A </span></dt>
4518N/A<dd><p>
4518N/A Use GSS-TSIG to sign the updated. This is equivalent to
4518N/A specifying <code class="option">-g</code> on the commandline.
4518N/A </p></dd>
4518N/A<dt><span class="term">
4518N/A <span><strong class="command">oldgsstsig</strong></span>
4518N/A </span></dt>
4518N/A<dd><p>
4518N/A Use the Windows 2000 version of GSS-TSIG to sign the updated.
4518N/A This is equivalent to specifying <code class="option">-o</code> on the
4518N/A commandline.
4518N/A </p></dd>
4518N/A<dt><span class="term">
3853N/A <span><strong class="command">realm</strong></span>
3853N/A {[<span class="optional">realm_name</span>]}
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A When using GSS-TSIG use <em class="parameter"><code>realm_name</code></em> rather
3853N/A than the default realm in <code class="filename">krb5.conf</code>. If no
3853N/A realm is specified the saved realm is cleared.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">prereq nxdomain</strong></span>
3853N/A {domain-name}
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Requires that no resource record of any type exists with name
4500N/A <em class="parameter"><code>domain-name</code></em>.
4500N/A </p></dd>
4500N/A<dt><span class="term">
4500N/A <span><strong class="command">prereq yxdomain</strong></span>
4500N/A {domain-name}
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Requires that
3853N/A <em class="parameter"><code>domain-name</code></em>
3853N/A exists (has as at least one resource record, of any type).
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">prereq nxrrset</strong></span>
3853N/A {domain-name}
3853N/A [class]
4500N/A {type}
4500N/A </span></dt>
4500N/A<dd><p>
4500N/A Requires that no resource record exists of the specified
4500N/A <em class="parameter"><code>type</code></em>,
4500N/A <em class="parameter"><code>class</code></em>
4500N/A and
4500N/A <em class="parameter"><code>domain-name</code></em>.
3853N/A If
3853N/A <em class="parameter"><code>class</code></em>
3853N/A is omitted, IN (internet) is assumed.
3853N/A </p></dd>
4500N/A<dt><span class="term">
4500N/A <span><strong class="command">prereq yxrrset</strong></span>
4500N/A {domain-name}
4500N/A [class]
4500N/A {type}
4500N/A </span></dt>
4500N/A<dd><p>
4500N/A This requires that a resource record of the specified
4060N/A <em class="parameter"><code>type</code></em>,
4060N/A <em class="parameter"><code>class</code></em>
4060N/A and
4060N/A <em class="parameter"><code>domain-name</code></em>
3853N/A must exist.
3853N/A If
3853N/A <em class="parameter"><code>class</code></em>
3853N/A is omitted, IN (internet) is assumed.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">prereq yxrrset</strong></span>
3853N/A {domain-name}
3853N/A [class]
3853N/A {type}
3853N/A {data...}
3853N/A </span></dt>
4500N/A<dd><p>
4500N/A The
4500N/A <em class="parameter"><code>data</code></em>
4500N/A from each set of prerequisites of this form
4500N/A sharing a common
4500N/A <em class="parameter"><code>type</code></em>,
4500N/A <em class="parameter"><code>class</code></em>,
4500N/A and
3853N/A <em class="parameter"><code>domain-name</code></em>
3853N/A are combined to form a set of RRs. This set of RRs must
3853N/A exactly match the set of RRs existing in the zone at the
3853N/A given
3853N/A <em class="parameter"><code>type</code></em>,
3853N/A <em class="parameter"><code>class</code></em>,
3853N/A and
3853N/A <em class="parameter"><code>domain-name</code></em>.
3853N/A The
3853N/A <em class="parameter"><code>data</code></em>
3853N/A are written in the standard text representation of the resource
3853N/A record's
3853N/A RDATA.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">update delete</strong></span>
3853N/A {domain-name}
3853N/A [ttl]
3853N/A [class]
3853N/A [type [data...]]
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Deletes any resource records named
3853N/A <em class="parameter"><code>domain-name</code></em>.
3853N/A If
3853N/A <em class="parameter"><code>type</code></em>
3853N/A and
3853N/A <em class="parameter"><code>data</code></em>
3853N/A is provided, only matching resource records will be removed.
3853N/A The internet class is assumed if
3853N/A <em class="parameter"><code>class</code></em>
3853N/A is not supplied. The
3853N/A <em class="parameter"><code>ttl</code></em>
3853N/A is ignored, and is only allowed for compatibility.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">update add</strong></span>
3853N/A {domain-name}
3853N/A {ttl}
3853N/A [class]
3853N/A {type}
3853N/A {data...}
3853N/A </span></dt>
3898N/A<dd><p>
3898N/A Adds a new resource record with the specified
3898N/A <em class="parameter"><code>ttl</code></em>,
3898N/A <em class="parameter"><code>class</code></em>
3898N/A and
3898N/A <em class="parameter"><code>data</code></em>.
4518N/A </p></dd>
4518N/A<dt><span class="term">
4518N/A <span><strong class="command">show</strong></span>
4518N/A </span></dt>
4518N/A<dd><p>
3853N/A Displays the current message, containing all of the
3853N/A prerequisites and
3853N/A updates specified since the last send.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">send</strong></span>
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Sends the current message. This is equivalent to entering a
3853N/A blank line.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">answer</strong></span>
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Displays the answer.
3853N/A </p></dd>
3853N/A<dt><span class="term">
3853N/A <span><strong class="command">debug</strong></span>
3853N/A </span></dt>
3853N/A<dd><p>
3853N/A Turn on debugging.
3853N/A </p></dd>
3853N/A</dl></div>
3853N/A<p>
3853N/A </p>
3853N/A<p>
3853N/A Lines beginning with a semicolon are comments and are ignored.
3853N/A </p>
3853N/A</div>
3853N/A<div class="refsect1" lang="en">
3853N/A<a name="id2675216"></a><h2>EXAMPLES</h2>
3853N/A<p>
3853N/A The examples below show how
3853N/A <span><strong class="command">nsupdate</strong></span>
3853N/A could be used to insert and delete resource records from the
3853N/A <span class="type">example.com</span>
3853N/A zone.
3853N/A Notice that the input in each example contains a trailing blank line so
3853N/A that
3853N/A a group of commands are sent as one dynamic update request to the
3853N/A master name server for
3853N/A <span class="type">example.com</span>.
3853N/A
3853N/A </p>
3853N/A<pre class="programlisting">
3853N/A# nsupdate
3853N/A&gt; update delete oldhost.example.com A
3853N/A&gt; update add newhost.example.com 86400 A 172.16.1.1
3858N/A&gt; send
3853N/A</pre>
3853N/A<p>
3853N/A </p>
3853N/A<p>
3853N/A Any A records for
3853N/A <span class="type">oldhost.example.com</span>
3853N/A are deleted.
3853N/A And an A record for
3858N/A <span class="type">newhost.example.com</span>
3853N/A with IP address 172.16.1.1 is added.
3853N/A The newly-added record has a 1 day TTL (86400 seconds).
3853N/A </p>
3853N/A<pre class="programlisting">
3853N/A# nsupdate
3853N/A&gt; prereq nxdomain nickname.example.com
3853N/A&gt; update add nickname.example.com 86400 CNAME somehost.example.com
3853N/A&gt; send
3858N/A</pre>
3853N/A<p>
3853N/A </p>
3853N/A<p>
3853N/A The prerequisite condition gets the name server to check that there
3853N/A are no resource records of any type for
3853N/A <span class="type">nickname.example.com</span>.
3853N/A
3853N/A If there are, the update request fails.
3858N/A If this name does not exist, a CNAME for it is added.
3853N/A This ensures that when the CNAME is added, it cannot conflict with the
3853N/A long-standing rule in RFC 1034 that a name must not exist as any other
3853N/A record type if it exists as a CNAME.
3853N/A (The rule has been updated for DNSSEC in RFC 2535 to allow CNAMEs to have
3853N/A RRSIG, DNSKEY and NSEC records.)
3853N/A </p>
3853N/A</div>
3853N/A<div class="refsect1" lang="en">
3853N/A<a name="id2675266"></a><h2>FILES</h2>
3853N/A<div class="variablelist"><dl>
3853N/A<dt><span class="term"><code class="constant">/etc/resolv.conf</code></span></dt>
3853N/A<dd><p>
3853N/A used to identify default name server
3853N/A </p></dd>
3853N/A<dt><span class="term"><code class="constant">/var/run/named/session.key</code></span></dt>
3853N/A<dd><p>
3853N/A sets the default TSIG key for use in local-only mode
3853N/A </p></dd>
3853N/A<dt><span class="term"><code class="constant">K{name}.+157.+{random}.key</code></span></dt>
3853N/A<dd><p>
3853N/A base-64 encoding of HMAC-MD5 key created by
3853N/A <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
3853N/A </p></dd>
3853N/A<dt><span class="term"><code class="constant">K{name}.+157.+{random}.private</code></span></dt>
3853N/A<dd><p>
3853N/A base-64 encoding of HMAC-MD5 key created by
3853N/A <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
3853N/A </p></dd>
3853N/A</dl></div>
3853N/A</div>
4500N/A<div class="refsect1" lang="en">
4500N/A<a name="id2675417"></a><h2>SEE ALSO</h2>
4500N/A<p>
4500N/A <em class="citetitle">RFC 2136</em>,
4500N/A <em class="citetitle">RFC 3007</em>,
4500N/A <em class="citetitle">RFC 2104</em>,
4500N/A <em class="citetitle">RFC 2845</em>,
4500N/A <em class="citetitle">RFC 1034</em>,
4500N/A <em class="citetitle">RFC 2535</em>,
4500N/A <em class="citetitle">RFC 2931</em>,
4500N/A <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
4500N/A <span class="citerefentry"><span class="refentrytitle">ddns-confgen</span>(8)</span>,
4500N/A <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
4500N/A </p>
4500N/A</div>
4500N/A<div class="refsect1" lang="en">
4500N/A<a name="id2675475"></a><h2>BUGS</h2>
4500N/A<p>
4500N/A The TSIG key is redundantly stored in two separate files.
4500N/A This is a consequence of nsupdate using the DST library
4500N/A for its cryptographic operations, and may change in future
4500N/A releases.
4500N/A </p>
4500N/A</div>
4500N/A</div>
4500N/A<div class="navfooter">
4500N/A<hr>
4500N/A<table width="100%" summary="Navigation footer">
4500N/A<tr>
4500N/A<td width="40%" align="left">
4500N/A<a accesskey="p" href="man.named-journalprint.html">Prev</a>�</td>
3853N/A<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch10.html">Up</a></td>
3853N/A<td width="40%" align="right">�<a accesskey="n" href="man.rndc.html">Next</a>
3853N/A</td>
3853N/A</tr>
3853N/A<tr>
3853N/A<td width="40%" align="left" valign="top">
3853N/A<span class="application">named-journalprint</span>�</td>
3853N/A<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
3853N/A<td width="40%" align="right" valign="top">�<span class="application">rndc</span>
3853N/A</td>
3853N/A</tr>
3853N/A</table>
3853N/A</div>
3853N/A</body>
3853N/A</html>
3853N/A