action, recordname, TTL, recordtype, rdata, comment, user-defined field name=value, user-defined field name n=value,...
|action||The action to be performed on the record. Valid
values are add,
delete. This column must be present
and must contain a value.
|recordname||The name of the resource record. This column must
be present and may or may not contain a value:
How you specify record names depends on from where you want to perform the bulk update:
|TTL||The time-to-live value, in seconds, for the resource record. This column must be present but may be left blank. To leave a column blank, leave a space between the commas that delimit the column.|
|recordtype||The type of resource record. Valid values are A,
AAAA, CNAME, MX, SRV, HINFO, TXT, and NAPTR. The following
generic record types are also valid: A6, AFSDB, APL,
CAA, CERT, DHCID, DNAME, DS,
IPSECKEY, ISDN, KEY, KX, LOC, MB,
MG, MINFO, MR, NS, NSAP, PTR,
PX, RP, RT, SINK, SPF, SSHFP,
TLSA, WKS, and X25.
Note: The A6 record type has been moved to Historic status per RFC 6563, and is planned for removal in a future release.This column must be present and must contain a value.
|rdata||The data to define the resource record. Where multiple parameters are specified for the rdata, the values are separated with a space. This column must be present and must contain a value.|
|comment||A text string describing the resource record. After the record is added to Address Manager, this string appears in the Comments field when viewing the resource record’s Details tab. This column is optional. If you are adding user-defined fields to the record, this column must be present but may be left blank. To leave a column blank, leave a space between the commas that delimit the column.|
|user-defined field name||The name and value for a user-defined field. This column is optional. You can add an unlimited number of user-defined field values in each line. The user-defined field must already exist in Address Manager. The name of the user-defined field must be specified exactly as it appears in Address Manager. The value must match the type of value defined for the field. For more information on user-defined fields, refer to Object types and user-defined fields.|
Resource record data
|A||Specify an IPv4 address for the host
|AAAA||Specify an IPv6 address for the host
|CNAME||Specify the host for the alias record.
|MX||Specify the priority and host name for the mail
exchanger record, with a single space between each value:
|SRV||Specify the priority, weight, port, and host for
the service record, with a single space between each
To leave a value blank, use a 0 (zero) for the value.
In this example, the
priority and weight values are set to 0 (zero):
|HINFO||Specify the central processor unit and operating
system for the host information record, with a single space
between each value. To include spaces in each value, the entire
rdata string must be enclosed in “quotation marks”. Values that
contain string must be enclosed in ““double”” quotation
|TXT||Specify the text string for the text
|NAPTR||Specify the order, preference, flags service,
regular expression, replacement, and for the naming authority
|Generic record types||Specify the rdata string for the record type. Refer to the respective RFC of each record type for the required rdata string.|
To add a host record with a comment and user-defined field:
add, host1.example.com., 3600, A, 192.168.0.1, A Host record, Location=Toronto
add, host2.example.com., 3600, A, 192.168.0.2, , Location=New York
add, host3.example.com., 3600, A, 192.168.0.2 add, host3.example.com., 3600, A, 192.168.0.3 add, host3.example.com., 3600, A, 192.168.0.4
add, srv.example.com., 3600, SRV, 10 0 50 host1.example.com, An SRV record
add, host4.example.com., 3600, AAAA, FD3B:4F43:E610:0:1322:33FF:FE44:5566
update, host1.example.com., 7200, A, 192.168.0.1, Updated the TTL
delete, host1.example.com., 7200, A, *