nsupdate.1in 14.9 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
.\" Man page generated from reStructuredText.
nsupdate \- dynamic DNS update utility
.nr rst2man-indent-level 0
.de1 rstReportMargin
\\$1 \\n[an-margin]
level \\n[rst2man-indent-level]
level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
.\" .rstReportMargin pre:
. RS \\$1
. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
. nr rst2man-indent-level +1
.\" .rstReportMargin post:
. RE
.\" indent \\n[an-margin]
.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
.nr rst2man-indent-level -1
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
\fBnsupdate\fP [\fB\-d\fP] [\fB\-D\fP] [\fB\-i\fP] [\fB\-L\fP level] [ [\fB\-g\fP] | [\fB\-o\fP] | [\fB\-l\fP] | [\fB\-y\fP [hmac:]keyname:secret] | [\fB\-k\fP keyfile] ] [\fB\-t\fP timeout] [\fB\-u\fP udptimeout] [\fB\-r\fP udpretries] [\fB\-v\fP] [\fB\-T\fP] [\fB\-P\fP] [\fB\-V\fP] [ [\fB\-4\fP] | [\fB\-6\fP] ] [filename]
38 39
\fBnsupdate\fP is used to submit Dynamic DNS Update requests, as defined in
\fI\%RFC 2136\fP, to a name server. This allows resource records to be added or
40 41 42 43 44 45 46 47 48
removed from a zone without manually editing the zone file. A single
update request can contain requests to add or remove more than one
resource record.
Zones that are under dynamic control via \fBnsupdate\fP or a DHCP server
should not be edited by hand. Manual edits could conflict with dynamic
updates and cause data to be lost.
The resource records that are dynamically added or removed with
49 50
\fBnsupdate\fP must be in the same zone. Requests are sent to the
zone\(aqs primary server, which is identified by the MNAME field of the
51 52 53
zone\(aqs SOA record.
Transaction signatures can be used to authenticate the Dynamic DNS
54 55
updates. These use the TSIG resource record type described in \fI\%RFC 2845\fP,
the SIG(0) record described in \fI\%RFC 2535\fP and \fI\%RFC 2931\fP, or GSS\-TSIG as
56 57 58 59
described in \fI\%RFC 3645\fP\&.
TSIG relies on a shared secret that should only be known to \fBnsupdate\fP
and the name server. For instance, suitable \fBkey\fP and \fBserver\fP
statements are added to \fB/etc/named.conf\fP so that the name server
can associate the appropriate secret key and algorithm with the IP
62 63
address of the client application that is using TSIG
authentication. \fBddns\-confgen\fP can generate suitable
configuration fragments. \fBnsupdate\fP uses the \fB\-y\fP or \fB\-k\fP options
to provide the TSIG shared secret; these options are mutually exclusive.
66 67 68 69 70 71 72 73 74 75
SIG(0) uses public key cryptography. To use a SIG(0) key, the public key
must be stored in a KEY record in a zone served by the name server.
GSS\-TSIG uses Kerberos credentials. Standard GSS\-TSIG mode is switched
on with the \fB\-g\fP flag. A non\-standards\-compliant variant of GSS\-TSIG
used by Windows 2000 can be switched on with the \fB\-o\fP flag.
76 77
.B \fB\-4\fP
This option sets use of IPv4 only.
79 80
.B \fB\-6\fP
This option sets use of IPv6 only.
82 83
.B \fB\-d\fP
This option sets debug mode, which provides tracing information about the update
84 85
requests that are made and the replies received from the name server.
86 87
.B \fB\-D\fP
This option sets extra debug mode.
89 90
.B \fB\-i\fP
This option forces interactive mode, even when standard input is not a terminal.
92 93
.B \fB\-k keyfile\fP
This option indicates the file containing the TSIG authentication key. Keyfiles may be in
two formats: a single file containing a \fBnamed.conf\fP\-format \fBkey\fP
statement, which may be generated automatically by \fBddns\-confgen\fP;
96 97 98
or a pair of files whose names are of the format
\fBK{name}.+157.+{random}.key\fP and
\fBK{name}.+157.+{random}.private\fP, which can be generated by
\fBdnssec\-keygen\fP\&. The \fB\-k\fP option can also be used to specify a SIG(0)
100 101 102
key used to authenticate Dynamic DNS update requests. In this case,
the key specified is not an HMAC\-MD5 key.
103 104
.B \fB\-l\fP
This option sets local\-host only mode, which sets the server address to localhost
(disabling the \fBserver\fP so that the server address cannot be
overridden). Connections to the local server use a TSIG key
found in \fB/var/run/named/session.key\fP, which is automatically
generated by \fBnamed\fP if any local \fBprimary\fP zone has set
109 110 111
\fBupdate\-policy\fP to \fBlocal\fP\&. The location of this key file can be
overridden with the \fB\-k\fP option.
112 113
.B \fB\-L level\fP
This option sets the logging debug level. If zero, logging is disabled.
115 116
.B \fB\-p port\fP
This option sets the port to use for connections to a name server. The default is
117 118
119 120
.B \fB\-P\fP
This option prints the list of private BIND\-specific resource record types whose
121 122
format is understood by \fBnsupdate\fP\&. See also the \fB\-T\fP option.
123 124 125
.B \fB\-r udpretries\fP
This option sets the number of UDP retries. The default is 3. If zero, only one update
request is made.
127 128 129
.B \fB\-t timeout\fP
This option sets the maximum time an update request can take before it is aborted. The
default is 300 seconds. If zero, the timeout is disabled.
131 132 133
.B \fB\-T\fP
This option prints the list of IANA standard resource record types whose format is
understood by \fBnsupdate\fP\&. \fBnsupdate\fP exits after the lists
134 135 136
are printed. The \fB\-T\fP option can be combined with the \fB\-P\fP
Other types can be entered using \fBTYPEXXXXX\fP where \fBXXXXX\fP is the
decimal value of the type with no leading zeros. The rdata, if
present, is parsed using the UNKNOWN rdata format, (<backslash>
140 141
<hash> <space> <length> <space> <hexstring>).
142 143 144
.B \fB\-u udptimeout\fP
This option sets the UDP retry interval. The default is 3 seconds. If zero, the
interval is computed from the timeout interval and number of UDP
145 146
147 148
.B \fB\-v\fP
This option specifies that TCP should be used even for small update requests. By default, \fBnsupdate\fP 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 is used. TCP may
151 152
be preferable when a batch of update requests is made.
153 154
.B \fB\-V\fP
This option prints the version number and exits.
156 157
.B \fB\-y [hmac:]keyname:secret\fP
This option sets the literal TSIG authentication key. \fBkeyname\fP is the name of the key,
158 159 160 161
and \fBsecret\fP is the base64 encoded shared secret. \fBhmac\fP is the
name of the key algorithm; valid choices are \fBhmac\-md5\fP,
\fBhmac\-sha1\fP, \fBhmac\-sha224\fP, \fBhmac\-sha256\fP, \fBhmac\-sha384\fP, or
\fBhmac\-sha512\fP\&. If \fBhmac\fP is not specified, the default is
\fBhmac\-md5\fP, or if MD5 was disabled, \fBhmac\-sha256\fP\&.
163 164
NOTE: Use of the \fB\-y\fP option is discouraged because the shared
secret is supplied as a command\-line argument in clear text. This may
166 167 168 169 170 171 172
be visible in the output from ps1 or in a history file maintained by
the user\(aqs shell.
\fBnsupdate\fP reads input from \fBfilename\fP or standard input. Each
command is supplied on exactly one line of input. Some commands are for
administrative purposes; others are either update instructions or
174 175 176
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 are rejected if the
178 179 180 181
tests for the prerequisite conditions fail.
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 either present or missing from
183 184 185 186
the zone. A blank input line (or the \fBsend\fP command) causes the
accumulated commands to be sent as one Dynamic DNS update request to the
name server.
The command formats and their meanings are as follows:
188 189
190 191 192 193 194
.B \fBserver servername port\fP
This command sends all dynamic update requests to the name server \fBservername\fP\&.
When no server statement is provided, \fBnsupdate\fP sends updates
to the primary server of the correct zone. The MNAME field of that
zone\(aqs SOA record identify the primary server for that zone.
\fBport\fP is the port number on \fBservername\fP where the dynamic
update requests are sent. If no port number is specified, the default
197 198
DNS port number of 53 is used.
199 200 201 202 203 204
.B \fBlocal address port\fP
This command sends all dynamic update requests using the local \fBaddress\fP\&. When
no local statement is provided, \fBnsupdate\fP sends updates using
an address and port chosen by the system. \fBport\fP can also
be used to force requests to come from a specific port. If no port number
is specified, the system assigns one.
206 207 208
.B \fBzone zonename\fP
This command specifies that all updates are to be made to the zone \fBzonename\fP\&.
If no \fBzone\fP statement is provided, \fBnsupdate\fP attempts to
209 210
determine the correct zone to update based on the rest of the input.
211 212
.B \fBclass classname\fP
This command specifies the default class. If no \fBclass\fP is specified, the default
213 214
class is \fBIN\fP\&.
215 216 217
.B \fBttl seconds\fP
This command specifies the default time\-to\-live, in seconds, for records to be added. The value
\fBnone\fP clears the default TTL.
219 220 221 222 223
.B \fBkey hmac:keyname secret\fP
This command specifies that all updates are to be TSIG\-signed using the
\fBkeyname\fP\-\fBsecret\fP pair. If \fBhmac\fP is specified, it sets
the signing algorithm in use. The default is \fBhmac\-md5\fP; if MD5
was disabled, the default is \fBhmac\-sha256\fP\&. The \fBkey\fP command overrides any key
224 225 226
specified on the command line via \fB\-y\fP or \fB\-k\fP\&.
.B \fBgsstsig\fP
This command uses GSS\-TSIG to sign the updates. This is equivalent to specifying
228 229 230
\fB\-g\fP on the command line.
.B \fBoldgsstsig\fP
This command uses the Windows 2000 version of GSS\-TSIG to sign the updates. This is
232 233
equivalent to specifying \fB\-o\fP on the command line.
234 235 236
.B \fBrealm [realm_name]\fP
When using GSS\-TSIG, this command specifies the use of \fBrealm_name\fP rather than the default realm
in \fBkrb5.conf\fP\&. If no realm is specified, the saved realm is
237 238
239 240
.B \fBcheck\-names [yes_or_no]\fP
This command turns on or off check\-names processing on records to be added.
241 242
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 is not added to the UPDATE message.
245 246
.B \fBprereq nxdomain domain\-name\fP
This command requires that no resource record of any type exist with the name
247 248
249 250
.B \fBprereq yxdomain domain\-name\fP
This command requires that \fBdomain\-name\fP exist (as at least one resource
251 252
record, of any type).
253 254 255
.B \fBprereq nxrrset domain\-name class type\fP
This command requires that no resource record exist of the specified \fBtype\fP,
\fBclass\fP, and \fBdomain\-name\fP\&. If \fBclass\fP is omitted, IN (Internet)
256 257
is assumed.
258 259 260
.B \fBprereq yxrrset domain\-name class type\fP
This command requires that a resource record of the specified \fBtype\fP,
\fBclass\fP and \fBdomain\-name\fP exist. If \fBclass\fP is omitted, IN
261 262
(internet) is assumed.
263 264
.B \fBprereq yxrrset domain\-name class type data\fP
With this command, the \fBdata\fP from each set of prerequisites of this form sharing a
265 266 267 268 269 270
common \fBtype\fP, \fBclass\fP, and \fBdomain\-name\fP 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 \fBtype\fP, \fBclass\fP, and
\fBdomain\-name\fP\&. The \fBdata\fP are written in the standard text
representation of the resource record\(aqs RDATA.
271 272 273 274
.B \fBupdate delete domain\-name ttl class type data\fP
This command deletes any resource records named \fBdomain\-name\fP\&. If \fBtype\fP and
\fBdata\fP are provided, only matching resource records are removed.
The Internet class is assumed if \fBclass\fP is not supplied. The
275 276
\fBttl\fP is ignored, and is only allowed for compatibility.
277 278
.B \fBupdate add domain\-name ttl class type data\fP
This command adds a new resource record with the specified \fBttl\fP, \fBclass\fP, and
279 280 281
.B \fBshow\fP
This command displays the current message, containing all of the prerequisites and
283 284 285
updates specified since the last send.
.B \fBsend\fP
This command sends the current message. This is equivalent to entering a blank
287 288 289
.B \fBanswer\fP
This command displays the answer.
291 292
.B \fBdebug\fP
This command turns on debugging.
294 295
.B \fBversion\fP
This command prints the version number.
297 298
.B \fBhelp\fP
This command prints a list of commands.
300 301
Lines beginning with a semicolon (;) are comments and are ignored.
303 304
The examples below show how \fBnsupdate\fP can be used to insert and
delete resource records from the \fBexample.com\fP zone. Notice that the
307 308
input in each example contains a trailing blank line, so that a group of
commands is sent as one dynamic update request to the primary name
309 310 311 312 313 314 315 316 317 318 319 320 321 322 323
server for \fBexample.com\fP\&.
.ft C
# nsupdate
> update delete oldhost.example.com A
> update add newhost.example.com 86400 A
> send
.ft P
Any A records for \fBoldhost.example.com\fP are deleted, and an A record
for \fBnewhost.example.com\fP with IP address is added. The
newly added record has a TTL of 1 day (86400 seconds).
327 328 329 330 331 332 333 334 335 336 337 338 339 340
.ft C
# nsupdate
> prereq nxdomain nickname.example.com
> update add nickname.example.com 86400 CNAME somehost.example.com
> send
.ft P
The prerequisite condition tells the name server to verify that there are
342 343 344 345 346 347
no resource records of any type for \fBnickname.example.com\fP\&. 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 \fI\%RFC 1034\fP 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 \fI\%RFC 2535\fP to allow CNAMEs to have RRSIG,
DNSKEY, and NSEC records.)
349 350 351 352
.B \fB/etc/resolv.conf\fP
Used to identify the default name server
354 355
.B \fB/var/run/named/session.key\fP
Sets the default TSIG key for use in local\-only mode
357 358
.B \fBK{name}.+157.+{random}.key\fP
Base\-64 encoding of the HMAC\-MD5 key created by \fBdnssec\-keygen\fP\&.
360 361
.B \fBK{name}.+157.+{random}.private\fP
Base\-64 encoding of the HMAC\-MD5 key created by \fBdnssec\-keygen\fP\&.
363 364 365 366
\fI\%RFC 2136\fP, \fI\%RFC 3007\fP, \fI\%RFC 2104\fP, \fI\%RFC 2845\fP, \fI\%RFC 1034\fP, \fI\%RFC 2535\fP, \fI\%RFC 2931\fP,
\fBnamed(8)\fP, \fBtsig\-keygen(8)\fP, \fBdnssec\-keygen(8)\fP\&.
368 369 370
The TSIG key is redundantly stored in two separate files. This is a
consequence of \fBnsupdate\fP using the DST library for its cryptographic
372 373 374 375 376 377 378
operations, and may change in future releases.
Internet Systems Consortium
2020, Internet Systems Consortium
.\" Generated by docutils manpage writer.