How to use the Bluecat Bulk import feature

How to use the Bluecat Bulk import feature

Use the Bluecat bulk import feature to update multiple DNS records simultaneously. Bulk DNS updates can be applied at the Bluecat View or Zone level. Bulk imports cannot be used to apply DHCP data.

Step-by-step guide

  1. Log in to the BAM, select the DNS tab and confirm the active configuration is WSU. It may be required to click the DNS tab twice, as the BAM will remember the last active page of a user session.

  2. Select a view. For most cases, the default view is most appropriate. If the import file is configured to be imported at the view level, skip to step 4

  3. Navigate to the zone to be updated. Note that if a zone has resource records, the BAM will default to showing records. Click on "Sub Zones" to browse further. Select "Resource Records" once you've reached the target zone.

  4. Using the gear icon, select "Bulk DNS Updates"

  5. use the file picker to select a CSV file with the format described below, click next

  6. Review each update.

    1. Correct errors and override the import data using the BAM UI.

    2. Remove a line by clicking on the 'Remove' link

  7. Select a error handling policy:

    1. Abort: if there is any error, do not apply any changes contained in the bulk update. Note that if the only errors in a file are for delete actions that fail because there's no record to delete, the entire transaction will still be applied.

    2. Skip records with errors: Any record that does not have an error will be applied.

    3. Override Naming Policy: ignore naming policies defined in the BAM and use hostnames defined in the import file. If not selected, naming policies are enforced and any records that violate naming policies will be treated as errors.

    4. Update dynamic record without dynamic deployment: Do not deploy dynamic record changes to the DHCP/DNS server. Normally dynamic updates are deployed automatically.

  8. Apply

  9. Review errors, correct the source CSV file and repeat as required.

 

CSV format (Zone imports)

The CSV bulk import does not use a header row. The columns listed here apply to each row, and the first data row should be row 1 of the CSV. See also examples at the bottom of this document.

  • Column 1: Action. Action is required and tells the Bluecat what action to perform for the data in the row 

    • add: add a record

    • update: change an existing record

    • delete: delete a record

  • Column 2: record name. Can be empty in some cases.

    • If blank: import will assume the records are using the (Same as Zone) naming convention

    • If not blank:

      • If the record contains a trailing dot, eg "foo.wsu.edu.", the record to be created will be considered absolute and will be created relative to the DNS root. For example, if importing into the zone "wsu.edu", the record "foo.wsu.edu." will be created as "foo.wsu.edu"

      • If the record does not contain a trailing dot, eg "foo.wsu.edu", the record will be created relative to the zone. For example, if importing into the wsu.edu zone, "foo.wsu.edu" will be created as "foo.wsu.edu.wsu.edu"

      • if the hostname contains '#', # is replaced with an incremental value

  • Column 3: Time to Live. The amount of time in seconds that a DNS server can cache this record. Can be left blank to use the default TTL by using a single whitespace.

  • Column 4: Record Type. Required and can be one of: A, AAAA, CNAME, MX, SRV, HINFO, TXT, or NAPTR, or can be a generic record with one of the following types: A6, AFSDB, APL, CAA, DHCID, DNAME, DS, IPSEC, ISDN, KEY, KX, LOC, MB, MG, MIINFO, MR, NS, NSAP, PTR, PX, RP, RT, SINK, SPF, SSHFP, TLSA, WKS, or X25

  • Column 5: Record Data: the data used to define a record, using space separated values. For non-generic record types, Record data takes the form:

    • A: an IPv4 address

    • AAAA: an IPv6 address

    • CNAME: the host name the CNAME points to

    • MX: priority and name of mail record, eg "10 mail.wsu.edu"

    • SRV: The priority, weight, port, and host record name eg "10 50 5050 host1.wsu.edu". Blank values for each sub element can be indicated using 0 as a placeholder.

    • HINFO: Specify CPU and OS data. Note that since a space is a field delimiter, if the values here contain spaces, they must be quoted, eg """Dual 1.2Ghz"" ""Linux 7.1""".

    • TXT: the contents of the text record. This is not a delimited field, so no quotes are required if the string contains whitespace.

    • NAPTR: order preference, flags, expression, and replacement string for a naming authority pointer record.

    • Generic types are defined by their individual properties.

  • Column 6: A comment describing the record. Can be blank by using a single whitespace.

  • Columns 7 to n: user-defined field data. Not required. If user-defined data is provided, it must exist as a user-defined field in the Bluecat address manager and should be entered using key=value syntax. Use one column for each user-defined field.

CSV format differences when importing to a View

When importing to a view, rather than a zone, fields remain the same except for record name field, which behaves differently:

  • The record name is required; there is no default to (Same as Zone) for empty record names

  • (Same as Zone) records are not supported

  • All hostnames should use FQDN values with the trailing dot

Example CSV import data


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

To add a host record with no comment and with a user-defined field:
add, host2.example.com., 3600, A, 192.168.0.2, , Location=New York

To add a host record with multiple IPv4 addresses:
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

To add an SRV record with a blank port value:
add, srv.example.com., 3600, SRV, 10 0 50 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, 192.168.0.1, Updated the TTL

To delete a host record that may have multiple IP addresses:
delete, host1.example.com., 7200, A, *

Related articles

If you encounter any difficulties or have questions, please email at crimsonservicedesk@wsu.edu for assistance.