RELEASE 8.0. Infoblox CSV Import Reference

Transcription

1 RELEASE 8.0 Infoblox CSV Import Reference

2 Copyright Statements 2016, 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 Product Information Hardware Models Infoblox Advanced Appliances: PT-1400, PT-1405, PT-2200, PT-2205, PT GE, PT-4000, and PT GE 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 GE NetMRI: NetMRI-1102-A, NT-1400, NT-2200, and NT-4000 Document Number: Rev. A Document Updated: October 20, 2016 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.

3 Preface 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: Document Overview on page 4 Documentation Conventions on page 4 Related Documentation on page 4 Customer Care on page 5 User Accounts on page 5 Software Upgrades on page 5 Technical Support on page 5 NIOS 8.0 CSV Import Reference (Rev. A) 3

4 Preface Document Overview The CSV import reference provides general guidelines and file format information about CSV import. It was last updated on October 20, For updated documentation, visit our Support site at Documentation Conventions The text in this guide follows the following style conventions. Style bold data Usage Indicates examples of the field names. Signifies the data in a CSV file. Related Documentation Other Infoblox appliance documentation: Infoblox CLI Guide Infoblox API Documentation Infoblox WAPI Documentation Infoblox CSV Import Reference Infoblox Installation Guide for the Trinzic 100 Appliance Infoblox Installation Guide for the 800 Series Platforms Infoblox Installation Guide for the 805 Series Platforms Infoblox Installation Guide for the 1400 Series Platforms Infoblox Installation Guide for the 1405 Series Platforms Infoblox Installation Guide for the 2200 Series Platforms 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 GE 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 techpubs@infoblox.com. 4 CSV Import Reference (Rev. A) NIOS 8.0

5 Customer Care Customer Care This section addresses user accounts, software upgrades, licenses and warranties, and technical support. 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 to maximize your Technical Support. Technical Support Infoblox Technical Support provides assistance via the Web, , and telephone. The Infoblox Support web site at provides access to product documentation and release notes, but requires the user ID and password you receive when you register your product online at: NIOS 8.0 CSV Import Reference (Rev. A) 5

6 Preface 6 CSV Import Reference (Rev. A) NIOS 8.0

7 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 File Format on page 10 IDN Support for CSV Import on page 11 CSV Import for Response Policy Zones on page 12 CSV Format for Inheritable Extensible Attributes on page 14 Importing Inheritable Extensible Attributes on page 14 Importing Active Directory Domains and Sites on page 15 CSV Import for Topology Rulesets and Rules in DNS Traffic Control on page 15 Supported Object Types on page 16 Importing Multiple Action CSV file on page 134 NIOS 8.0 CSV Import Reference (Rev. A) 7

8 CSV Import Reference Guidelines for CSV Import You can create a data file using a text editor, such as Microsoft tepad, 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. General Guidelines 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. te that Microsoft Excel imports data in the default code page, either in ISO or WINDOWS You must not import a CSV file that is encoded in Windows 1252 or ISO formats. Specify the version number in the first line of the data file. For example, enter version 1.0 in the first line. 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. 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. 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. te that you cannot delete jobs that are already imported. Use the replace function 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. 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. When you stop an import, the appliance finishes importing the data row that it is currently processing before it stops the import. 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. 8 CSV Import Reference (Rev. A) NIOS 8.0

9 Guidelines for CSV Import 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 , the imported data is , 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 16. te that all required fields are marked with an asterisk (*) in an exported file. te: 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. te 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 data types in each supported object type in order for the appliance to overwrite existing data. You can perform a CSV import of an object even if it has been scheduled for addition, modification, or deletion. 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, an address, a URL, or a date in YYYY-MM-DD format. te 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. te that only one value can be specified when importing the extensible attribute. EA-Building is a predefined type for building numbers. It can have a value of 5. EA-TechPubs is a user defined address type. It can have a value of techpubs@infoblox.com. EA-IB is a user defined URL type. It can have a value of EA-Date is a user defined date type attribute. It can have a value of 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. NIOS 8.0 CSV Import Reference (Rev. A) 9

