RELEASE Infoblox CSV Import Reference

Transcription

1 RELEASE 6.11 Infoblox CSV Import Reference

2 Copyright Statements 2015, 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 Trinzic product line: 100, 810, 820, 1410, 1420, 2210, 2220, and Infoblox-4010 Network Insight: ND-800, ND-1400, ND-2200, and ND-4000 Trinzic Reporting: 1400, 2000, 2200, and 4000 Advanced DNS Protection: PT-1400, PT-2200, PT4000 Infoblox-4030 DNS Caching Accelerator Appliance Infoblox-250-A, -550-A, A, A, A, A, and A Network Automation: NetMRI-1102-A, NT-1400, NT-2200, and NT-4000 Document Number: Rev. B Document Updated: February 26, 2015 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 accessing 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 6.11 CSV Import Reference (Rev. B) 3

4 Preface Document Overview The CSV import reference provides general guidelines and file format information about CSV import. It was last updated on February 26, 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 NIOS Administrator Guide Infoblox API Documentation Infoblox CLI Guide Infoblox Installation Guide for the Trinzic 100 Appliance Infoblox Installation Guide for the Trinzic 800 Series and Network Insight ND-800 Platforms Infoblox Installation Guide for the Trinzic 1400 Series and Network Insight ND-1400 Platforms Infoblox Installation Guide for the Trinzic 2200 Series and Network Insight ND-2200 Platforms Infoblox Installation Guide for the Infoblox-4010 and Network Insight ND-4000 Platforms Infoblox Installation Guide for Infoblox Advanced Appliance PT-1400 Infoblox Installation Guide for Infoblox Advanced Appliance PT-2200 Infoblox Installation Guide for Infoblox Advanced Appliance PT-4000 Infoblox Installation Guide for the Infoblox-4030 Appliance Infoblox DNS Caching Acceleration Application Guide Infoblox Installation Guide for the Trinzic Reporting 1400 Appliance Infoblox Installation Guide for the Trinzic Reporting 2000 Appliance Infoblox Installation Guide for the Trinzic Reporting 2200 Appliance Infoblox Installation Guide for the Trinzic Reporting 4000 Appliance Infoblox Installation Guide for the Infoblox-250-A Appliance Infoblox Installation Guide for the Infoblox-550-A, A, A, and A Appliances Infoblox Installation Guide for the Infoblox-1852-A Appliance Infoblox Installation Guide for the Infoblox-2000-A Appliance Infoblox Installation Guide for vnios Software on Riverbed Services Platforms Infoblox Installation Guide for Installing vnios Software on Cisco Platforms Infoblox Installation Guide for vnios Software on VMware Infoblox Installation Guide for vnios on Microsoft 2008 R2 for Hyper-V Quick Start Guide for Installing vibos Software on VMware Platforms 4 CSV Import Reference (Rev. B) NIOS 6.11

5 Customer Care Infoblox IBOS Administrator Guide Infoblox Safety Guide To provide feedback on any of the Infoblox technical documents, please 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 6.11 CSV Import Reference (Rev. B) 5

6 Preface 6 CSV Import Reference (Rev. B) NIOS 6.11

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 8 CSV File Format on page 10 Supported Object Types on page 15 NIOS 6.11 CSV Import Reference (Rev. B) 7

8 CSV Import Reference 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. 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. Note 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 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. 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. 8 CSV Import Reference (Rev. B) NIOS 6.11

9 Guidelines for CSV Import For each supported object type, you must include all the required fields in the data file. For information, see Supported Object Types on page 15. 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 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. 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 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. 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. NIOS 6.11 CSV Import Reference (Rev. B) 9

10 CSV Import Reference 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 15. 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. B) NIOS 6.11

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 6.11 CSV Import Reference (Rev. B) 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. 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 15. 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 DNS Zone on page 17 along with the three new columns. However, for RPZ rulesets it supports the values that are listed in CNAME Record on page 23 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. B) NIOS 6.11

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 HEADER- RESPONSEPOLICYCNAMERECORD HEADER- RESPONSEPOLICYARECORD ADDRESS* FQDN* DISABLED PARENT_ZONE VIEW RESPONSEPOLICYCNAMERECORD PQR.ABC.NET FALSE ABC.NET DEFAULT 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. 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. 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. NIOS 6.11 CSV Import Reference (Rev. B) 13

