Generates a DNS update packet readable by a BIND 8 nameserver.
nsupdate8 [ -v ] [ -d ] [Filename]
The nsupdate8 command can read from a file specified on the command line, from stdin for pipes or redirected input from a file, or interactively from a tty. All three methods use the same format specified below. The input defines a DNS update packet that can be used to update a ZONE. There are two sections to an update, a prerequisite section and an update section. The DNS name server verifies that all the prerequisites are true before processing the update section.
|-d||Causes nsupdate8 to generate additional debug information about its actions.|
|-v||Tells nsupdate8 to use a virtual circuit (TCP connection), instead of the usual UDP connection.|
The input format is defined as a set of update packets. Each packet is a set of strings terminated with a newline. The last string in the input stream may end with an EOF. If the stream is to contain multiple update packets, each packet must be separated from the next packet by a blank line (single newline character). The semi-colon is used a comment character. Anything after it is ignored and thrown out of the update packet.
The input format for nsupdate8 is a follows:
section opcode name [ttl] [class] [type] [data]
This is the general form. Each value of section and
opcode modify what is required for later arguments.
|section||Defines the section of the update this record is for. Values
|opcode||Defines the operation to do with this record.
|name||The name of the DNS entry that one is testing or modifying.|
|[ttl]||Optional time-to-live for the record being added. In some forms, this is not optional.|
|[class]||Class of the record to be added to the zone. Values are IN, HESIOD, and CHAOS. The default for all messages is IN.|
|[type]||The type of the record to be added to or checked against the zone. Values are A, NS, CNAME, SOA, MB, MR, NULL, WKS, PTR, HINFO, MINFO, MX, TXT, RP, AFSDB, X25, ISDN, RT, NSAP, NSAP_PTR, PX, and LOC. NOTE: The CNAME type may only be added with TSIG and TKEY records which are not currently supported in BIND 8.|
|[data]||The data to be added or checked against the zone. The data should be valid for the specified type and in the DOMAIN data file format of a DNS server zone file. For prerequisite checking, an asterik (*) is used to match any value. This can also be used to delete all records of a particular type.|
Here are the specific format cases:
prereq nxdomain <name> <ttl != 0> [class] prereq nydomain <name ttl != 0> [class] prereq nxrrset <name> [ttl] [class] <type> prereq nyrrset <name> [ttl] [class] <type> <data> update delete <name> [ttl] [class] [type] [data] update add <name> <ttl != 0> [class] <type> <data>
Messages indicating the different actions done and/or problems encountered by the program.
The nsupdate command, named command,.
The named.conf file format, DOMAIN Cache file format, DOMAIN Data file format, DOMAIN Reverse Data file format, DOMAIN Local Data file format, resolv.conf file format.
TCP/IP Name Resolution and TCP/IP Daemons in AIX 5L Version 5.1 System Management Guide: Communications and Networks.
Configuring Name Servers and Planning for DOMAIN Name Resolution in AIX 5L Version 5.1 System Management Guide: Communications and Networks.