10 CSV Import Reference 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. 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 GE 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 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 16. 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 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 NETWORK HostRecord TRUE host1.dhcp.corp100.com HostRecord TRUE host2.dhcp.corp100.com 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 CSV Import Reference (Rev. A) NIOS 8.0

11 CSV File Format Table 1.2 CSV File Example 2 A B C D E 1 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Secondary Address 2 NETWORK NETWORK HEADER-HostRecord configure_for_dns* FQDN* ADDRESSES 5 HostRecord TRUE host1.dhcp.corp100.com HostRecord TRUE host2.dhcp.corp100.com 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. Table 1.3 CSV File Example 3 A B C D E 1 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Secondary Address 2 NETWORK NETWORK HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Host Range 5 NETWORK NETWORK 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 11. HEADER-NETWORK,ADDRESS*,NETMASK*,EA-Gateway,EA-Secondary Address NETWORK, , , NETWORK, , , , HEADER-HostRecord,FQDN*,ADDRESSES HostRecord,host1.dhcp.corp100.com, HostRecord,host2.dhcp.corp100.com, IDN Support for CSV Import 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. NIOS 8.0 CSV Import Reference (Rev. A) 11

12 CSV Import Reference 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. te 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 16. 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 28 along with the three new columns. However, for RPZ rulesets it supports the values that are listed in CNAME Record on page 40 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 FQDN* ZONE_ FORMAT* ALLOW_UPDATE PRIORITY RPZ_POLICY SUBSTITUTE _NAME VIEW ZONE_TYPE RESPONSEPOLICYZONE ABC.NET FORWARD TSIG-RPZ_LOCAL_UP DATER_KEY._default. abc.net/ka36ujeavm hrh2yqx8hedpc6ok SFcsOb2evyWVAO5f M=/ALLOW/HMAC-S HA256 RESPONSEPOLICYZONE XYZ.IN FORWARD TSIG-RPZ_LOCAL_UP DATER_KEY._default. xyz.in/ka36ujeavmh rh2yqx8hedpc6oksf csob2evywvao5fm= /ALLOW/HMAC-SHA2 56 RESPONSEPOLICYZONE AIM.EDU FORWARD TSIG-RPZ_LOCAL_UP DATER_KEY._default. aim.edu/vielofean4 YZUMOzGIvWnxhtOP XWM5QfJwxfHJbDXjQ =/ALLOW/HMAC-SHA GIVEN DEFAULT RESPONSEPOLICY 1002 NXDOMAIN DEFAULT RESPONSEPOLICY 1003 NODATA DEFAULT RESPONSEPOLICY RESPONSEPOLICYZONE PQDR.C OM FORWARD TSIG-RPZ_LOCAL_UP DATER_KEY._default. pqdr.com/r9tdpx8n +cbs0w32hedzk5m wrjpuh%2feyjssguk sx8sm=/allow/hm AC-SHA PASSTHRU DEFAULT RESPONSEPOLICY RESPONSEPOLICYZONE JKL.INFO FORWARD TSIG-RPZ_LOCAL_UP DATER_KEY._default.j kl.info/rlopr5+sf4m pcfypdjv+kwadttxa U5kFTFWFWuLV2Rw= /ALLOW/HMAC-SHA SUBSTITUTE JKI.NET DEFAULT RESPONSEPOLICY RESPONSEPOLICYZONE ASAC.CO M FORWARD TSIG-RPZ_LOCAL_UP DATER_KEY._default. asac.com/ka36ujeav mhrh2yqx8hedpc6o ksfcsob2evywvao5 fm=/allow/hmac-s HA DISABLED DEFAULT RESPONSEPOLICY 12 CSV Import Reference (Rev. A) NIOS 8.0