14 CSV Import Reference 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. A B C D E NETWORK 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- HEADER- NETWORK ADDRESS* NETMASK* EA-Region EAInherited-Region NETWORK San Pablo INHERIT 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. Note: This is valid for Network related objects only. The supported inheritance chain is: Network View -> Network Container -> Network -> Range -> Host/Fixed Address/Reservation. 14 CSV Import Reference (Rev. B) NIOS 6.11

15 Supported Object Types 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. Note: All inherited fields follow the override conventions described in Data Specific Guidelines on page 8. Table 1.4 Supported DNS Object Types DNS Object Type s & Syntax Authoritative Zone Authoritative DNS Zone on page 17. Yes A Record A Record on page 21 Yes AAAA Record AAAA Record on page 22 Yes CNAME Record CNAME Record on page 23 Yes DNAME Record DNAME Record on page 24 Yes MX Record MX Record on page 26 Yes NAPTR Record NAPTR Record on page 27 Yes IDN Supported NS Record NS Record on page 29 Yes (supports only FQDN) PTR Record PTR Record on page 30 Yes SRV Record SRV Record on page 33 Yes TXT Record TXT Record on page 32 Yes Host Record Host Record on page 35 Yes IPv4 Host Address IPv4 Host Address on page 37 No IPv6 Host Address IPv6 Host Address on page 39 No Rulesets NXDOMAIN and Blacklist Rulesets on page 41 No NXDOMAIN Rule NXDOMAIN Rule on page 42 No Blacklist Rule Blacklist Rule on page 42 No DNS64 Synthesis Group DNS64 Synthesis Group on page 43 No Table 1.5 Supported DHCP Object Types Note: IDN is not supported for DHCP object types. DHCP Object Type s & Syntax IPv4 Network IPv4 Network on page 44 IPv6 Network IPv6 Network on page 48 IPv4 Shared Network IPv4 Shared Network on page 51 NIOS 6.11 CSV Import Reference (Rev. B) 15

16 CSV Import Reference DHCP Object Type s & Syntax IPv6 Shared Network IPv6 Shared Network on page 53 IPv4 DHCP Range IPv4 DHCP Range on page 54 IPv6 DHCP Range IPv6 DHCP Range on page 58 IPv4 Fixed Address and Reservation IPv4 Fixed Address/Reservation on page 60 IPv6 Fixed Address IPv6 Fixed Address on page 63 DHCP Fingerprint DHCP Fingerprint on page 66 DHCP MAC Filter DHCP MAC Filter on page 67 MAC Filter Address Item MAC Filter Address on page 68 Option Filter Option Filter on page 70 Option Filter Match Rule Option Filter Match Rule on page 71 DHCP Fingerprint Filter DHCP Fingerprint Filter on page 73 Relay Agent Filter Relay Agent Filter on page 72 NAC Filter DHCP Fingerprint Filter on page 73 IPv4 Option Space IPv4 Option Space on page 75 IPv6 Option Space IPv6 Option Space on page 76 IPv4 Option Definition IPv4 Option Definition on page 76 IPv6 Option Definition IPv6 Option Definition on page 77 Permissions for DNS resources with associated IP addresses in networks and ranges Permissions for DNS Resources with Associated IP Addresses in Networks and Ranges on page 78 Table 1.6 Other Supported Objects Upgrades Upgrade Groups Distribution Schedules Upgrade Schedules s and Syntax Upgrade Groups and Schedules on page 79 Named ACLs (access control lists) Named ACLs on page 80 ACES in Named ACLs on page 81 Infoblox Network Insight Discovery Credentials on page CSV Import Reference (Rev. B) NIOS 6.11

