infoblox csv import reference

Infoblox CSV Import ReferenceInfoblox CSV Import Reference
Copyright Statements © 2017, Infoblox Inc.— All rights reserved. The contents of this document may not be copied or duplicated in any form, in whole or in part, without the prior
written permission of Infoblox, Inc.
The information in this document is subject to change without notice. Infoblox, Inc. shall not be liable for any
damages resulting from technical errors or omissions which may be present in this document, or from use of this
document.
This document is an unpublished work protected by the United States copyright laws and is proprietary to Infoblox,
Inc. Disclosure, copying, reproduction, merger, translation, modification, enhancement, or use of this document by
anyone other than authorized employees, authorized users, or licensees of Infoblox, Inc. without the prior written
consent of Infoblox, Inc. is prohibited.
For Open Source Copyright information, refer to the Infoblox Administrator Guide.
Trademark Statements Infoblox, the Infoblox logo, Grid, NIOS, bloxTools, NetMRI and PortIQ are trademarks or registered trademarks of
Infoblox Inc.
All other trademarked names used herein are the properties of their respective owners and are used for identification
purposes only.
Company Information
Network Insight Appliances: ND-800, ND-805, ND-1400, ND-1405, ND-2200, ND-2205, and ND-4000
Trinzic Appliances: TE-100, TE-810, TE-815, TE-820, TE-825, TE-1410, TE-1415, TE-1420, TE-1425, TE-2210, TE-2215,
TE-2220, TE-2225, IB-4010, and IB-4020
Cloud Network Automation: CP-V800, CP-V1400, and CP-V2200
Trinzic Reporting: TR-800, TR-805, TR-1400, TR-1405, TR-2200, TR-2205, and TR-4000
DNS Cache Acceleration Appliances: IB-4030 and IB-4030-10GE
NetMRI: NetMRI-1102-A, NT-1400, NT-2200, and NT-4000
Document Number: 400-0703-200 Rev. A
Document Updated: July 21, 2017
Warranty Information Your purchase includes a 90-day software warranty and a one year limited warranty on the Infoblox appliance, plus
an Infoblox Warranty Support Plan and Technical Support. For more information about Infoblox Warranty information,
refer to the Infoblox Web site, or contact Infoblox Technical Support.
This preface describes the document conventions of this guide, and provides information about how to find
additional product information, including how to access Infoblox Technical Support. It includes the following
sections:
NIOS 8.2 CSV Import Reference (Rev. A) 3
Preface
Document Overview
The CSV import reference provides general guidelines and file format information about CSV import. It was last
updated on July 21, 2017. For updated documentation, visit our Support site at https://support.infoblox.com.
Documentation Conventions
The text in this guide follows the following style conventions.
Related Documentation
• Infoblox Installation Guide for the 2205Series Platforms
• Infoblox Installation Guide for the 4000 Series Platforms
• Infoblox Installation Guide for the Infoblox-4010 Appliance
• Infoblox Installation Guide for the IB-4030 and IB-4030-10GE Appliances
• Infoblox DNS Cache Acceleration Administrator Guide
• Infoblox Installation Guide for vNIOS for Microsoft Azure
• Infoblox Installation Guide for vNIOS for AWS
• Infoblox Installation Guide for vNIOS for VMware
• Infoblox Installation Guide for vNIOS on Microsoft 2008 R2 for Hyper-V
• Infoblox Installation Guide for vNIOS for KVM Hypervisor and KVM-based OpenStack
• Infoblox Safety Guide
To provide feedback on any of the Infoblox technical documents, please e-mail [email protected].
Style Usage
data Signifies the data in a CSV file.
4 CSV Import Reference (Rev. A) NIOS 8.2
User Accounts
The Infoblox appliance ships with a default user name and password. Change the default admin account password
immediately after the system is installed to safeguard its use. Make sure that the NIOS appliance has at least one
administrator account with superuser privileges at all times, and keep a record of your account information in a safe
place. If you lose the admin account password, and did not already create another superuser account, the system will
need to be reset to factory defaults, causing you to lose all existing data on the NIOS appliance. You can create new
administrator accounts, with or without superuser privileges. For more information, refer to the Infoblox Administrator Guide.
Software Upgrades
Software upgrades are available according to the Terms of Sale for your system. Infoblox notifies you when an
upgrade is available. Register immediately with Infoblox Technical Support at
http://www.infoblox.com/support/customer/evaluation-and-registration to maximize your Technical Support.
Infoblox Technical Support provides assistance via the Web, e-mail, and telephone. The Infoblox Support web site at
https://support.infoblox.com provides access to product documentation and release notes, but requires the user ID
and password you receive when you register your product online at:
http://www.infoblox.com/support/customer/evaluation-and-registration.
CSV Import Reference
This chapter provides general guidelines and file format information about each supported object type for CSV
import. You must follow the format and syntax described in this section to ensure a successful data import.
This appendix includes the following sections:
• Guidelines for CSV Import on page 8
— General Guidelines on page 8
— Data Specific Guidelines on page 9
— CSV Import Limitations on page 10
• CSV File Format on page 11
— IDN Support for CSV Import on page 12
— CSV Import for Response Policy Zones on page 13
— CSV Format for Inheritable Extensible Attributes on page 15
— Importing Inheritable Extensible Attributes on page 15
— Importing Active Directory Domains and Sites on page 16
— CSV Import for Topology Rulesets and Rules in DNS Traffic Control on page 16
• Supported Object Types on page 17
• Importing Multiple Action CSV file on page 135
Guidelines for CSV Import
You can create a data file using a text editor, such as Microsoft Notepad, or an application that supports CSV file
format, such as Microsoft Excel.
You can also import data using Infoblox Migration Wizard, which is a standalone software tool that facilitates the
migration of DNS and DHCP data from Microsoft servers to the Infoblox Grid. This tool synchronizes DNS and DHCP
data from Microsoft servers and generates a CSV file based on conversion rules you set up through the tool. You can
then import the CSV data to the Infoblox Grid through CSV import. For more information, refer to the Infoblox Administrator Guide for Infoblox Migration Wizard.
WARNING: CSV imports and operations that involve massive data, such as deleting large zones and recursive
deletion of networks and all child objects, will significantly affect member performance,
resulting in service outage.
Follow these rules to start a data file:
• Do not use UTF-8 characters in the CSV file name, but the contents of a CSV file must be encoded in UTF-8
characters. Note that Microsoft Excel imports data in the default code page, either in ISO-8859-1 or
WINDOWS-1252. You must not import a CSV file that is encoded in Windows 1252 or ISO-8859-1 formats.
• Use a new line to enter data for each row. Separate each data field with a supported separator, such as a
comma, semicolon, space, or tab.
• Do not include blank lines in the data file.
• Field names: Specify the field names in the second line. You can include multiple rows of field names as long as
you define the fields before the data. The first column in the field name row must be defined as “Header.” The
rest of the columns are field names of the data. Columns without a field name are ignored. If multiple field
names are specified, the latest field names are used to import the data.
• It may take longer than expected to import a large number of DHCP ranges that are associated with a single MAC
address filter.
• When a CSV import starts, the appliance validates the first 100,000 rows of data in the CSV file. If the file
contains more than 100,000 rows of data, the appliance validates the rest of the data as the import progresses.
• The appliance supports up to one million rows of data in each CSV import.
• Use the add function to add new rows from the imported CSV file to the database.
• Use the Override function, not the merge function, to overwrite existing data. When you use the merge function,
the appliance does not overwrite existing data, even if the data file contains new data.
• Use the Delete function to delete import jobs that are uploaded. You can delete the content of a CSV file that you
have imported to the database. Note that you cannot delete jobs that are already imported.
• Use the Replace operation to replace current data in the database with data in the imported file. You can use the
replace function for authoritative zone data only. The replace operation might affect system performance if you
try to replace a zone with a lot of changes. Infoblox recommends that you perform the replace operation for large
import files (more than 10,000 rows of changes) during non-peak hours. This operation does not support DNS
records that are automatically generated or exported, but it supports NS records that are created manually.
• When you import CSV files for NS record updates, you must specify a value for zone_nameservers. NIOS
displays an error message if you do not specify a value for this field when you import the CSV file.
• When you perform a CSV export of automatically created NS records using Infoblox API, the zone_nameservers
field will have an empty value. Therefore, if you import the previously exported CSV file that includes
automatically created NS records through the Infoblox GUI, then the CSV import fails and Grid Manager displays
an error message.
• When you perform a CSV import that includes objects that have scheduled changes or updates associated with
them, the import fails. Only superusers can cancel the scheduled changes.
Guidelines for CSV Import
• When you stop an import, the appliance completes the import of the data row it is currently processing before it
stops the import. You cannot resume the import from where it stopped.
• You can download uploaded or error files, snapshots, and results file. For more information, see Infoblox NIOS Administrator Guide.
• When you import a small file, the appliance processes the import quickly. Under this circumstance, the
appliance may generate an error message when you try to stop the import because the import is completed
before you can stop it.
• The error files of the last two imports are stored on the appliance. You can download these files using the API
import_id method. For information, refer to the Infoblox API Documentation.
• When you use Microsoft Excel to create or view a data file, ensure that you review the settings of the file. Some
data, such as dates, may show up in a different format depending on your settings.
• All operations triggered by a CSV import are recorded in the audit log.
Data Specific Guidelines
Follow these guidelines to enter data:
• The appliance uses double quotes (“) as the escape characters in CSV import. If you want to include supported
separators in a field, you must enclose the data in a pair of double quotes (“ “). This applies to the field names
and data. For example, if you want to use the field name ADMGRP-CSV ,; Import, you must enter “ADMGRP-CSV
,; Import” as the value. Otherwise, the import fails. When you enter “123””123”, the imported data is
123””123, and when you enter “\\”, the imported data is \\.
• If you have an empty value in the last field, you must still include the separator at the end of the data row.
Otherwise, the corresponding column and all its data are not imported, and the appliance generates an error.
• For each supported object type, you must include all the required fields in the data file. For information, see
Supported Object Types on page 17. Note that all required fields are marked with an asterisk (*) in an exported
file.
Note: If you want to modify a required field XXX (for either the overwrite or merge function), you must add a
corresponding field, _new_XXX, to include the new value. For example, “fqdn” is a required field in an A
record. If you want to update this field, you must include a new field “_new_fqdn” and define the new
value here. The appliance overwrites the existing data in the required field using the values you specify in
the new field. Note that the replace function ignores _new_XXX fields in the imported CSV files.
• When you perform an overwrite function, you must define all boolean and integer data types in each supported
object type in order for the appliance to overwrite existing data.
• Inherited fields: The appliance uses the following conventions to override inherited fields:
— When a value is specified in a field, the appliance overrides the inherited value with the new value.
— When a value is set to “ “ or an empty value, the appliance does not override the inherited value.
— When a value is set to a string with a value of <empty>, the appliance overrides the inherited value with an
empty value.
• Extensible attributes: A field name of EA-XXX indicates an extensible attribute, where XXX is the attribute name.
The value of an extensible attribute can be a string, a list, an integer, an email address, a URL, or a date in
YYYY-MM-DD format. Note that extensible attributes do not support time zones. Following are some examples:
• “EA-Site” is a predefined string type for locations. It can have a value of “Santa Clara”.
• “EA-User” is a user defined list type for employee types. It can have a list of values, such as
“Local,Remote,Temp”. Note that only one value can be specified when importing the extensible attribute.
• “EA-Building” is a predefined integer type for building numbers. It can have a value of “5”.
• “EA-TechPubs” is a user defined email address type. It can have a value of “[email protected]”.
• “EA-IB” is a user defined URL type. It can have a value of “www.infoblox.com”.
• “EA-Date” is a user defined date type attribute. It can have a value of “2010-11-20”.
• Admin permissions: A field name of ADMGRP-XXX indicates the admin permission of a specific admin group,
where XXX is the name of the admin group. The value of an admin permission can be a string or a list of strings
with subtypes. If there is a single value in the permission, use RW, RO, or DENY. If there is a subtype in the
permission, use a list format, such as “RW, ARecord/RO”.
• DHCP options: A field name of OPTION-XXX-nn indicates a DHCP option, where XXX is the vendor name of the
option and nn is the option number. If the option is of the DHCP vendor class, you can omit -XXX in the field
name. For example, OPTION-1 implies vendor class = DHCP and option number = 1, and OPTION-CISCO-122
implies vendor class = CISCO and option number = 122.
• Named ACLs (access control lists): When you import a named ACL or ACEs (access control entries) to a named
ACL, ensure that you validate the named ACLs to avoid conflicts and unexpected results. When adding ACEs to a
named ACL, all entries are appended to the end of the list. To reorder ACEs in a named ACL through CSV import,
you must first export the ACEs, delete all the ACEs in the current ACL, reorder the ACES in the exported .csv file,
and than re-import the ACEs to the named ACL. For more information about access control and named ACLs,
refer to the Infoblox NIOS Administrator Guide.
CSV Import Limitations
Ensure that you understand the following limitations before you start an import:
• You can import multiple CSV files at a time, but at any given time you can execute only one single task. The
import tasks are queued. Note that only one task at a time will be in the Import in progress state, while the
others are in the Import pending state.
• You cannot roll back to previous data.
• You cannot import network containers.
• The following data cannot be imported: Microsoft management, DNSSEC, and GSS-TSIG data.
• You cannot export or import zone configuration for DNSSEC signed zones, although resource records added for
a signed zone are supported.
• Only editable data can be imported. Discovered data cannot be imported or manipulated.
• If you upload a file and preview the file using the Preview option, and later update the content of the same CSV
file, and then try to view the edited file using the same Preview wizard, you may not be able to see the changes.
Infoblox recommends that you start a fresh CSV import to upload the edited file and navigate to the Preview
wizard to preview the file.
• You cannot perform the CSV import operation on a Microsoft Server zone object, but NIOS allows you to perform
the CSV import operation on records within a Microsoft Server zone. You may not see an error message when
you perform a CSV import using the replace operation on an Microsoft Server zone.
• When you promote a new Grid Master during an import, the import stops; and it does not restart on the new
Grid Master. When a failover occurs during an import, the import stops on the old active node, and it does not
restart on the new active node.
• When you configure Unbound as the DNS resolver, NIOS does not support certain features and they are not
displayed in Grid Manager. However, fields related to these unsupported features will appear in CSV export
files. Although these fields are only relevant to the IB-4030 and IB-4030-10GE appliances and might not apply
to the appliances in your Grid, you can still perform CSV imports using these CSV export files without any issues.
CSV File Format
CSV File Format
A CSV file is typically created and edited using a spreadsheet, though you can create a CSV file in a text editor using
any supported separator. You can include more than one object type in a single CSV file when you add or modify data.
For information, see Supported Object Types on page 17. You can also organize field names and data in a CSV file
using different formats, as shown in the following examples. For additional information about how to create a CSV
file, see Guidelines for CSV Import on page 8.
You can create one CSV file to update data of multiple object types (Network and Host Record), as illustrated in CSV File Example 1. In this example, you define the field names you want to modify for the two object types in rows 1 and
2. You then include the corresponding data as shown in rows 3 to 6.
Table 1.1 CSV File Example 1
In CSV File Example 1, the field name HEADER-NETWORK identifies the first row as a header row for the Network
objects. The field names ADDRESS, NETMASK, EA-Gateway, and EA-Secondary Address (in rows B1 to E1) tell NIOS
how to interpret a row of network data in the CSV file. Each row of data that begins with “Network” in column A is
identified as a network data row. Therefore, NIOS interprets rows 3 and 4 as network data rows, in which column B
contains the network addresses, column C contains the network masks, and columns D and E contain extensible
attribute values for gateway and secondary address.
Similarly, the field name HEADER-HostRecord identifies the second row as a header row for the Host Record objects.
This header declaration tells NIOS that for each subsequent row of data that begins with “HostRecord” in column A,
column C contains the FQDN of the host, and column D contains the host address. Therefore, NIOS interprets rows 5
and 6 as host record data rows that contain the FQDNs of the hosts in column C and the host addresses in column D.
Alternatively, you can organize the information in CSV File Example 1 so that the data rows immediately follow the
header rows, as shown in CSV File Example 2.
A B C D E
1 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Secondary Address
2 HEADER-HostRecord configure_for_dns* FQDN* ADDRESSES
3 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129
4 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0
5 HostRecord TRUE host1.dhcp.corp100.com 172.20.2.21
You can also specify multiple header declarations for the same object type, as shown in CSV File Example 3. In this
example, you specify the field names (in row 1) and data (in rows 2 and 3) to modify the extensible attributes
(EA-Gateway and EA-Secondary Address) of two network addresses. You then specify the field names (in row 4) and
data (in rows 5 and 6) to add new extensible attributes (EA-Gateway and EA-Host Range) of two other network
addresses.
The examples in this section are illustrated using tables that resemble spreadsheet layouts. However, all other
examples in this appendix use the comma separated value text file format. For example, the following is the CSV file
notation equivalent of CSV File Example 2 on page 12.
HEADER-NETWORK,ADDRESS*,NETMASK*,EA-Gateway,EA-Secondary Address
The appliance supports IDNs (Internationalized Domain Names) and punycode for most of the DNS object types in a
CSV file. An IDN is a domain name that contains a language-specific script or alphabet, such as Arabic, Chinese,
Russian, Devanagari, or the Latin alphabet-based characters with diacritics, such as French. IDNs are encoded in
multi-byte Unicode and are decoded into ASCII strings using a standardized mechanism known as Punycode
transcription. For example, DNS Zone ‘.’ (IDN in Russian) can be written as
‘xn--90anhdigczv.xn--p1ai’ in the punycode representation. For information about IDNs, refer to the Infoblox NIOS Administrator Guide.
A B C D E
2 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129
3 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0
4 HEADER-HostRecord configure_for_dns* FQDN* ADDRESSES
A B C D E
2 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129
3 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0
4 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Host Range
5 NETWORK 10.176.90.0 255.255.255.128 10.176.90.1 10.176.90.4-126
6 NETWORK 10.176.90.128 255.255.255.128 10.176.90.129 10.176.90.132-254
CSV File Format
You can use either IDNs or punycode to create DNS zones. Even if you use punycode to create a zone, the appliance
automatically generates the corresponding IDN and displays the zone name in its native characters. Note that the
appliance does not perform any conversion (IDN to punycode and vice versa) for DNS records, but preserves the data
in the original characters. In other words, if a DNS object or a field name contains IDN, the appliance imports the data
in IDN. If a DNS object or a field name is in punycode, the appliance imports the data in punycode. For more
information about supported objects for CSV import, Supported Object Types on page 17.
CSV Import for Response Policy Zones
You can import local RPZs (Response Policy Zones) and their rulesets using the CSV Import feature. When you import
local RPZs using this feature, you must specify three new columns, priority, rpz_policy, and substitute_name with
relevant values, whereas importing an RPZ ruleset requires specifying the value for parent RPZ in the parent_zone
column, as mentioned in the following tables. For a local RPZ, CSV import supports all the values that are listed in
Authoritative Zone on page 29 along with the three new columns. However, for RPZ rulesets it supports the values
that are listed in CNAME Record on page 41 along with a new column parent_zone.
For example, if you want to add a new local RPZ, JKL.INFO and substitute this domain with JKI.NET, then you must
mention the priority, rpz_policy, and substitute name as follows: .
A B C D E F G H I
HEADER-
RESPONSEPOLICYZONE
VIEW ZONE_TYPE
1001 GIVEN DEFAULT RESPONSEPOLICY
1002 NXDOMAIN DEFAULT RESPONSEPOLICY
1003 NODATA DEFAULT RESPONSEPOLICY
1004 PASSTHRU DEFAULT RESPONSEPOLICY
RESPONSEPOLICYZONE ASAC.CO M
Examples of Substitute and Block Domain Names:
The following example shows a new column, parent_zone, which is added to the spreadsheet while importing an RPZ
ruleset to a local RPZ abc.net:
Example of an A Record CSV format:
Example of an RPZ Policy IP Address:
Example of an RPZ Policy Client IP Address:
Note the following:
• You must specify the name of the parent zone when you import RPZ rules to a local zone. For example,
clarity.abc.net where abc.net is the local RPZ.
• In the above example, the domain name clarity.abc.net is substituted with the domain name clear.in because
clear.in is specified as the canonical name.
• The domain arm.abc.net is blocked and the DNS client receives a message that the domain does not exist. For
more information about RPZ rules, refer to the Infoblox NIOS Administrator Guide.
A B C D E F
HEADER-
RESPONSEPOLICYCNAMERECORD
RESPONSEPOLICYCNAMERECORD CLARITY.ABC.NET CLEAR.IN FALSE ABC.NET DEFAULT
RESPONSEPOLICYCNAMERECORD ARM.ABC.NET FALSE ABC.NET DEFAULT
A B C D E F
HEADER-
RESPONSEPOLICYARECORD
RESPONSEPOLICYCNAMERECORD 10.32.2.1 PQR.ABC.NET FALSE ABC.NET DEFAULT
A B C D E F
HEADER-
RESPONSEPOLICYIPADDRESS
RESPONSEPOLICYIPADDRESS 10.1.2.3.ABC.NET 10.1.2.3 FALSE ABC.NET DEFAULT
A B C D E F
HEADER-
RESPONSEPOLICYCLIENTIPADDRESS
RESPONSEPOLICYCLIENTIPADDRESS 10.1.2.1.ABC.NET 10.1.2.1 FALSE ABC.NET DEFAULT
CSV File Format
Exporting Inheritable Extensible Attributes
When you export data, if an object has inheritable extensible attributes associated with it, then an additional column
EAInherited-XXX is displayed in the spreadsheet, where XXX is the name of the inheritable extensible attribute. Note
that the column EA-XXX displays the name of the inheritable extensible attribute and its value whereas
EAInherited-XXX displays the inheritance state, which is either Inherit or Override. Extensible attributes with the
following inheritance states will be exported: Inherited, Native, and Overridden.
Note the following about inheritable extensible attributes:
• By default, the value is displayed as Override for inheritable extensible attributes, which are at the top of the
inheritance chain or if the value of the inherited extensible attribute is overridden at the descendant level.
• If the value is inherited by the descendants of the parent object, then the inheritance state is set to Inherit.
• If an extensible attribute is not inheritable or if the status is set to Not Inherited, then the EAInherited-XXX
column will not be displayed for these attributes.
• NIOS does not support EA inheritance for DNS objects, but you might see the EAInherited-XXX column in the
CSV file when you export data through Grid Manager. Note that NIOS treats these objects as normal extensible
attributes even when you enable inheritance for extensible attributes.
Importing Inheritable Extensible Attributes
You can specify new inheritable extensible attributes in the spreadsheet and import this file using the CSV Import
feature. When you import inheritable extensible attributes using the CSV Import feature, you must specify two new
columns, EA-XXX and EAInherited-XXX, with relevant values as mentioned in the following tables. Note that XXX is the
name of the inheritable extensible attribute.
For example, if you want to update the value of an existing inheritable extensible attribute Building, you must set the
inheritance state to Override in the spreadsheet. The following example shows that the original value of attribute
Building, which is replaced by Millennium Tower.
The following example shows two new columns, EA-Region and EAInherited-Region, which are added to the
spreadsheet to associate a new inheritable extensible attribute with an existing object:
Note the following about inheritance states:
• When you import attributes for a parent object, the inheritance state must be set to Override.
• For descendants, the inheritance state can be set to Override or Inherit. If you specify Inherit, the attribute value
will be inherited from the parent object. If you specify Override, the original value of the attribute will be
replaced with the value specified in the spreadsheet.
A B C D E
HEADER-
NETWORK
Note: This is valid for Network related objects only. The supported inheritance chain is: Network View -> Network
Container -> Network -> Range -> Host/Fixed Address/Reservation.
Importing Active Directory Domains and Sites
The Infoblox CSV format does not support extensible attributes that contain information about Active Directory
domains and sites or objects that represent Active Directory domains or sites. The appliance displays an error
message when you define values for such extensible attributes in the imported CSV file.
When you export networks, the appliance does not include extensible attributes that contain information about
Active Directory domains or sites in the generated .CSV file.
CSV Import for Topology Rulesets and Rules in DNS Traffic Control
You can import DNS Traffic Control topology rulesets and their rules using the CSV Import feature. You must specify
the topology rulesets and rules separated by commas in the CSV file:
header-dtctopology,name*,comment
dtctopology,topo_server11,TopologyRule
dtctopologyrule,dtc_s11,Server,Rule11,topo_server11,SUBNET/IS_NOT/172.31.0.0/16,1
dtctopologyrule,pool12,Server,Rule12,topo_server11,"COUNTRY/IS/Canada",2
Importing Topology Rulesets and Rules
To import topology rulesets, you must specify the header-topology, name and comment columns in the spreadsheet.
The name column indicates the name of the topology ruleset. To import topology rules, specify the following in the
spreadsheet:
DTCTOPOL
OGY
1
2
DTCTOPOL
OGY
1
Supported Object Types
You must specify the dest_link, dest_type, name, parent, sources, and position columns when you import a CSV file
with topology rules. Note that the dest_link indicates the name of the destination, which is either a pool or server and
position indicates the order of rules in a topology ruleset. The values that you specify for dest_link must exist in the
database. The dest_type indicates the destination type, which can either be a server or a pool. Specify a name for the
topology rule in the name column. In the parent column, you can specify the name of the DTC topology ruleset. The
sources column must contain either a subnet IP address or a geographic location. The appliance displays an error
message if you do not specify valid GeoIP labels when you import a CSV file.
This section describes the supported object types and their corresponding fields for CSV import and export. It also
includes examples of how to create data files. Ensure that you review this information before you import or export a
data file.
Note: All inherited fields follow the override conventions described in Data Specific Guidelines on page 9.
Table 1.4 Supported DNS Object Types
DNS Object Type Required Fields & Syntax IDN Supported
(Yes/No)
Grid DNS Objects Grid DNS Objects on page 20 Yes
Member DNS Objects Member DNS Objects on page 24 Yes
Authoritative Zone Authoritative Zone on page 29 Yes
Forward-Mapping Zone Forward-Mapping Zone on page 34 Yes
Stub Zone Stub Zone on page 35 Yes
Delegated Zone Delegated Zone on page 35 Yes
Authoritative Name Server
Forwarding Member Name
37
Yes
Forward/Stub Server Name
38
Yes
A Record A Record on page 38 Yes
AAAA Record AAAA Record on page 40 Yes
CNAME Record CNAME Record on page 41 Yes
DNAME Record DNAME Record on page 42 Yes
MX Record MX Record on page 43 Yes
NAPTR Record NAPTR Record on page 45 Yes
NS Record NS Record on page 47 Yes (supports only FQDN)
IPv4 Host Address IPv4 Host Address on page 56 No
IPv6 Host Address IPv6 Host Address on page 58 No
Bulk Host Bulk Host on page 60 No
Rulesets NXDOMAIN and Blacklist Rulesets on page 61 No
NXDOMAIN Rule NXDOMAIN Rule on page 62 No
Blacklist Rule Blacklist Rule on page 62 No
Whitelist Rule Whitelist Rule on page 63 No
DNS64 Synthesis Group DNS64 Synthesis Group on page 63 No
Response Policy Zone Response Policy Zone on page 64 No
Response Policy A Record Response Policy A Record on page 65 No
Response Policy AAAA
Response Policy AAAA Record on page 65 No
Response Policy IP A Record Response Policy IP A Record on page 65 No
Response Policy IP AAAA
Response Policy IP AAAA Record on page 66 No
Response Policy MX Record Response Policy MX Record on page 66 No
Response Policy NAPTR
Response Policy NAPTR Record on page 66 No
Response Policy PTR Record Response Policy PTR Record on page 66 No
Response Policy SRV Record Response Policy SRV Record on page 66 No
Response Policy TXT Record Response Policy TXT Record on page 66 No
Response Policy CNAME
Response Policy CNAME Record on page 67 No
Response Policy IP Address Response Policy IP Address on page 67 No
Response Policy Client IP
Response Policy IP Address
Response Policy Client IP
page 69
Dynamic Update Group Dynamic Update Group on page 70 No
(Yes/No)
Note: IDN is not supported for DHCP object types.
Dynamic Update Cluster
DHCP Object Type Required Fields & Syntax
Grid DHCP Grid DHCP Objects on page 70
Member DHCP Member DHCP Objects on page 75
Network View Network View on page 81
DNS View DNS View on page 82
IPv4 Network Container IPv4 Network Container on page 84
IPv4 Network IPv4 Network on page 87
IPv6 Network Container IPv6 Network Container on page 92
IPv6 Network IPv6 Network on page 94
IPv4 Shared Network IPv4 Shared Network on page 97
IPv6 Shared Network IPv6 Shared Network on page 99
IPv4 DHCP Range IPv4 DHCP Range on page 101
IPv6 DHCP Range IPv6 DHCP Range on page 105
IPv4 Fixed Address and Reservation IPv4 Fixed Address/Reservation on page 107
IPv6 Fixed Address IPv6 Fixed Address on page 110
DHCP Fingerprint DHCP Fingerprint on page 112
DHCP MAC Filter DHCP MAC Filter on page 113
MAC Filter Address Item MAC Filter Address on page 114
Option Filter Option Filter on page 116
Option Filter Match Rule Option Filter Match Rule on page 117
DHCP Fingerprint Filter DHCP Fingerprint Filter on page 119
Relay Agent Filter Relay Agent Filter on page 118
NAC Filter DHCP Fingerprint Filter on page 119
IPv4 Option Space IPv4 Option Space on page 121
IPv6 Option Space IPv6 Option Space on page 122
IPv4 Option Definition IPv4 Option Definition on page 122
IPv6 Option Definition IPv6 Option Definition on page 123
(Yes/No)
Grid DNS Objects
addresses in networks and ranges
Permissions for DNS Resources with Associated IP Addresses in Networks and Ranges on page 124
DHCP Failover Association DHCP Failover Association on page 125
Other Supported Objects Required Fields and Syntax
Grid Member Grid Member on page 126
Upgrade Groups
Distribution Schedules
Upgrade Schedules
Named ACLs (access control lists) Named ACLs on page 131
ACES in Named ACLs on page 132
Infoblox Network Insight Discovery Credentials on page 133
Field Name Data Type Required (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-GridDNS String Yes Identifies the first row as a header row
for the Grid DNS objects. Example:
GridDNS
Example: 10800
retry Unsigned
Example: 3600
expire Unsigned
seconds. Example: 2419200
[email protected]
notification. Example: False
Example: False
notify_source_port Unsigned
enable_query_source_port Boolean No Enable query source port. Example:
False
transfers to
NACL1or
“12.0.0.12/Deny,1234::/64/Allow”.
named ACL in this field.
excluded_servers IP address
transfers.
Example: MANY_ANSWERS
an IP address, a network entry, Any or a
TSIG-/permission. If the first value is
not Any or TSIG-, it is assumed to be an
IP address or a network entry. Example:
10.0.0.10/Allow, 11.0.0.0/16/Deny,
named ACL. Example: NACL1.
recursive queries. Example: False
recursive_query_list ACL No It can be an IP address, a network entry,
Any or a TSIG-/permission. If the first
value is not Any or TSIG-, it is assumed
to be an IP address or a network entry.
Example: 10.0.0.10/Allow,
11.0.0.0/16/Deny, TSIG-foo/xyz/Allow.
NACL1.
an IP address, a network entry, Any or a
TSIG-/permission. If the first value is
not Any or TSIG-, it is assumed to be an
IP address or a network entry. Example:
10.0.0.10/Allow, 11.0.0.0/16/Deny,
allow_update_forwarding Boolean No Allow
secondary zones. Example: False
from a bulkhost. Example: Refuse
forwarders_only Boolean No Use
Example: False
enable_custom_root_server Boolean No Indicates the flag to enable custom root
servers. Example: False
servers. Example:
message if the root_name_servers
enable_custom_root_server field is set
False
Example: “NACL” or
the notify messages are sent to the
secondaries. The valid value is
between 5 and 86400 seconds.
Example: 5
responses. Example: False
nxdomain_redirect_addresses IP address
redirect to for nxdomain responses.
Example: “1.1.1.1,2.2.2.2,...”
nxdomain_redirect_ttl Unsigned
nxdomain_log_query Boolean No If you set this to True, the appliance
logs the NXDOMAIN redirections.
Example: False
nxdomain_rulesets Pattern list No Indicates the list of ruleset objects that
are used for NXDOMAIN redirection.
Example: pattern1/MODIFY,
at the Grid level. Example: False
blacklist_redirect_addresses IP address
which the blacklisted queries are
redirected. Example: 1.1.1.1,2.2.2.2
blacklist_action String No Action blacklist_action Indicates the action to be performed
when a domain name matches the
pattern defined in an assigned rule.
Example: Refuse
blacklist_redirect_ttl Unsigned
in seconds. Example: 60
blacklist_log_query Boolean No blacklist_log_
queries are logged. Example: False
blacklist_rulesets List of
blacklist redirection. Example:
False
dns64_groups List of
Example: dns64_groupA,
enable_host_rrset_order flag or False
preserve_host_rrset_order_on_ secondaries
preserve_host_rrset_order_on_second
preserve_host_rrset_order_on_second
value is False. Example: False
filter_aaaa String No Indicates the type of AAAA filtering for
this Grid DNS object. The default value
is No. Example: Yes
filter_aaaa_list ACL No Indicates the list of IPv4 addresses and
networks from which queries are
received. Note that the AAAA filtering is
applied to these addresses. Example:
“12.0.0.12/Deny,13.0.0.0/8/Allow,..”
allowed IP addresses from zone
transfer list into also-notify statement
in named.conf. Example: False
can specify unsigned integers between
10 and 100. The default value is 10.
Example: 10
transfers_out Unsigned
outbound concurrent zone transfers for
the Grid. You can specify unsigned
integers between 10 and 100. The
default value is 10. Example: 10
transfers_per_ns Unsigned
value is two. Example: 2
serial_query_rate Unsigned
max_cache_ttl Unsigned
seconds) for which the server will cache
positive answers. The default value is
604800.
seconds) for which the server will cache
negative (NXDOMAIN) responses. The
allowed value is 604800.
Member DNS Objects
NIOS does not support add and delete operations.
Note: When you export member DNS properties, the CSV file might include the “unbound_logging_level” field with
“OPERATIONS” as the value. Although this field is only applicable to the IB-4030 and IB-4030-10GE
appliances and might not apply to your Grid members, you can still perform CSV import using the CSV export
file that contains this field without any issues.
disable_edns Boolean No Enable or disable EDNS0 support for
queries that require recursive
resolution. The default value is False.
query_rewrite_enabled Boolean No When this is set to True, query rewrite is
enabled at the Grid level. Example:
False
trigger DNS query rewrite.Example:
DNS query rewrite. The default value is
undefined.
ignores RPZ-IP rules with prefix lengths
that are less than the specified prefix
length limit. Example: TRUE
length for RPZ-IP triggers. The default
value is 29.
length for RPZ-IP triggers. The default
value is 112.
seconds between RPZ hit rate checks.
The default interval is 10 seconds.
rpz_hit_rate_min_query Unsigned
queries between RPZ hit rate checks.
The default value is 1000.
rpz_hit_rate_max_query Unsigned
queries between RPZ hit rate checks.
The default value is 100000.
ddns_force_creation_timestamp_u
pdate
update happens even if there is no
change to the resource record.
Header-MemberDns String Yes Identifies the first row as a header
row for the member DNS objects.
Example: MemberDns
Example: member1.infoblox.com
the MGMT port. Example: False
dns_over_lan2 Boolean No Enable or disable DNS services on
the LAN2 port. Example: False
minimal_response Boolean No Enable or disable minimal
response of the DNS server.
Example: False
Example: False
member_view_nats List of
address used for creating glue
records for the view. Example:
dns_view1/INTERFACE/10.10.10.
notify_source_port. Example: False
number.
query_source_port. Example: False
number.
auto-sort. Example: False
member_views List of
Example: dns_view1, dns_view2,..
transfers to
that you can import the name of a
named ACL in this field. Example:
NACL1or
transfers.
Example: MANY_ANSWERS
recursive queries. Example: False
can be an IP address, a network
entry, Any or a TSIG-/permission. If
the first value is not Any or TSIG-, it
is assumed to be an IP address or a
network entry. Example:
can be an IP address, a network
entry, Any or a TSIG-/permission. If
the first value is not Any or TSIG-, it
is assumed to be an IP address or a
network entry.
"NACL1"
recursive client number. Example:
allowed to perform concurrent
Any or a TSIG-/permission. If the
first value is not Any or TSIG-, it is
assumed to be an IP address or a
network entry. Example:
zone updates. Example: False
allow_update_forwarding Boolean No Allow
secondary zones. Example: False
root servers. Example: False
servers. Example:
message if the root_name_servers
the enable_custom_root_server
CSV file.
False
addresses. Example: “NACL” or
delay the notify messages are sent
to the secondaries. The valid value
is between 5 and 86400 seconds.
Example: 5
nxdomain responses. Example:
to redirect to for nxdomain
responses. Example:
in seconds. Example: 60
nxdomain_log_query Boolean No If you set this to True, the appliance
logs the NXDOMAIN redirections.
nxdomain_rulesets Pattern list No Indicates the list of ruleset objects
that are used for NXDOMAIN
redirection. Example:
pattern1/MODIFY, pattern2/PASS,
Grid level. Example: False
redirected. Example:
blacklist_action String No Action blacklist_action Indicates the action to be
performed when a domain name
matches the pattern defined in an
assigned rule. Example: Refuse
DNS responses resulted by
blacklisted queries. Example: 60
blacklist_log_query Boolean No blacklist_log_
blacklist_rulesets List of
are blacklisted at the Grid level.
Example: list1.com, list2.com, ...
False
Example: dns64_groupA,
stored in the hardware acceleration
cache. You can specify unsigned
integer between 60 and 86400.
Default value is 86400.
the IPv6 MGMT port. Example:
False
the IPv6 LAN2 port. Example: False
filter_aaaa String No Indicates the type of AAAA filtering
for this Grid DNS object. The default
value is No. Example: Yes
filter_aaaa_list ACL No Indicates the list of IPv4 addresses
and networks from which queries
are received. Note that the AAAA
filtering is applied to these
addresses. Example:
copy_xfer_to_notify Boolean No Enable or disable copying of the
allowed IP addresses from zone
transfer list into also-notify
statement in named.conf. Example:
concurrent transfers for the Grid.
You can specify unsigned integers
between 10 and 100. The default
value is 10. Example: 10
transfers_out Unsigned
outbound concurrent zone
specify unsigned integers between
10. Example: 10
concurrent transfers per member
unsigned integers between two
Example: 2
serial_query_rate Unsigned
concurrent SOA queries per second
for the Grid. You can specify
unsigned integers between 20 and
100. The default value is 20.
Example: 20
max_cache_ttl Unsigned
cache positive answers. The default
value is 604800.
Authoritative Zone
You can import the name of a named ACL in the fields that support named ACLs, such as allow_transfer, allow_query,
and allow_update.
Note: IDN is supported for object types: fqdn, soa_mname, and soa_email. You can use punycode or IDNs while
importing these objects.
cache negative (NXDOMAIN)
10800. The maximum allowed
for queries that require recursive
resolution. The default value is
False.
query_rewrite_enabled Boolean No When this is set to True, query
rewrite is enabled at the Grid level.
Example: False
admin group. Example: RW
rpz_drop_ip_rule_enabled Boolean No Ignore
ignores RPZ-IP rules with prefix
lengths that are less than the
specified prefix length limit.
default value is 29.
default value is 112.
Header-AuthZone String Yes
zone_format String Yes Valid values are FORWARD, IPV4,and IPV6
view String No DNS view views If no view is specified, the Default view is used.
prefix String No prefix Prefix is used for reverse-mapping RFC2317
zones only. If you include a prefix in a
forward-mapping zone, the appliance ignores
the prefix. No error message is generated.
_new_prefix String No Add this field to overwrite the prefix field when
you select the overwrite or merge option.Use
the hostname of the grid member in this field. Example: infoblox.localdomain
primary servers. Example: True
“hostname/stealth” Example:
Primary
“name/ip/stealth/use_2x_tsig/ use_tsig/tsig_name/tsig_key/
tsig_key_algorithm”. Only name and ip are required fields. If no
value is specified for stealth, use_2x_tsig, and
use_tsig, the default value FALSE is used. If
either use_2x_tsig or use_tsig is TRUE,
tsig_name and tsig_key are required. If no
value is specified for tsig_key_algorithm, the
default value is HMAC-MD5. If both
use_2x_tsig and use_tsig are TRUE, only
use_tsig = TRUE and the tsig key name and key
are imported. Example: "ext1.test.com/1.1.1.1/FALSE"
“hostname/stealth/lead/grid_ replicate”.
specify values for stealth, lead, and
grid_replicate, the default value FALSE is used. Example: "member1.localdomain/FALSE
/TRUE/FALSE"
Secondary
“name/ip/stealth/use_2x_tsig/use_ tsig/tsig_name/tsig_key/
required fields. If no value is specified for
stealth, use_2x_tsig, and use_tsig, the default
value FALSE is used. If either use_2x_tsig or
use_tsig is TRUE, tsig_name and tsig_key are
required. If no value is specified for
tsig_key_algorithm, the default value is
HMAC-MD5. If both use_2x_tsig and use_tsig
are TRUE, only use_tsig = TRUE and the tsig key
name and key are imported. Example: "sec1.com/1.1.1.1/FALSE/FALSE/ FALSE/foo/sdfssdf86ew"
ns_group String No Name server
group
Example: name-ns-group1
disabled Boolean No Disable disable Example: FALSE
create_underscore_ zones
enable_ad_server The Valid value is a list of IP addresses.
Example: “1.1.1.1, 10.0.0.1”
integer
No Refresh soa_refresh When you modify this field to override an
inherited value, you must include values for all
SOA timer fields. The appliance updates all the
SOA timers when you update any of them.
soa_retry Unsigned
integer
No Retry soa_retry Ensure that you include this field when you
override the soa_refresh field.
integer
No Expire soa_expire Ensure that you include this field when you
integer
No Default TTL soa_default_ttl Ensure that you include this field when you
MNAME fields
“foo.localdomain/foobar.localadmin,...”
forwarders...
from...
Permission
table
forward_to Data must be in the following formats: ip address/permission network/network cidr/permission ANY/permission TSIG-XXX/permission Permission can be ALLOW or DENY
If the first value is not Any or TSIG-, it is
assumed to be an IP or network address. Example:
"10.0.0.10/Allow,11.0.0.0/16/Deny,TSIG-foo
/sdfdsfwhsdgfsw8sdf/Allow"
transfers to
allow_update ACL No Allow updates
from
allow_update Example: “13.0.0.0/8/Allow” Note that you can import the name of a named ACL in this field.
allow_query ACL No Allow queries
from
allow_query Example: “127.0.0.1/Allow” Note that you can import the name of a named ACL in this field.
Field Name Data Type Required (Yes/N0)
Examples
This section contains examples of how to create data files for DNS zones. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding DNS Zones
This example shows how to add a forward mapping zone, corp100.com, with a Grid primary and a Grid secondary,
where the grid secondary = hostname/stealth/lead/grid_replicate.
header-authzone,fqdn*,zone_format*,comment,grid_secondaries
authzone,corp100.com,FORWARD,USA,member.infoblox.com/False/ False3
This example shows how to create a data file to add an IPv4 reverse mapping zone, 100.0.0.0/8, with a Grid primary
and an external secondary, where the external secondary = name/ip/stealth/use_2x_tsig/use_tsig/ tsig_name/tsig_key.
header-authzone,fqdn*,zone_format*,external_secondaries
authzone,100.0.0.0/8,IPV4,ns2.com/2.2.2.2/False/False/False/None/None
This example shows how to create a data file to add an IPv6 reverse-mapping zone, 1234::/64, with an external
primary and a Grid secondary, where the external primary = name/ip/stealth/use_2x_tsig/use_tsig/
tsig_name/tsig_key.
Overwriting DNS Zone Data
This example shows how to overwrite a comment from “USA” to “Japan” and remove the Grid secondary.
header-authzone,fqdn*,zone_format*,comment,grid_secondaries
Merging DNS Zone Data
This example shows how to merge the extensible attribute “Site” = “HQ” and add the RW permission to an admin
group “DNS_admins”.
notify_delay Unsigned
No notify_delay This field specifies the seconds of delay the
notify messages are sent to the secondaries.
The valid value is between 5 and 86400
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and examples,
see Data Specific Guidelines on page 9.
EA-Users List No Extensible
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see Data
Specific Guidelines on page 9.
ADMGRP-JoeSmith String No Permissions
permission of a specific admin group. For
information about data format and examples,
see Data Specific Guidelines on page 9.
Field Name Data Type Required (Yes/N0)
header-authzone,fqdn*,zone_format*,ADMGRP-DNS_admins,EA-site
authzone,corp100.com,FORWARD,RW,HQ
This example shows how to add an external secondary with these values:
“ns3.com/2.2.2.2/False/False/False/None/None”.
Adding Named ACL Data
This example shows how to import the names of named ACLs in supported fields, such as allow_transfer,
allow-query, and allow_update:
Forward-Mapping Zone
Note that to delete a parent zone and the associated subzones, you must add remove-subzones column to the CSV
export file and set the value to True. If you want to delete only the parent zone, then you must set this column value
to False.
Header-ForwardZone String Yes Identifies the first row as a header row for the
forward zones. Example: ForwardZone
fqdn FQDN Yes Name zone This field combines the AAAA record name and
the zone name to form the FQDN. Example:
aaaa1.corp100.com
view String No DNS View views If no view is specified, the default view is used.
Example: Default
zone_format String Yes Type Valid values are FORWARD, IPV4,and IPV6.
prefix String No RFC 2317
Prefix
disabled Boolean No Disable disable Enable or disable the forward zone. Example:
FALSE
comment String No Comment comment Example: This is a Forward zone.
forward_to Zone
Example: fwd1.test.com/1.1.1.1/,...
forwarding_servers Forwarding
members list
"infoblox.localdomain,..."
ns_group String No ns_group Forwarding member name server group name.
Example: fwd_ns_group1.
Example: ext_ns_group1.
predefined attributes to the data file. Example:
California.
attributes to the data file. Example: [‘Annie’,
‘John’].
permission of a specific admin group.
Example: RW
Header-StubZone String Yes Identifies the first row as a header row for the
stub zones. Example: StubZone
fqdn FQDN Yes Name zone This field combines the AAAA record name and
the zone name to form the FQDN. Example:
aaaa1.corp100.com
view String No DNS View views If no view is specified, the default view is used.
Example: Default
zone_format String Yes Type Valid values are FORWARD, IPV4,and IPV6.
prefix String No RFC 2317
Prefix
disabled Boolean No Disable disable Enable or disable the stub zone. Example:
FALSE
comment String No Comment comment Example: This is a stub zone.
disable_forwarding Boolean No Do not use
forwarders
stub_from Master
"nm1.test.com/2.2.2.2,..."
ns_group String No ns_group Stub member name server group name.
Example: stub_ns_group1.
Example: ext_ns_group1.
California.
attributes to the data file. Example: [‘Annie’,
‘John’].
permission of a specific admin group.
Example: RW
Header-DelegatedZone String Yes Identifies the first row as a header row for
delegated zones. Example:
DelegatedZone
fqdn FQDN Yes Name zone This field combines the AAAA record
name and the zone name to form the
FQDN. Example: aaaa1.corp100.com
Authoritative Name Server Group
view String No DNS View views If no view is specified, the default view is
used. Example: Default
IPV6.
Prefix
RFC2317 zones only. If you include a
prefix in a forward-mapping zone, the
appliance ignores the prefix. No error
message is generated.
disabled Boolean No Disable disable Enable or disable the zone. Example:
FALSE
delegate_to Delegated
Servers list
Yes Example:
EA-Site String No Extensible
predefined attributes to the data file.
Example: California.
attributes to the data file. Example:
[‘Annie’, ‘John’].
admin permission of a specific admin
group. Example: RW
Header-NsGroup String Yes Identifies the first row as a header row for the
authoritative name server group objects.
Example: AuthoritativeNsGroup.
group_name String Yes Indicates the name of the authoritative name
server group. Example: ns_group1
grid_primaries Grid member
primary stealth List of primary servers of the name server
group. The valid format is:
“hostname/stealth” Example:
Primary
format is:
address are required. If stealth is not
specified, use_2x_tsig and use_tsig are used
and the default value is set to False . Example:
"ext1.test.com/1.1.1.1/FALSE,.."
Secondary
format is:
tsig_name and tsig_key are required.
Example:
is: hostname/stealth/lead/grid_replicate.
assumes default value for stealth. Values are
not specified for lead and grid_replicate fields.
Example:
"member1.localdomain/FALSE/TRUE/FALSE,"
is_grid_default Boolean No Set this to True to set this name server group
as Grid default, set to False to unset this name
server group as Grid default. Example: False
comment String No Comment comment Example: This is a authoritative name server
group.
California.
attributes to the data file. Example: John.
Header-ForwardingM
emberNsGroup
String Yes Identifies the first row as a header row for the
forwarding member name server group
objects. Example:
ForwardingMemberNsGroup.
group_name String Yes Name name Indicates the name of the forwarding member
name server group. Example: fwd_ns_group1
_new_group_name String No You can overwrite the group name.
comment String No Comment comment Example: This is a forwarding member name
server group.
forwarding_servers Forwarding
members list
infoblox.localdomain.
A Record
Note: IDN is supported for object type: fqdn. You can use IDN or punycode while importing this object.
Header-StubMember
NsGroup
stub member name server group objects.
Example: StubMemberNsGroup.
group_name String Yes Name name Indicates the name of the stub member name
server group. Example: stub_ns_group1
comment String No Comment comment Example: This is a stub member name server
group.
EA-XXX String No Extensible
Header-ForwardStub
ServerNsGroup
forward/stub server name server group
objects. Example:
ForwardStubServerNsGroup.
group_name String Yes Name name Indicates the name of the forward/stub server
name server group. Example: ext_ns_group1
comment String No Comment comment Example: This is a forward/stub server name
server group.
external_servers External
server list
EA-XXX String No Extensible
Header-ARecord String Yes Example: ARecord
fqdn FQDN Yes Name name This field combines the A record name
and the zone name to form the FQDN.
Example: a1.corp100.com
Examples
This section contains examples of how to create data files for A records. All examples use comma as the separator.
Adding an A Record
This example shows how to add an A record, bind_a.corp100.com, with the extensible attribute Site = Infoblox, and
the permission, DNS_Admins = RO.
Overwriting A Record Data
This example shows how to modify the permission of the admin group DNS_Admins from RO to DENY in an existing
A record, bind_a.corp100.com.
header-arecord,address*,fqdn*,ADMGRP-DNS_Admins
Merging DNS Zone Data
This example shows how to merge the TTL value = 1280 to an existing A record, bind_a.corp100.com.
_new_fqdn FQDN No Add this field to overwrite the fqdn field
when you select the overwrite or merge
option.
view String No DNS View views If no view is specified, the Default view is
used.
address IP address Yes IP Address ipv4addrss Example: 192.138.1.1
_new_address IP address No Add this field to overwrite the address
field when you select the overwrite or
merge option.
ttl Unsigned
No TTL ttl This is an inherited field. For information,
see Data Specific Guidelines on page 9. Example: 7200
information about data format and
examples, see Data Specific Guidelines
on page 9.
about data format and examples, see
Data Specific Guidelines on page 9.
group. For information about data format
and examples, see Data Specific
Guidelines on page 9.
header-arecord,address*,fqdn*,ttl
AAAA Record
Examples
This section contains examples of how to create data files for AAAA records. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an AAAA Record
This example shows how to add an AAAA record, bind_aaaa.corp100.com, with a comment = add by superuser, and
TTL = 3600.
Header-AaaaRecord String Yes Example: AaaaRecord
fqdn FQDN Yes Name zone This field combines the AAAA record
FQDN. Example: aaaa1.corp100.com
option.
address IPv6 address Yes IP Address ipv6addrss Example: 100::10
_new_address IPv6 address No Add this field to overwrite the address
merge option.
disabled Boolean No Disable disabled Example: FALSE
ttl Unsigned
on page 9.
header-aaaarecord,address*,fqdn*,comment,ttl
aaaarecord,1234:1234::1,bind_aaaa.corp100.co,add by superuser,3600
Overwriting AAAA Record Data
This example shows how to modify an existing AAAA record from address 1234:1234::1 to 1234:1234::2, and TTL
from 3600 to 3800.
This example shows how to disable an existing AAAA record.
header-aaaarecord,address*,fqdn*,disabled
CNAME Record
Note: IDN is supported for object types: fqdn and canonical_name. You can use punycode or IDNs while importing
these objects.
Header-CnameRecord String Yes Example: CnameRecord
fqdn FQDN Yes Alias zone This field combines the CNAME record
FQDN. Example: c1.corp100.com
option.
comment String No Comment comment
ttl Unsigned
on page 9.
Examples
This section contains examples of how to create data files for CNAME records. All examples use comma as the
Adding a CNAME Record
This example shows how to add a CNAME record, bind_cname.corp100.com, to the Default DNS view.
header-cnamerecord,fqdn*,canonical_name*,view
Overwriting CNAME Record Data
This example shows how to override a canonical name from somewhere.corp100.com to somewhere2.corp100.com.
header-cnamerecord,fqdn*,canonical_name*
Merging CNAME Record Data
This example shows how to merge the following data: admin group DNS_Admins with RW permission and extensible
attribute Site = New York.
header-cnamerecord,fqdn*,ADMGRPDNS_Admins,EA-Site
cnamerecord,bind_cname.corp100.com,RW,New York
DNAME Record
Note: IDN is supported for object types: fqdn and target. You can use punycode or IDNs while importing these
objects.
Header-DnameRecord String Yes Example: DnameRecord
fqdn FQDN Yes Alias zone This field combines the DNAME record
FQDN. Example: d1.corp100.com
option.
ttl Unsigned
on page 9.
Examples
This section contains examples of how to create data files for DNAME records. All examples use comma as the
Adding a DNAME Record
This example shows how to add a DNAME record, bind_dname.corp100.com, with target =
bind_dname.corp200.com, extensible attribute Site = HQ, and disabled = TRUE.
header-dnamerecord,fqdn*,target*,disabled,EA-Site
This example shows how to enable the existing DNAME record, bind_dname.corp100.com, and add admin group
DNS_Admins with RO permission.
Merging DNAME Record Data
This example shows how to add a comment to the existing DNAME record, bind_dname.corp100.com, and change
the TTL to 3860.
MX Record
Note: IDN is supported for object types: fqdn and mx. You can use punycode or IDNs while importing these objects.
Header-MxRecord String Yes Example: MxRecord
fqdn FQDN Yes Mail
Example: MX1.corp100.com
option.
Examples
This section contains examples of how to create data files for MX records. All examples use comma as the separator.
Adding an MX Record
This example shows how to add an MX record, bind_mx.corp100.com, with a mail exchanger, exchange.corp100.com
and priority = 20.
header-mxrecord,fqdn*,mx*,priority*
Overwriting MX Record Data
This example shows how to overwrite an existing MX record with a new fqdn, bind_mx2.corp100.com, and a new mail
exchanger, new_exchange.corp100.com.
Merging MX Record Data
This example shows how to merge data to the existing MX record, bind_mx2.corp100.com, by adding inherited TTL
value and extensible attributes Site = USA.
_new_mx Domain
option.
_new_priority Unsigned
merge option.
ttl Unsigned
on page 9.
NAPTR Record
Note: IDN is supported for object types: fqdn and replacement. You can use punycode or IDNs while importing
these objects.
Header-NaptrRecord String Yes Example: NaptrRecord
fqdn FQDN Yes Domain name This field combines the domain name and
the zone name to form the FQDN. Example: aptr1.corp100.com
option.
order Unsigned integer Yes Order order Example: 10
_new_order Unsigned integer No Add this field to overwrite the order field
option.
preference Unsigned integer Yes Preference preference Example: 20
_new_preference Unsigned integer No Add this field to overwrite the preference
merge option.
flags String No Flags flags You can leave this field empty. Example: U
_new_flags String No Add this field to overwrite the flags field
option.
services String No Service services You can leave this field empty. Example: SIP+D2U
_new_services String No Add this field to overwrite the services field
option.
regexp String No REGEX regexp You can leave this field empty. Example: http://([^/:]+)!\1!i
_new_regexp String No Add this field to overwrite the regexp field
option.
_new_replacement String No Add this field to overwrite the replacement
merge option.
Examples
This section contains examples of how to create data files for NPATR records. All examples use comma as the
Adding a NAPTR Record
This example shows how to add a NAPTR record, bind_naptr.corp100.com, with order = 10, preference = 20, and
replacement = corp200.com.
Overwriting NAPTR Record Data
This example shows how to overwrite the FQDN of an existing NAPTR record from bind_naptr.corp100.com to
bind_naptr2.corp100.com.
naptrrecord,bind_naptr.corp100.com,bind_naptr2.corp100.com,10,20,corp200.com
This example shows how to override the preference of an existing NAPTR record from 20 to 25 and replacement from
corp200.com to corp300.com.
Merging NAPTR Record Data
This example shows how to merge Service = http+E2U and TTL = 3600 seconds to an existing NAPTR record.
header-naptrrecord,fqdn*,order*,preference*,replacement*,services,ttl
naptrrecord,bind_naptr.corp100.com,10,25,Corp300.com,http+E2U,3600
ttl Unsigned integer No TTL ttl This is an inherited field. For information,
examples, see Data Specific Guidelines on
page 9.
about data format and examples, see Data
NS Record
Note: When you perform a CSV export of automatically created NS records using Infoblox API, the zone_nameservers
field will have an empty value. Therefore, if you import the previously exported CSV file that includes
automatically created NS records through the Infoblox GUI, then the CSV import fails and Grid Manager
displays an error message.
Examples
This section contains examples of how to create data files for NS records. All examples use comma as the separator.
Adding an NS Record
This example shows how to add an NS record corp100.com in the Default DNS view with DNAME (name server) =
ns1.corp100.com, name server address = 100.0.0.101, and TRUE for adding a PTR Record.
header-nsrecord,fqdn*,view,dname*,zone_nameservers*
nsrecord,corp100.com,default,ns1.corp100.com,“100.0.0.101/TRUE”
This example shows how to add an NS record corp200.com in the Internal DNS view with DNAME (name server) =
ns1.corp200.com and two name server addresses: 200.0.0.101 with TRUE for adding a PTR Record and 200.0.0.102
with TRUE for adding a PTR record.
header-nsrecord,fqdn*,view,dname*,zone_nameservers*
Overwriting NS Record Data
This example shows how to overwrite the DNAME of an existing NS record from ns1.corp100.com to
ns2.corp100.com.
Header-NsRecord String Yes Example: NsRecord
fqdn FQDN Yes Zone name This field combines the domain name
and the zone name to form the FQDN.
Example: test.corp100.com
view String No DNS View views If no view is specified, the Default view
is used. Example: Default
dname Domain name Yes Name Server nameserver Example: ns1.corp100.com
_new_dname Domain name No Add this field to overwrite the dname
merge option.
zone_nameservers Server list Yes Name server list addresses Data must be in the following format:
“IPAddress1/auto_create_ptr1,
IPAddress2/auto_create_ptr2”
This example shows how to overwrite the zone name servers of an existing NS record to 100.0.0.101/TRUE and
100.0.0.102/TRUE.
Merging NS Record Data
This example shows how to merge zone name servers 100.0.0.101/TRUE and 100.0.0.102/TRUE to an NS record.
header-nsrecord,fqdn*,dname*,zone_nameservers*
nsrecord,corp200.com,ns1.corp200.com,“100.0.0.101/TRUE,100.0.0.102/TRUE”
PTR Record
Note: IDN is supported for object types: fqdn and dname. You can use punycode or IDNs while importing these
objects.
fqdn FQDN No Name name zone
This field is required if you do not use
the address field. Either the IP address
or FQDN is required. Example:
10.0.0.10.in.addr.arpa
_new_fqdn Reverse FQDN No Add this field to overwrite the fqdn
field when you use the overwrite or
merge option.
view String No DNS View views If no view is specified, the Default view
is used. Example: Default
This field is required if you do not use
the fqdn field. Either the IP address or
FQDN is required. Example: 10.0.0.11
If the PTR record belongs to a
forward-mapping zone, this field is
empty.
_new_address IP address No Add this field to overwrite the address
field when you use the overwrite or
merge option.
_new_dname FQDN No Add this field to overwrite the dname
merge option.
ttl Unsigned
No TTL ttl This is an inherited field. Example: 28800
EA-Site String No Extensible attribute
Site
predefined attributes to the data file.
For information about data format and
examples, see Data Specific
Examples
This section contains examples of how to create data files for PTR records. All examples use comma as the separator.
Adding a PTR Record
header-ptrrecord,dname*,fqdn
Overwriting PTR Record Data
This example shows how to overwrite an existing PTR record with a new FQDN, 2.0.0.100.in-addr.arpa.
header-ptrrecord,dname*,fqdn
header-ptrrecord,dname*,address
Merging PTR Record Data
This example shows how to change the DNAME of a PTR record from ptr.corp100.com to ptr2.corp100.com, and to
add comment = East Asia.
header-ptrrecord,dname*,_new_dname,comment
ptrrecord,ptr.corp100.com,ptr2.corp100.com,East Asia
TXT Record
ADMGRP-JoeSmith String No Permissions Admin
Group/Role
group. For information about data
format and examples, see Data
Associated GUI Field Associated PAPI Method
fqdn FQDN Yes Name name zone
This field combines the record name and
the zone name to form the FQDN. Example: t1.corp100.com
option.
text String No Text text You can leave this field empty.
Associated GUI Field Associated PAPI Method
Examples
This section contains examples of how to create data files for TXT record data import. All examples use comma as the
Adding a TXT Record
This example shows how to add a TXT record, bind_txt.corp100.com, with text = this is a TXT record and TTL set to
3600 seconds.
header-txtrecord,fqdn*,text,ttl
Overwriting TXT Record Data
This example shows how to overwrite the text field of a TXT record.
header-txtrecord,fqdn*,text,_new_text
txtrecord,bind_txt.corp100.com,this is a TXT record,this is a new TXT record
Merging TXT Record Data
This example shows how to add comment = USA and disabled = TRUE to an existing TXT record.
header-txtrecord,fqdn*,text,comment,disabled
SRV Record
Note: IDN is supported for object types: fqdn and targ

infoblox csv import reference

Documents