13 CSV File Format 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: A B C D E F FQDN* CANONICAL_NAME DISABLED PARENT_ZONE VIEW RESPONSEPOLICYCNAMERECORD CLARITY.ABC.NET CLEAR.IN FALSE ABC.NET DEFAULT RESPONSEPOLICYCNAMERECORD ARM.ABC.NET FALSE ABC.NET DEFAULT Example of an A Record CSV format: A B C D E F RESPONSEPOLICYARECORD ADDRESS* FQDN* DISABLED PARENT_ZONE VIEW RESPONSEPOLICYCNAMERECORD PQR.ABC.NET FALSE ABC.NET DEFAULT Example of an RPZ Policy IP Address: A B C D E F RESPONSEPOLICYIPADDRESS FQDN* CANONICAL_NAME DISABLED PARENT_ZONE VIEW RESPONSEPOLICYIPADDRESS ABC.NET FALSE ABC.NET DEFAULT Example of an RPZ Policy Client IP Address: A B C D E F HEADER- RESPONSEPOLICYCNAMERECORD HEADER- HEADER- HEADER- RESPONSEPOLICYCLIENTIPADDRESS FQDN* CANONICAL_NAME DISABLED PARENT_ZONE VIEW RESPONSEPOLICYCLIENTIPADDRESS ABC.NET FALSE ABC.NET DEFAULT te 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. NIOS 8.0 CSV Import Reference (Rev. A) 13

14 CSV Import Reference CSV Format for Inheritable Extensible Attributes 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. te 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. te 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 t 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. te 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. te 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. A B C D E ADDRESS* NETMASK* EA-Building EAInherited-Building NETWORK Millennium Tower OVERRIDE 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: A B C HEADER- NETWORK HEADER- NETWORK ADDRESS* NETMASK* EA-Region EAInherited-Region NETWORK San Pablo INHERIT te 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. 14 CSV Import Reference (Rev. A) NIOS 8.0

15 CSV File Format te: 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 header-dtctopologyrule,dest_link*,dest_type*,name*,parent*,sources*,position dtctopology,topo_server11,topologyrule dtctopologyrule,dtc_s11,server,rule11,topo_server11,subnet/is_not/ /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: A B C NAME* COMMENT HEADER- DTCTOPOL OGY HEADER- DTCTOPOL OGYRULE DTCTOPOL OGY DEST_LINK* DEST_TYPE* NAME* PARENT* SOURCES* POSITION topo_server1 Topology Server 1 DTCTOPOL OGYRULE DTCTOPOL OGYRULE DTCTOPOL OGY DTCTOPOL OGYRULE dtc_s1 SERVER RULE1 topo_server1 SUBNET/IS/ /8 dtc_s2 SERVER RULE2 topo_server1 SUBNET/IS/ /16 topo_pool1 Topology Pool 3 pool1 POOL RULE3 topo_pool1 COUNTRY/IS/Antar ctica,continent/i S/Africa,SUBDIVISI ON/IS/Aden NIOS 8.0 CSV Import Reference (Rev. A) 15

16 CSV Import Reference You must specify the dest_link, dest_type, name, parent, sources, and position columns when you import a CSV file with topology rules. te 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. Supported Object Types 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. te: 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 s & Syntax Grid DNS Objects Grid DNS Objects on page 19 Yes Member DNS Objects Member DNS Objects on page 23 Yes Authoritative Zone Authoritative Zone on page 28 Yes Forward-Mapping Zone Forward-Mapping Zone on page 33 Yes Stub Zone Stub Zone on page 34 Yes Delegated Zone Delegated Zone on page 34 Yes Authoritative Name Server Group Forwarding Member Name Server Group Stub Member Name Server Group Forward/Stub Server Name Server Group Authoritative Name Server Group on page 35 Forwarding Member Name Server Group on page 36 Stub Member Name Server Group on page 37 Forward/Stub Server Name Server Group on page 37 A Record A Record on page 37 Yes AAAA Record AAAA Record on page 39 Yes CNAME Record CNAME Record on page 40 Yes DNAME Record DNAME Record on page 41 Yes MX Record MX Record on page 42 Yes NAPTR Record NAPTR Record on page 44 Yes IDN Supported (Yes/) NS Record NS Record on page 46 Yes (supports only FQDN) Yes Yes Yes Yes 16 CSV Import Reference (Rev. A) NIOS 8.0

