man.nsupdate.html revision 2cbb4ab75757fbb656997a82c14ca07db37d481a
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<!--
cbf0854acc9f5d11142dba30b1ab23e0532baaf2Automatic Updater - Copyright (C) 2004-2009 Internet Systems Consortium, Inc. ("ISC")
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - Copyright (C) 2000-2003 Internet Software Consortium.
ec5347e2c775f027573ce5648b910361aa926c01Automatic Updater -
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - Permission to use, copy, modify, and distribute this software for any
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - purpose with or without fee is hereby granted, provided that the above
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - copyright notice and this permission notice appear in all copies.
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 -
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 - PERFORMANCE OF THIS SOFTWARE.
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉-->
cbf0854acc9f5d11142dba30b1ab23e0532baaf2Automatic Updater<!-- $Id: man.nsupdate.html,v 1.49 2009/07/04 01:13:19 tbox Exp $ -->
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<html>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<head>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<title>nsupdate</title>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉<link rel="prev" href="man.named.html" title="named">
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<link rel="next" href="man.rndc.html" title="rndc">
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉</head>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<div class="navheader">
a84724de8db9e52857fb11bbcdb195658f9a05b2Michael Graff<table width="100%" summary="Navigation header">
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<tr><th colspan="3" align="center"><span class="application">nsupdate</span></th></tr>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<tr>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<td width="20%" align="left">
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<a accesskey="p" href="man.named.html">Prev</a>�</td>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<th width="60%" align="center">Manual pages</th>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<td width="20%" align="right">�<a accesskey="n" href="man.rndc.html">Next</a>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉</td>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉</tr>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉</table>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<hr>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉</div>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<div class="refentry" lang="en">
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<a name="man.nsupdate"></a><div class="titlepage"></div>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<div class="refnamediv">
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<h2>Name</h2>
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉<p><span class="application">nsupdate</span> &#8212; Dynamic DNS update utility</p>
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉</div>
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉<div class="refsynopsisdiv">
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉<h2>Synopsis</h2>
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉<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">-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>
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉</div>
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉<div class="refsect1" lang="en">
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉<a name="id2612407"></a><h2>DESCRIPTION</h2>
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉<p><span><strong class="command">nsupdate</strong></span>
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉 is used to submit Dynamic DNS Update requests as defined in RFC2136
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉 to a name server.
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉 This allows resource records to be added or removed from a zone
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉 without manually editing the zone file.
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉 A single update request can contain requests to add or remove more than
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉 one
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉 resource record.
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉 </p>
1c3ed2a83d176d9023b51b60dfc96c133f678362Tatuya JINMEI 神明達哉<p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 Zones that are under dynamic control via
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 <span><strong class="command">nsupdate</strong></span>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 or a DHCP server should not be edited by hand.
a84724de8db9e52857fb11bbcdb195658f9a05b2Michael Graff Manual edits could
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 conflict with dynamic updates and cause data to be lost.
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 </p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 The resource records that are dynamically added or removed with
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 <span><strong class="command">nsupdate</strong></span>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 have to be in the same zone.
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 Requests are sent to the zone's master server.
cbf0854acc9f5d11142dba30b1ab23e0532baaf2Automatic Updater This is identified by the MNAME field of the zone's SOA record.
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 </p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉<p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 The
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 <code class="option">-d</code>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 option makes
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 <span><strong class="command">nsupdate</strong></span>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 operate in debug mode.
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 This provides tracing information about the update requests that are
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 made and the replies received from the name server.
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 </p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 The <code class="option">-D</code> option makes <span><strong class="command">nsupdate</strong></span>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 report additional debugging information to <code class="option">-d</code>.
a84724de8db9e52857fb11bbcdb195658f9a05b2Michael Graff </p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 The <code class="option">-L</code> option with an integer argument of zero or
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 higher sets the logging debug level. If zero, logging is disabled.
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 </p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 Transaction signatures can be used to authenticate the Dynamic
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 DNS updates. These use the TSIG resource record type described
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 in RFC2845 or the SIG(0) record described in RFC3535 and
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 RFC2931 or GSS-TSIG as described in RFC3645. TSIG relies on
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 a shared secret that should only be known to
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 <span><strong class="command">nsupdate</strong></span> and the name server. Currently,
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 the only supported encryption algorithm for TSIG is HMAC-MD5,
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉 which is defined in RFC 2104. Once other algorithms are
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 defined for TSIG, applications will need to ensure they select
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 the appropriate algorithm as well as the key when authenticating
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 each other. For instance, suitable <span class="type">key</span> and
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <span class="type">server</span> statements would be added to
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <code class="filename">/etc/named.conf</code> so that the name server
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 can associate the appropriate secret key and algorithm with
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 the IP address of the client application that will be using
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 TSIG authentication. SIG(0) uses public key cryptography.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 To use a SIG(0) key, the public key must be stored in a KEY
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 record in a zone served by the name server.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <span><strong class="command">nsupdate</strong></span> does not read
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <code class="filename">/etc/named.conf</code>.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 GSS-TSIG uses Kerberos credentials.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 </p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉<p><span><strong class="command">nsupdate</strong></span>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 uses the <code class="option">-y</code> or <code class="option">-k</code> option
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 to provide the shared secret needed to generate a TSIG record
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 for authenticating Dynamic DNS update requests, default type
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 HMAC-MD5. These options are mutually exclusive.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 </p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉<p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 When the <code class="option">-y</code> option is used, a signature is
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 generated from
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 [<span class="optional"><em class="parameter"><code>hmac:</code></em></span>]<em class="parameter"><code>keyname:secret.</code></em>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <em class="parameter"><code>keyname</code></em> is the name of the key, and
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <em class="parameter"><code>secret</code></em> is the base64 encoded shared secret.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 Use of the <code class="option">-y</code> option is discouraged because the
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 shared secret is supplied as a command line argument in clear text.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 This may be visible in the output from
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <span class="citerefentry"><span class="refentrytitle">ps</span>(1)</span>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 or in a history file maintained by the user's shell.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 </p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉<p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 With the
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <code class="option">-k</code> option, <span><strong class="command">nsupdate</strong></span> reads
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 the shared secret from the file <em class="parameter"><code>keyfile</code></em>.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 Keyfiles may be in two formats: a single file containing
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 a <code class="filename">named.conf</code>-format <span><strong class="command">key</strong></span>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 statement, which may be generated automatically by
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <span><strong class="command">ddns-confgen</strong></span>, or a pair of files whose names are
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 of the format <code class="filename">K{name}.+157.+{random}.key</code> and
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <code class="filename">K{name}.+157.+{random}.private</code>, which can be
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 generated by <span><strong class="command">dnssec-keygen</strong></span>.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 The <code class="option">-k</code> may also be used to specify a SIG(0) key used
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 to authenticate Dynamic DNS update requests. In this case, the key
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 specified is not an HMAC-MD5 key.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 </p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉<p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <span><strong class="command">nsupdate</strong></span> can be run in a local-host only mode
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 using the <code class="option">-l</code> flag. This sets the server address to
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 localhost (disabling the <span><strong class="command">server</strong></span> so that the server
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 address cannot be overridden). Connections to the local server will
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 use a TSIG key found in <code class="filename">/var/run/named/ddns.key</code>,
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 which is automatically generated by <span><strong class="command">named</strong></span> if any
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 local master zone has the <span><strong class="command">dynamic</strong></span> zone option set
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 to yes. The location of this key file can be overridden with
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 the <code class="option">-k</code> option.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 </p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉<p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 By default, <span><strong class="command">nsupdate</strong></span>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 uses UDP to send update requests to the name server unless they are too
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 large to fit in a UDP request in which case TCP will be used.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 The
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <code class="option">-v</code>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 option makes
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 <span><strong class="command">nsupdate</strong></span>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 use a TCP connection.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 This may be preferable when a batch of update requests is made.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 </p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉<p>
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 The <code class="option">-p</code> sets the default port number to use for
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 connections to a name server. The default is 53.
c528bd698637d84a0081d26a58813607c7f52bb7Tatuya JINMEI 神明達哉 </p>
5597be9bb88de138dfec9fa9176708443813925eTatuya JINMEI 神明達哉<p>
The <code class="option">-t</code> option sets 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>
<p>
The <code class="option">-u</code> option sets 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>
<p>
The <code class="option">-r</code> option sets the number of UDP retries. The
default is
3. If zero, only one update request will be made.
</p>
<p>
The <code class="option">-R <em class="replaceable"><code>randomdev</code></em></code> option
specifies a source of 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>
</div>
<div class="refsect1" lang="en">
<a name="id2612864"></a><h2>INPUT FORMAT</h2>
<p><span><strong class="command">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><strong class="command">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>
<dt><span class="term">
<span><strong class="command">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><strong class="command">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><strong class="command">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><strong class="command">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><strong class="command">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><strong class="command">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><strong class="command">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><strong class="command">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><strong class="command">key</strong></span>
{name}
{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>keysecret</code></em> pair.
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>.
</p></dd>
<dt><span class="term">
<span><strong class="command">prereq 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><strong class="command">prereq 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><strong class="command">prereq 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><strong class="command">prereq 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><strong class="command">prereq 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><strong class="command">update delete</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><strong class="command">update 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><strong class="command">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><strong class="command">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><strong class="command">answer</strong></span>
</span></dt>
<dd><p>
Displays the answer.
</p></dd>
<dt><span class="term">
<span><strong class="command">debug</strong></span>
</span></dt>
<dd><p>
Turn on debugging.
</p></dd>
</dl></div>
<p>
</p>
<p>
Lines beginning with a semicolon are comments and are ignored.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2666734"></a><h2>EXAMPLES</h2>
<p>
The examples below show how
<span><strong class="command">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 RFC1034 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 RFC2535 to allow CNAMEs to have
RRSIG, DNSKEY and NSEC records.)
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2666785"></a><h2>FILES</h2>
<div class="variablelist"><dl>
<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/ddns.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="refsect1" lang="en">
<a name="id2666868"></a><h2>SEE ALSO</h2>
<p><span class="citerefentry"><span class="refentrytitle">RFC2136</span></span>,
<span class="citerefentry"><span class="refentrytitle">RFC3007</span></span>,
<span class="citerefentry"><span class="refentrytitle">RFC2104</span></span>,
<span class="citerefentry"><span class="refentrytitle">RFC2845</span></span>,
<span class="citerefentry"><span class="refentrytitle">RFC1034</span></span>,
<span class="citerefentry"><span class="refentrytitle">RFC2535</span></span>,
<span class="citerefentry"><span class="refentrytitle">RFC2931</span></span>,
<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="refsect1" lang="en">
<a name="id2666947"></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.html">Prev</a>�</td>
<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>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">named</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>
</body>
</html>