Bulk DNS Update CSV File

Transcription

1 Bulk DNS Updates Bulk DNS Update CSV File Each line in the comma-separated value (CSV) file represents a resource record. A line break must follow each line, and the file may contain up to 5000 lines. The comma-separated values represent columns of data, but the CSV file must not contain column headings. action, recordname, TTL, recordtype, rdata, comment, user-defined field name=value, user-defined field name n=value,... Lines in the file cannot be commented out. Each line contains the following columns: Column action recordname TTL Description The action to be performed on the record. Valid values are add, update, and delete. This column must be present and must contain a value. add creates a new resource record. update changes only the TTL, comment, and user-defined fields for most resource record types. For CNAME records, update changes only the host record to which the CNAME record points. For A records, update ignores any change made to the record s IPv4 address. delete deletes resource records. If a record is not found in Proteus, a file-notfound error is logged in the server log. To delete records that contain multiple IP addresses, specify the address with an * asterisk. The name of the resource record. This column must be present and may or may not contain a value: When performing a bulk update at the zone level, this column can be blank to give the resource record the same name as the zone. The name of the record appears in Proteus as (Same as Zone). When performing a bulk update at the view level, this column must contain a value. Bulk DNS Update cannot create records with (Same as Zone) for the record name from the view level. If your resource record names are controlled by a naming policy, you need to specify names that match the requirements of the policy. To specify an Incremental value in the CSV file, using the # (pound) symbol. For more information on naming policies, see Naming Policies on page 53. How you specify record names depends on from where you want to perform the bulk update: When performing the bulk update at the view level, specify FQDNs. Proteus assumes that all record names are not dot-separated. For example, add, host1.example.com., 3600, A, adds the host record host1.example.com. When performing the bulk update at the zone level, specify record names as relative names or FQDNs. Names ending with a dot are considered as absolute names which should not contain dot-separated named. Names not ending with a dot are considered as relative names and can contain a dot. For example, add, host2, 3600, A, adds the host record host2.example.com. For example, add, host3.example.com., 3600, A, adds the host record host3.example.com. 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. Version Proteus Administration Guide 197

2 Chapter 6: DNS Column recordtype rdata comment user-defined field name Description The type of resource record. Valid values are A, CNAME, MX, SRV, HINFO, TXT, and NAPTR. The following generic record types are also valid: A6, AAAA, AFSDB, APL, CERT, DNAME, DNSKEY, DS, ISDN, KEY, KX, LOC, MB, MG, MINFO, MR, NS, NSAP, PX, RP, RT, SINK, SSHFP, WKS, or X25. This column must be present and must contain a value. The data to define the resource record. For information about the rdata required for each type of resource record, see Resource Record rdata on page 198. 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. A text string describing the resource record. After the record is added to Proteus, 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. 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 Proteus. The name of the user-defined field must be specified exactly as it appears in Proteus. The value must match the type of value defined for the field. For more information on user-defined fields, see User- Defined Fields on page 66. Resource Record rdata The rdata field contains the parameters for the resource record being added, updated, or deleted. When adding a record, the parameters define the record. When updating or deleting a record, the parameters are used to find the record in Proteus to update or delete; all parameters must match an existing record for the record to be updated or deleted. Record Type A CNAME MX SRV HINFO rdata Specify an IPv4 address for the host record. For example: Specify the host for the alias record. For example: host1.example.com Specify the priority and host name for the mail exchanger record, with a single space between each value: For example: 10 mail.example.com Specify the priority, port, weight, and host for the service record, with a single space between each value. For example: host1.example.com 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): host1.example.com" 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 doubled quotation marks. For example: """Dual 1.2Ghz"" ""Linux 7.1""" 198 Proteus Administration Guide Version 3.0.1

3 Bulk DNS Updates Record Type TXT NAPTR Generic record types rdata Specify the text string for the text record. For example: This is a text record Specify the order, preference, service, regular expression, replacement, and flags for the naming authority pointer record. For example: E2U+ !^.*$!mailto:information@example.com!i. A Specify the rdata string for the record type. Refer to the RFCs for each record type for the required rdata string. CSV Examples To add a host record with a comment and user-defined field: add, host1.example.com., 3600, A, , A Host record, Location=Toronto To add a host record with no comment and with a user-defined field: add, host2.example.com., 3600, A, ,, Location=New York To add a host record with multiple IPv4 addresses: add, host3.example.com., 3600, A, add, host3.example.com., 3600, A, add, host3.example.com., 3600, A, To add an SRV record with a blank port value: add, srv.example.com., 3600, SRV, host1.example.com", An SRV record To add an AAAA record for an IPv6 address: add, host4.example.com., 3600, AAAA, FD3B:4F43:E610:0:1322:33FF:FE44:5566 To update the TTL and comment for a host record: update, host1.example.com., 7200, A, , Updated the TTL To delete a host record that may have multiple IP addresses: delete, host1.example.com., 7200, A, * Version Proteus Administration Guide 199

4 Chapter 6: DNS Performing a Bulk DNS Update To perform a DNS Bulk Update: 1 Click the My IPAM tab. From the configuration drop-down list, select a configuration. 2 Click the DNS tab. Tabs remember the page you last worked on, so click the DNS tab again to ensure you are working with the Configuration information page. 3 You can perform a DNS Bulk Update at the view or zone level. Navigate to and select a view or zone. 4 Click Action and select Bulk DNS Updates. The Upload a CSV File page appears. 5 Beside the Bulk DNS Updates CSV file field, click Browse. A dialog box appears where you can select a CSV file on your workstation. 6 Select a CSV file and click Open. The file selection dialog box closes and the path for the selected file appears in the Bulk DNS Updates CSV file field. 200 Proteus Administration Guide Version 3.0.1

5 Bulk DNS Updates 7 Click Next. The Bulk DNS Updates Bulk Update Review page appears. 8 In the General section, each Line field contains a line from your CSV file. If Proteus finds an error in a line, the error is noted in red text to the right of the field. Review each line and correct any errors by editing the text in the Line field. For more information on the update entry format, see Bulk DNS Updates on page 196. To remove a line from the list, click the Remove link to the right of the Line field. 9 In the Apply Option section, set the error handling and naming policy options: Abort entire operation if there is an error when selected, cancels the entire update process if there is an error with any of the updates. None of the updates are applied if any one update contains an error. If errors are encountered, a list of entries with errors appears at the end of the update process. Skip failure when selected, ignored any updates that contain errors. Updates without errors are applied. Override Naming Policy when selected, resource records are created with names as specified in the update entries; any naming policies assigned to the view or zone are ignored. When not selected, any naming policies assigned to the view or zone are enforced; entries with resource record names that do not follow the naming policy are ignored. If updates are ignored because of naming policy conflicts, a list of entries with conflicts appears at the end of the update process. For information on naming policies, see Naming Policies on page In the Change Control section, add comments to describe the changes. This step is optional but may be set to be required. Version Proteus Administration Guide 201

6 Chapter 6: DNS 11 Click Apply. The Bulk DNS Updates Bulk Update Result page appears. 12 Review the results in the General section. This section lists the error handling and naming policy options you selected for the update and the number of updates successfully applied. 13 If entries were skipped or caused the update process to be cancelled, a list of errors appears. Review the errors and correct the problems in your CSV file and attempt the updated process again. 14 Click OK to return to the DNS view Zones tab or to the DNS zone Resource Records tab. 202 Proteus Administration Guide Version 3.0.1