17 Supported Object Types DNS Object Type PTR Record PTR Record on page 47 Yes SRV Record SRV Record on page 49 Yes TXT Record TXT Record on page 48 Yes TLSA Record TLSA Record on page 51 Host Record Host Record on page 53 Yes IPv4 Host Address IPv4 Host Address on page 55 IPv6 Host Address IPv6 Host Address on page 57 Bulk Host Bulk Host on page 59 Rulesets NXDOMAIN and Blacklist Rulesets on page 60 NXDOMAIN Rule NXDOMAIN Rule on page 61 Blacklist Rule Blacklist Rule on page 61 Whitelist Rule Whitelist Rule on page 62 DNS64 Synthesis Group DNS64 Synthesis Group on page 62 Response Policy Zone Response Policy Zone on page 63 Response Policy A Record Response Policy A Record on page 64 Response Policy AAAA Record Response Policy AAAA Record on page 64 Response Policy IP A Record Response Policy IP A Record on page 64 Response Policy IP AAAA Record Response Policy IP AAAA Record on page 65 Response Policy MX Record Response Policy MX Record on page 65 Response Policy NAPTR Record Response Policy NAPTR Record on page 65 Response Policy PTR Record Response Policy PTR Record on page 65 Response Policy SRV Record Response Policy SRV Record on page 65 Response Policy TXT Record Response Policy TXT Record on page 65 Response Policy CNAME Record Response Policy CNAME Record on page 66 Response Policy IP Address Response Policy IP Address on page 66 Response Policy Client IP Address Response Policy IP Address CNAME Response Policy Client IP Address CNAME s & Syntax Response Policy Client IP Address on page 66 Response Policy IP Address CNAME on page 67 Response Policy Client IP Address CNAME on page 68 Dynamic Update Group Dynamic Update Group on page 69 IDN Supported (Yes/) NIOS 8.0 CSV Import Reference (Rev. A) 17

18 CSV Import Reference DNS Object Type Dynamic Update Cluster Group s & Syntax Dynamic Update Cluster Group on page 69 IDN Supported (Yes/) Table 1.5 Supported DHCP Object Types te: IDN is not supported for DHCP object types. DHCP Object Type s & Syntax Grid DHCP Grid DHCP Objects on page 69 Member DHCP Member DHCP Objects on page 74 Network View Network View on page 80 DNS View DNS View on page 80 IPv4 Network Container IPv4 Network Container on page 83 IPv4 Network IPv4 Network on page 86 IPv6 Network Container IPv6 Network Container on page 90 IPv6 Network IPv6 Network on page 93 IPv4 Shared Network IPv4 Shared Network on page 96 IPv6 Shared Network IPv6 Shared Network on page 98 IPv4 DHCP Range IPv4 DHCP Range on page 99 IPv6 DHCP Range IPv6 DHCP Range on page 104 IPv4 Fixed Address and Reservation IPv4 Fixed Address/Reservation on page 106 IPv6 Fixed Address IPv6 Fixed Address on page 109 DHCP Fingerprint DHCP Fingerprint on page 111 DHCP MAC Filter DHCP MAC Filter on page 112 MAC Filter Address Item MAC Filter Address on page 113 Option Filter Option Filter on page 115 Option Filter Match Rule Option Filter Match Rule on page 116 DHCP Fingerprint Filter DHCP Fingerprint Filter on page 118 Relay Agent Filter Relay Agent Filter on page 117 NAC Filter DHCP Fingerprint Filter on page 118 IPv4 Option Space IPv4 Option Space on page 120 IPv6 Option Space IPv6 Option Space on page 121 IPv4 Option Definition IPv4 Option Definition on page 121 IPv6 Option Definition IPv6 Option Definition on page CSV Import Reference (Rev. A) NIOS 8.0

