nsupdate.1 (2010 09)
n
nsupdate(1) nsupdate(1)
(BIND 9.3)
update delete domain-name class type data...
Deletes any resource records named domain-name .Iftype and data are provided, only
matching resource records will be removed. The Internet class (
IN) is assumed if class is
not supplied.
update add domain-name ttl class type data...
Adds a new resource record with the specified ttl , class and data .
show Displays the current message, containing all the prerequisites and updates specified
since the last send operation.
send Sends the current message. This is equivalent to entering a blank line.
answer Displays the answer.
EXAMPLES
The examples below show how
nsupdate could be used to insert and delete resource records from the
example.com 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
example.com.
Example 1
# nsupdate
> update delete oldhost.example.com A
> update add newhost.example.com 86400 A 172.16.1.1
>
Any A records for oldhost.example.com
are deleted. An A record for newhost.example.com
with IP address 172.16.1.1 is added. The newly-added record has a 1 day TTL (86400 seconds)
Example 2
# nsupdate
> prereq nxdomain nickname.example.com
> update add nickname.example.com CNAME somehost.example.com
>
The prerequisite condition gets the name server to check that there are no resource records of any type
for nickname.example.com
. 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 record 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
CNAME records to have
RRSIG, DNSKEY,
and
NSEC records.)
WARNINGS
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.
AUTHOR
nsupdate was developed by the Internet Systems Consortium (ISC).
FILES
/etc/resolv.conf Used to identify default name server.
Kname.+157.+random .key Base-64 encoding of HMAC-MD5 key created by dnssec-keygen.
Kname.+157.+random .private
Base-64 encoding of HMAC-MD5 key created by dnssec-keygen.
SEE ALSO
dnssec-keygen(1), named(1M).
Requests for Comments (RFC): 1034, 2104, 2136, 2137, 2535, 2845, 2931, available online at
http://www.rfc-editor.org/.
HP-UX IP Address and Client Management Administrator’s Guide , available online at
http://www.hp.com/go/hpux-networking-docs.
HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3