17 Supported Object Types Authoritative DNS 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_ . You can use punycode or IDNs while importing these objects. (Yes/N0) Associated GUI Header-AuthZone String Yes fqdn FQDN Yes Name name Example: test.com 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 is_multimaster Boolean No Multi-master is_multimaster Indicates whether the zone has multiple primary servers. Example: True grid_primaries Grid member list and stealth state No Grid Primary/ Stealth primary stealth Data must be in the following format: hostname/stealth Example: foo.localadmin/false,corp1.com/true,... grid_primary Grid member No Grid Primary primary external_primaries Server list No External Primary primary Data must be in the following format: 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/ /false" grid_secondaries Member server list No Grid Secondary secondaries Data must be in the following format: hostname/stealth/lead/grid_ replicate. Only hostname is required. If you do not specify values for stealth, lead, and grid_replicate, the default value FALSE is used. Example: "member1.localdomain/false /TRUE/FALSE" NIOS 6.11 CSV Import Reference (Rev. B) 17

18 CSV Import Reference (Yes/N0) Associated GUI external_secondaries Server list No External Secondary ns_group String No Name server group secondaries ns_group Data must be in the following format: 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: "sec1.com/ /false/false/ FALSE/foo/sdfssdf86ew" Example: name-ns-group1 comment String No Comment comment disabled Boolean No Disable disable Example: FALSE create_underscore_ zones Boolean No Automatically create underscore zones create_underscore_ zones Example: FALSE allow_active_dir List of IP addresses No Allow unsigned updates from these domain controllers enable_ad_server The Valid value is a list of IP addresses. Example: , soa_refresh soa_retry soa_expire soa_default_ttl 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. No Retry soa_retry Ensure that you include this field when you override the soa_refresh field. No Expire soa_expire Ensure that you include this field when you override the soa_refresh field. No Default TTL soa_default_ttl Ensure that you include this field when you override the soa_refresh field. soa_negative_ttl No Negativecaching TTL soa_negative_ttl Ensure that you include this field when you override the soa_refresh field. soa_mnames FQDN list No List of SOA MNAME fields soa_mname Data must include the FQDN and hostname Example: foo.localdomain/foobar.localadmin,... soa_ address No address for SOA MNAME field soa_ Example: root@test.com soa_serial_number No Serial Number soa_serial_number disable_forwarding Boolean No Don t user forwarders... disable_forwarding Example: TRUE 18 CSV Import Reference (Rev. B) NIOS 6.11

19 Supported Object Types (Yes/N0) Associated GUI allow_update_ forwarding Boolean No Allow updates from forward_to Example: FALSE update_forwarding ACL No Allow updates from... Permission table allow_transfer ACL No Allow zone transfers to allow_update ACL No Allow updates from allow_query ACL No Allow queries from forward_to allow_transfer allow_update allow_query 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: " /Allow, /16/Deny,TSIG-foo /sdfdsfwhsdgfsw8sdf/allow" Example: " /Deny,1234::/64/Allow" Note that you can import the name of a named ACL in this field. Example: /8/Allow Note that you can import the name of a named ACL in this field. Example: /Allow Note that you can import the name of a named ACL in this field. notify_delay 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 seconds. Example: 10 EA-Site String No Extensible attribute EA-Users List No Extensible attribute ADMGRP-JoeSmith String No Permissions Admin Group/Role extensible_attributes extensible_attributes permission EA-Site is an example of a predefined 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 8. EA-Users is an example of a user defined 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 8. ADMGRP-JoeSmith is an example of an admin permission of a specific admin group. For information about data format and examples, see Data Specific Guidelines on page 8. 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 gird secondary = hostname/stealth/lead/grid_replicate. header-authzone,fqdn*,zone_format*,comment,grid_primary,grid_primary_stealth, grid_secondaries authzone,corp100.com,forward,usa,grid.infoblox.com,false,member.infoblox.com/false/ False3 NIOS 6.11 CSV Import Reference (Rev. B) 19