19 Supported Object Types DHCP Object Type Permissions for DNS resources with associated IP addresses in networks and ranges s & Syntax Permissions for DNS Resources with Associated IP Addresses in Networks and Ranges on page 123 DHCP Failover Association DHCP Failover Association on page 124 Table 1.6 Other Supported Objects Other Supported Objects s and Syntax Grid Member Grid Member on page 125 Upgrade Groups Distribution Schedules Upgrade Schedules Upgrade Groups and Schedules on page 129 Named ACLs (access control lists) Named ACLs on page 130 ACES in Named ACLs on page 131 Infoblox Network Insight Discovery Credentials on page 132 Grid DNS Objects (Yes/) Associated GUI Header-GridDNS String Yes Identifies the first row as a header row for the Grid DNS objects. Example: GridDNS refresh Indicates the refresh time in seconds. Example: retry Indicates the retry time in seconds. Example: 3600 expire Indicates the expiration time in seconds. Example: default_ttl Indicates the default TTL value in seconds. Example: negative_ttl Indicates the negative TTL value in seconds. Example: 900 lame_ttl Indicates the lame TTL value in seconds. Example: 600 String Indicates the address. Example: admin@xyz.com enable_secondary_notify Boolean Enable Grid secondaries to send notification. Example: False enable_notify_source_port Boolean Enable notification source port Example: False notify_source_port Indicates notify-source port number. enable_query_source_port Boolean Enable query source port. Example: False NIOS 8.0 CSV Import Reference (Rev. A) 19

20 CSV Import Reference (Yes/) Associated GUI query_source_port Indicates query-source port number. allow_transfer ACL Allow zone transfers to allow_transfer List of address_tsig_ac items. Example: NACL1or /Deny,1234::/64/Allow. te that you can import the name of a named ACL in this field. excluded_servers IP address list List of excluded servers for zone transfers. zone_transfer_format_option String Indicates the zone transfer format. Example: MANY_ANSWERS allow_query ACL Allow queries from allow_query List of address_tsig_ac items. 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: /Allow, /16/Deny, TSIG-foo/xyz/Allow. It can also be a named ACL. Example: NACL1. recursion_enabled Boolean Indicates the flag to respond to recursive queries. Example: False recursive_query_list ACL 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: /Allow, /16/Deny, TSIG-foo/xyz/Allow. It can also be a named ACL. Example: NACL1. allow_update ACL Allow updates from allow_update_forwarding Boolean Allow updates from allow_update forward_to List of address_tsig_ac items. 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: /Allow, /16/Deny, TSIG-foo/xyz/Allow. It can also be a named ACL. Example: NACL1. Enable update forwarding for secondary zones. Example: False allow_bulkhost_ddns String Enable updates to PTR records sourced from a bulkhost. Example: Refuse forwarders_only Boolean Use Forwarders Only Enable use of forwarders only. Example: False allow_forwarder IP address list Indicates the list of forwarders. enable_custom_root_server Boolean Indicates the flag to enable custom root servers. Example: False 20 CSV Import Reference (Rev. A) NIOS 8.0

21 Supported Object Types (Yes/) Associated GUI root_name_servers Root nameserver list Indicates the list of custom root servers. Example: rnm1.test.com/ /,... The appliance displays an error message if the root_name_servers column has an empty value when the enable_custom_root_server field is set to True in the imported CSV file. enable_blackhole Boolean Enable blackhole setting. Example: False blackhole ACL Indicates the list of banned addresses. Example: NACL or /Deny,1234::/64/Allow,.. notify_delay notify_delay This field specifies the seconds of delay the notify messages are sent to the secondaries. The valid value is between 5 and seconds. Example: 5 enable_nxdomain_redirect Boolean Enable intercept and redirect nxdomain responses. Example: False nxdomain_redirect_addresses IP address list Indicates the list of IPv4 addresses to redirect to for nxdomain responses. Example: , ,... nxdomain_redirect_ttl Indicates the NXDOMAIN redirect ttl in seconds. Example: 60 nxdomain_log_query Boolean If you set this to True, the appliance logs the NXDOMAIN redirections. Example: False nxdomain_rulesets Pattern list Indicates the list of ruleset objects that are used for NXDOMAIN redirection. Example: pattern1/modify, pattern2/pass,... enable_blacklist Boolean enable_blacklist Enable or disable blacklist redirection at the Grid level. Example: False blacklist_redirect_addresses IP address list blacklist_ redirect_ addresses Indicates the list of IPv4 addresses to which the blacklisted queries are redirected. Example: , blacklist_action String 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 blacklist_ redirect_ttl Indicates the blacklist redirect TTL value in seconds. Example: 60 blacklist_log_query Boolean blacklist_log_ query When this is set to True, blacklisted queries are logged. Example: False blacklist_rulesets List of domain names blacklist_ rulesets List of ruleset objects that are used for blacklist redirection. Example: list1.com, list2.com,... enable_dns64 Boolean Enable DNS64 synthesis. Example: False NIOS 8.0 CSV Import Reference (Rev. A) 21

22 CSV Import Reference (Yes/) Associated GUI dns64_groups List of Dns64 groups List of SynthesisGroup objects. Example: dns64_groupa, dns64_groupb,... host_rrset_order Boolean Specify True to set the enable_host_rrset_order flag or False to deactivate enable_host_rrset_order value at the Grid level. Example: False preserve_host_rrset_order_on_ secondaries Boolean Specify True to set the preserve_host_rrset_order_on_second aries flag or False to deactivate preserve_host_rrset_order_on_second aries value at the Grid level. The default value is False. Example: False filter_aaaa String Indicates the type of AAAA filtering for this Grid DNS object. The default value is. Example: Yes filter_aaaa_list ACL Indicates the list of IPv4 addresses and networks from which queries are received. te that the AAAA filtering is applied to these addresses. Example: /Deny, /8/Allow,.. or NACL1 copy_xfer_to_notify Boolean Enable or disable copying of the allowed IP addresses from zone transfer list into also-notify statement in named.conf. Example: False transfers_in Indicates the number of maximum concurrent transfers for the Grid. You can specify unsigned s between 10 and 100. The default value is 10. Example: 10 transfers_out Indicates the number of maximum outbound concurrent zone transfers for the Grid. You can specify unsigned s between 10 and 100. The default value is 10. Example: 10 transfers_per_ns Indicates the number of maximum concurrent transfers per member for the Grid. You can specify unsigned s between two and 100. The default value is two. Example: 2 serial_query_rate Indicates the number of maximum concurrent SOA queries per second for the Grid. You can specify unsigned s between 20 and 100. The default value is 20. Example: 20 max_cache_ttl Indicates the maximum time (in seconds) for which the server will cache positive answers. The default value is max_ncache_ttl Indicates the maximum time (in seconds) for which the server will cache negative (NXDOMAIN) responses. The default value is The maximum allowed value is CSV Import Reference (Rev. A) NIOS 8.0