20 CSV Import Reference This example shows how to create a data file to add an IPv4 reverse mapping zone, /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,grid_primary, grid_primary_stealth authzone, /8,ipv4,ns2.com/ /false/false/false/none/none, grid.infoblox.com,false 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. header-authzone,fqdn*,zone_format*,external_primaries,grid_secondaries authzone,1234::/64,ipv6,ns1.com/ /false/false/false/none/none, member.infoblox.com/false/false/false 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_primary,grid_primary_stealth,grid_seco ndaries authzone,corp100.com,forward,japan,grid.infoblox.com,false This example shows how to overwrite a Grid primary from grid.infoblox.com to member.infoblox.com. header-authzone,fqdn*,zone_format*,external_secondaries,grid_primary, grid_primary_stealth authzone, /8,ipv4,ns2.com/ /false/false/false/none/none, member.infoblox.com,false 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. 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/ /false/false/false/none/none. header-authzone,fqdn*,zone_format*,external_secondaries,grid_primary, grid_primary_stealth authzone, /8,ipv4,ns2.com/ /false/false/false/none/none,ns3.com/ / False/False/False/None/None,FALSE 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: Header-authzone,fqdn*,grid_primary,view,external_secondaries,allow_transfer,allow_quer y,zone_type,allow_active_dir,allow_update,zone_format,notify_delay,disabled,grid_prima ry_stealth,soa_negative_ttl,soa_mname,soa_default_ttl,soa_retry,,create_underscore_zon es,soa_serial_number,soa_ ,comment,soa_expire,soa_refresh authzone,test_data_export.com,infoblox.localdomain,default,test_data.infoblox.com/ /TRUE," /Deny,1234::/64/Allow",My_Named_ACL,Authoritative, ,"1234::/6 4/Allow",FORWARD,100,FALSE,FALSE,100,mname2,300,600,FALSE,FALSE,1,soa @infoblox.co m,authzone2,200,500 authzone,test_csv_export.com,infoblox.localdomain,default,test_csv.infoblox.com/ /TRUE,My_Named_ACL," /Deny,1234::/64/Allow",, ,"4321::/64/Allow",FORWAR D,100,FALSE,FALSE,400,mname1,900,800,FALSE,FALSE,1,tel@infoblox.com,Authzone1,100, CSV Import Reference (Rev. B) NIOS 6.11

21 Supported Object Types A Record Note: IDN is supported for object type: fqdn. You can use IDN or punycode while importing this object. 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 _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: _new_address IP address No Add this field to overwrite the address field when you select the overwrite or merge option. comment String No Comment comment disabled Boolean No Disable disable Example: FALSE ttl No TTL ttl This is an inherited field. For information, see Data Specific Guidelines on page 8. Example: 7200 EA-Site String No Extensible attribute Site EA-Users List No Extensible attribute Users ADMGRP-JoeSmith String No Permissions Admin Group/Role extensible_attributes extensible_attributes permission EA-Site is an example of a predefined 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 8. EA-Users is an example of a user defined 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 8. ADMGRP-JoeSmith is an example of an admin permission of a specific admin group. For information about data format and examples, see Data Specific Guidelines on page 8. Examples This section contains examples of how to create data files for A records. All examples use comma as the separator. You can use other supported separators, such as semicolon, space, or tab. 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_Adams = RO. header-arecord,address*,fqdn*,admgrp-dns_admins,ea-site arecord, ,bind_a.corp100.com,ro,infoblox NIOS 6.11 CSV Import Reference (Rev. B) 21