23 Supported Object Types (Yes/) Associated GUI disable_edns Boolean Enable or disable EDNS0 support for queries that require recursive resolution. The default value is False. query_rewrite_enabled Boolean When this is set to True, query rewrite is enabled at the Grid level. Example: False query_rewrite_domain_names List of domain names Indicates the list of domain names that trigger DNS query rewrite.example: aa.com, bb.com. query_rewrite_prefix String Indicates the domain name prefix for DNS query rewrite. The default value is undefined. rpz_drop_ip_rule_enabled Boolean Ignore RPZ-IP triggers with too small prefix lengths When this is set to True, DNS server ignores RPZ-IP rules with prefix lengths that are less than the specified prefix length limit. Example: TRUE rpz_drop_ip_rule_min_prefix_leng th_ipv4 Integer Minimum IPv4 Prefix Length Indicates the minimum IPv4 prefix length for RPZ-IP triggers. The default value is 29. rpz_drop_ip_rule_min_prefix_leng th_ipv6 Integer Minimum IPv6 Prefix Length Indicates the minimum IPv6 prefix length for RPZ-IP triggers. The default value is 112. rpz_hit_rate_interval Integer Interval Indicates the minimum time interval in seconds between RPZ hit rate checks. The default interval is 10 seconds. rpz_hit_rate_min_query Integer Minimum query Indicates the minimum number of queries between RPZ hit rate checks. The default value is rpz_hit_rate_max_query Integer Maximum query Indicates the maximum number of queries between RPZ hit rate checks. The default value is Member DNS Objects NIOS does not support add and delete operations. te: 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 GE 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. (Yes/) Associated GUI Header-MemberDns String Yes Identifies the first row as a header row for the member DNS objects. Example: MemberDns parent FQDN Yes Indicates the parent object. Example: member1.infoblox.com NIOS 8.0 CSV Import Reference (Rev. A) 23

24 CSV Import Reference (Yes/) Associated GUI dns_over_mgmt Boolean Enable or disable DNS services on the MGMT port. Example: False dns_over_lan2 Boolean Enable or disable DNS services on the LAN2 port. Example: False minimal_response Boolean Enable or disable minimal response of the DNS server. Example: False forwarders_only Boolean Use Forwarders Only Enable use of forwarders only. Example: False allow_forwarder IP address list Indicates the list of forwarders. member_view_nats List of Member view NATs Indicates the list of views with NAT address used for creating glue records for the view. Example: dns_view1/interface/ enable_notify_source_port Boolean Enable or disable notify_source_port. Example: False notify_source_port Indicates the notify source port number. enable_query_source_port Boolean Enable or disable query_source_port. Example: False query_source_port Indicates the query source port number. lame_ttl Indicates the lame TTL value in seconds. Example: 600 auto_sort_views Boolean Enable or disable DNS views auto-sort. Example: False member_views List of Member views Indicates the list of member views. Example: dns_view1, dns_view2,.. allow_transfer ACL Allow zone transfers to allow_transfer List of address_tsig_ac items.te that you can import the name of a named ACL in this field. Example: NACL1or /Deny,1234::/64/ Allow. excluded_servers IP address list List of excluded servers for zone transfers. zone_transfer_format_option String Indicates the zone transfer format. Example: MANY_ANSWERS recursion_enabled Boolean Indicates the flag to respond to recursive queries. Example: False 24 CSV Import Reference (Rev. A) NIOS 8.0

25 Supported Object Types (Yes/) Associated GUI allow_query ACL Allow queries from allow_query List of address_tsig_ac items. 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: /Allow, /16/Deny, TSIG-foo/xyz/Allow. It can also be a named ACL. Example: NACL1. allow_recursive_query ACL List of address_tsig_ac items. 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:" /Allow, /16/Deny,TSIG-foo/xyz/Allow,.." or it can be a named ACL. Example: "NACL1" limit_concurrent_recursive_clients Boolean Enable limit of concurrent recursive client number. Example: False concurrent_recursive_clients Indicates the number of clients allowed to perform concurrent queries. Example: 1000 allow_update ACL Allow updates from allow_update List of address_tsig_ac items. 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: /Allow, /16/Deny, TSIG-foo/xyz/Allow. It can also be a named ACL. Example: NACL1. allow_gss_tsig_zone_updates Boolean Allow GSS-TSIG clients to perform zone updates. Example: False allow_update_forwarding Boolean Allow updates from forward_to Enable update forwarding for secondary zones. Example: False enable_custom_root_server Boolean Indicates the flag to enable custom root servers. Example: False root_name_servers Root nameserver list Indicates the list of custom root servers. Example: rnm1.test.com/ /,. The appliance displays an error message if the root_name_servers column has an empty value when the enable_custom_root_server field is set to True in the imported CSV file. enable_blackhole Boolean Enable blackhole setting. Example: False NIOS 8.0 CSV Import Reference (Rev. A) 25