22 CSV Import Reference Overwriting A Record Data This example shows how to to modify the permission of the admin group DNS_Adams from RO to DENY in an existing A record, bind_a.corp100.com. header-arecord,address*,fqdn*,admgrp-dns_admins arecord, ,bind_a.corp100.com,deny Merging DNS Zone Data This example shows how to merge the TTL value = 1280 to an existing A record, bind_a.corp100.com. header-arecord,address*,fqdn*,ttl arecord, ,bind_a.corp100.com,1280 AAAA Record Note: IDN is supported for object type: fqdn. You can use IDN or punycode while importing this object. Header-AaaaRecord String Yes Example: AaaaRecord fqdn FQDN Yes Name zone This field combines the AAAA record name and the zone name to form the FQDN. Example: aaaa1.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. Example: Default address IPv6 address Yes IP Address ipv6addrss Example: 100::10 _new_address IPv6 address No Add this field to overwrite the address field when you select the overwrite or merge option. comment String No Comment comment disabled Boolean No Disable disabled Example: FALSE ttl No TTL ttl This is an inherited field. For information, see Data Specific Guidelines on page 8. Example: 7200 EA-Site String No Extensible attribute Site EA-Users List No Extensible attribute Users ADMGRP-JoeSmith String No Permissions Admin Group/Role extensible_attributes extensible_attributes permission EA-Site is an example of a predefined 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 8. EA-Users is an example of a user defined 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 8. ADMGRP-JoeSmith is an example of an admin permission of a specific admin group. For information about data format and examples, see Data Specific Guidelines on page CSV Import Reference (Rev. B) NIOS 6.11

23 Supported Object Types 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 = 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 header-aaaarecord,address*,_new_address,fqdn*,ttl aaaarecord,1234:1234::1,1234:1234:2,bind_aaaa.corp100.com,3800 Merging AAAA Record Data This example shows how to disable an existing AAAA record. header-aaaarecord,address*,fqdn*,disabled aaaarecord,1234:1234::2,bind_aaaa.corp100.com,true 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 name and the zone name to form the FQDN. Example: c1.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. Example: Default canonical_name Domain name Yes Canonical Name canonical Example: comment String No Comment comment disabled Boolean No Disable disabled Example: FALSE ttl No TTL ttl This is an inherited field. For information, see Data Specific Guidelines on page 8. Example: NIOS 6.11 CSV Import Reference (Rev. B) 23

24 CSV Import Reference EA-Site String No Extensible attribute Site ADMGRP-JoeSmith String No Permissions Admin Group/Role extensible_attributes permission EA-Site is an example of a predefined 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 8. ADMGRP-JoeSmith is an example of an admin permission of a specific admin group. For information about data format and examples, see Data Specific Guidelines on page 8. Examples This section contains examples of how to create data files for CNAME records. All examples use comma as the separator. You can use other supported separators, such as semicolon, space, or tab. 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 cnamerecord,bind_cname.corp100.com,somewhere.corp100.com,default 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* cnamerecord,bind_cname.corp100.com,somewhere2.corp100.com 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 name and the zone name to form the FQDN. Example: d1.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. Example: Default 24 CSV Import Reference (Rev. B) NIOS 6.11

25 Supported Object Types target Domain name Yes Target target Example: d1.foo.com comment String No Comment comment disabled Boolean No Disable disabled Example: FALSE ttl No TTL ttl This is an inherited field. For information, see Data Specific Guidelines on page 8. Example: EA-Site String No Extensible attribute Site ADMGRP-JoeSmith String No Permissions Admin Group/Role extensible_attributes permission EA-Site is an example of a predefined 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 8. ADMGRP-JoeSmith is an example of an admin permission of a specific admin group. For information about data format and examples, see Data Specific Guidelines on page 8. Examples This section contains examples of how to create data files for DNAME records. All examples use comma as the separator. You can use other supported separators, such as semicolon, space, or tab. 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 dnamerecord,bind_dname.corp100.com,bind_dname.corp200.com,true,hq Overwriting DNAME Record Data This example shows how to enable the existing DNAME record, bind_dname.corp100.com, and add admin group DNS_Adams with RO permission. header-dnamerecord,fqdn*,target*,disabled,admgrpdns_admins dnamerecord,bind_dname.corp100.com,bind_dname.corp200.com,false,ro 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 header-dnamerecord,fqdn,target*,comment,ttl dnamerecord,bind_dname.corp100.com,bind_dname.corp200.com,add by DNS admin,3860 NIOS 6.11 CSV Import Reference (Rev. B) 25