Infoblox CSV Import Reference: NIOS 6.5 For Infoblox Core Network Services Appliances

Infoblox CSV Import Reference
NIOS 6.5
for Infoblox Core Network Services Appliances
Copyright Statements
© 2012, 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
Infoblox is located at:
4750 Patrick Henry Drive
Santa Clara, CA 95054-1851, USA
Web: www.infoblox.com
support.infoblox.com
Phone: 408.625.4200 
Toll Free: 888.463.6259 
Outside North America: +1.408.716.4300 
Fax: 408.625.4201
Product Information
Hardware Models: Trinzic 800, 1400, 2200, and 4000 series; Infoblox-250-A, -550-A, -1050-A, -1550-A, -1552-A,
-1852-A, -2000, -2000-A, -4010, and -4030
Document Number: 400-0463-000 Rev. A
Document Updated: July 23, 2012
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.
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.5 CSV Import Reference (Rev. A) 3

Preface
Document Overview
The CSV import reference provides general guidelines and file format information about CSV import. It was last
updated on July 23, 2012. For updated documentation, visit our Support site at
http://www.infoblox.com/en/support/support-center-login.html
Documentation Conventions
The text in this guide follows the following style conventions.
Style Usage
bold Indicates examples of the field names.
data Signifies the data in a CSV file.
Related Documentation
Other Infoblox appliance documentation:
• Infoblox NIOS Administrator Guide
• Infoblox IBOS Administrator Guide
• Infoblox API Documentation
• Infoblox CSV Import Reference
• Infoblox Installation Guide for the Trinzic 800 Appliances
• Infoblox Installation Guide for the Infoblox-4010 Appliance
• Infoblox Installation Guide for the Infoblox-4030 Appliance
• Quick Start Guide for Installing vNIOS Software on Riverbed Services Platforms
• Quick Start Guide for Installing vNIOS Software on Cisco Application eXtension 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
• Infoblox Safety Guide
To provide feedback on any of the Infoblox technical documents, please e-mail techpubs@infoblox.com.
4 CSV Import Reference (Rev. A) NIOS 6.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
http://www.infoblox.com/en/support/product-registration.html to maximize your Technical Support.
Technical Support
Infoblox Technical Support provides assistance via the Web, e-mail, and telephone. The Infoblox Support web site at
http://www.infoblox.com/en/support/support-center-login.html provides access to product documentation and
release notes, but requires the user ID and password you receive when you register your product online at:
http://www.infoblox.com/en/support/product-registration.html.

Preface

Chapter 1 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 9
• Supported Object Types on page 12

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.
• 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
• Field names: Specify the field names in the second line. You can include multiple rows of field names as long as
you define the fields before the data. The first column in the field name row must be defined as “Header.” The
rest of the columns are field names of the data. Columns without a field name are ignored. If multiple field
names are specified, the latest field names are used to import the data.
• Use the overwrite 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.
• 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 “123””123”, the imported data is
123””123, and when you enter “\\”, the imported data is \\.
• If you have an empty value in the last field, you must still include the separator at the end of the data row.
Otherwise, the corresponding column and all its data are not imported, and the appliance generates an error.
• For each supported object type, you must include all the required fields in the data file. For information, see
Supported Object Types on page 12. 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.

CSV File Format
• When you perform an overwrite function, you must define all boolean and integer data types in each supported
object type in order for the appliance to overwrite existing data.
• 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 integer, an email address, a URL, or a date in
YYYY-MM-DD format. Note that extensible attributes do not support time zones. Following are some examples:
• “EA-Site” is a predefined string type for locations. It can have a value of “Santa Clara”.
• “EA-User” is a user defined list type for employee types. It can have a list of values, such as
“Local,Remote,Temp”. Note that only one value can be specified when importing the extensible attribute.
• “EA-Building” is a predefined integer type for building numbers. It can have a value of “5”.
• “EA-TechPubs” is a user defined email address type. It can have a value of “techpubs@infoblox.com”.
• “EA-IB” is a user defined URL type. It can have a value of “www.infoblox.com”.
• “EA-Date” is a user defined date type attribute. It can have a value of “2010-11-20”.
• Admin permissions: A field name of ADMGRP-XXX indicates the admin permission of a specific admin group,
where XXX is the name of the admin group. The value of an admin permission can be a string or a list of strings
with subtypes. If there is a single value in the permission, use RW, RO, or DENY. If there is a subtype in the
permission, use a list format, such as “RW, ARecord/RO”.
• DHCP options: A field name of OPTION-XXX-nn indicates a DHCP option, where XXX is the vendor name of the
option and nn is the option number. If the option is of the DHCP vendor class, you can omit -XXX in the field
name. For example, OPTION-1 implies vendor class = DHCP and option number = 1, and OPTION-CISCO-122
implies vendor class = CISCO and option number = 122.
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 12. 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 10.251.133.128 255.255.255.192 10.251.133.129
4 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0
5 HostRecord TRUE host1.dhcp.corp100.com 172.20.2.21
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 B contains the FQDN of the host, and column C 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 B and the host addresses in column C.
Alternatively, you can organize the information in CSV File Example 1 so that the data rows immediately follow the
header rows, as shown in CSV File Example 2.
A B C D E
2 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129
3 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0
4 HEADER-HostRecord configure_for_dns* FQDN* ADDRESSES

CSV File Format
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.
A B C D E
2 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129
3 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0
4 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Host Range
5 NETWORK 10.176.90.0 255.255.255.128 10.176.90.1 10.176.90.4-126
6 NETWORK 10.176.90.128 255.255.255.128 10.176.90.129 10.176.90.132-254
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 10.
HEADER-NETWORK,ADDRESS*,NETMASK*,EA-Gateway,EA-Secondary Address
NETWORK,10.251.133.128,255.255.255.192,10.251.133.129
NETWORK,10.176.80.255,255.255.252.0,10.176.80.1,172.16.213.0
HEADER-HostRecord,FQDN*,ADDRESSES
HostRecord,host1.dhcp.corp100.com,172.20.2.21
HostRecord,host2.dhcp.corp100.com,172.20.2.22

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 Required Fields & Syntax

Authoritative Zone Authoritative DNS Zone on page 13.
A Record A Record on page 17
AAAA Record AAAA Record on page 18
CNAME Record CNAME Record on page 19
DNAME Record DNAME Record on page 20
MX Record MX Record on page 22
NAPTR Record NAPTR Record on page 23
NS Record NS Record on page 25
PTR Record PTR Record on page 26
SRV Record SRV Record on page 29
TXT Record TXT Record on page 27
Host Record Host Record on page 30
IPv4 Host Address IPv4 Host Address on page 32
IPv6 Host Address IPv6 Host Address on page 34
Rulesets NXDOMAIN and Blacklist Rulesets on page 36
NXDOMAIN Rule NXDOMAIN Rule on page 37
Blacklist Rule Blacklist Rule on page 37
DNS64 Synthesis Group DNS64 Synthesis Group on page 38
Table 1.5 Supported DHCP Object Types
DHCP Object Type Required Fields & Syntax

IPv4 Network IPv4 Network on page 39
IPv6 Network IPv6 Network on page 42
IPv4 Shared Network IPv4 Shared Network on page 44
IPv6 Shared Network IPv6 Shared Network on page 46
IPv4 DHCP Range IPv4 DHCP Range on page 48

DHCP Object Type Required Fields & Syntax

IPv6 DHCP Range IPv6 DHCP Range on page 52
IPv4 Fixed Address and Reservation IPv4 Fixed Address/Reservation on page 53
IPv6 Fixed Address IPv6 Fixed Address on page 56
DHCP MAC Filter DHCP MAC Filter on page 58
MAC Filter Address Item MAC Filter Address on page 59
Option Filter Option Filter on page 61
Option Filter Match Rule Option Filter Match Rule on page 62
Relay Agent Filter Relay Agent Filter on page 64
NAC Filter NAC Filter on page 65
IPv4 Option Space IPv4 Option Space on page 66
IPv6 Option Space IPv6 Option Space on page 67
IPv4 Option Definition IPv4 Option Definition on page 67
IPv6 Option Definition IPv6 Option Definition on page 68
Table 1.6 Other Supported Objects
Upgrades Required Fields and Syntax

Upgrade Groups Upgrade Groups and Schedules on page 69
Distribution Schedules
Upgrade Schedules
Authoritative DNS Zone
Required Associated Associated PAPI

Field Name Data Type (Yes/N0) GUI Field Method Usage and Guidelines
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
grid_primary Grid member No Grid Primary primary
grid_primary_stealth Boolean No Stealth stealth Example: FALSE


Field Name Data Type Usage and Guidelines
(Yes/N0) GUI Field Method
external_primaries Server list No External primary Data must be in the following format:
Primary “name/ip/stealth/use_2x_tsig/
use_tsig/tsig_name/tsig_key/
tsig_key_algorithm”. 
Only name and ip are required fields. If no
value is specified for stealth, use_2x_tsig, and
use_tsig, the default value FALSE is used. If
either use_2x_tsig or use_tsig is TRUE,
tsig_name and tsig_key are required. If no
value is specified for tsig_key_algorithm, the
default value is HMAC-MD5. If both
use_2x_tsig and use_tsig are TRUE, only
use_tsig = TRUE and the tsig key name and key
are imported. 
Example: "ext1.test.com/1.1.1.1/FALSE"
grid_secondaries Member No Grid secondaries Data must be in the following format:

server list Secondary “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"
external_secondaries Server list No External secondaries Data must be in the following format:
Secondary “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/1.1.1.1/FALSE/FALSE/
FALSE/foo/sdfssdf86ew"
ns_group String No Name server ns_group Example: name-ns-group1

group
comment String No Comment comment
disabled Boolean No Disable disable Example: FALSE
create_underscore_ Boolean No Automatically create_underscore_ Example: FALSE

zones create zones
underscore
zones
allow_active_dir List of IP No Allow enable_ad_server The Valid value is a list of IP addresses.

addresses unsigned Example: “1.1.1.1, 10.0.0.1”
updates from
these domain
controllers
soa_refresh Unsigned No Refresh soa_refresh When you modify this field to override an
integer inherited value, you must include values for all
SOA timer fields. The appliance updates all the
SOA timers when you update any of them.


soa_retry Unsigned No Retry soa_retry Ensure that you include this field when you
integer override the soa_refresh field.
soa_expire Unsigned No Expire soa_expire Ensure that you include this field when you
soa_default_ttl Unsigned No Default TTL soa_default_ttl Ensure that you include this field when you
soa_negative_ttl Unsigned No Negative- soa_negative_ttl Ensure that you include this field when you
integer caching TTL override the soa_refresh field.
soa_mname FQDN No SOA MNAME soa_mname Example: infoblox.localdomain

field
soa_email Email No Email address soa_email Example: root@test.com

address for SOA
MNAME field
soa_serial_number Unsigned No Serial Number soa_serial_number

integer
disable_forwarding Boolean No Don’t user disable_forwarding Example: TRUE

forwarders...
allow_update_ Boolean No Allow updates forward_to Example: FALSE

forwarding from
update_forwarding ACL No Allow updates forward_to Data must be in the following formats: 
from... ip address/permission
Permission network/network cidr/permission
table ANY/permission
TSIG-XXX/permission
Permission can be ALLOW or DENY
If the first value is not Any or TSIG-, it is
assumed to be an IP or network address.
Example:
"10.0.0.10/Allow,11.0.0.0/16/Deny,TSIG-foo
/sdfdsfwhsdgfsw8sdf/Allow"
allow_transfer ACL No Allow zone allow_transfer Example: "12.0.0.12/Deny,1234::/64/Allow"

transfers to
allow_update ACL No Allow updates allow_update Example: “13.0.0.0/8/Allow”

from
allow_query ACL No Allow queries allow_query Example: “127.0.0.1/Allow”

from
notify_delay Unsigned No notify_delay This field specifies the seconds of delay the
integer notify messages are sent to the secondaries.
The valid value is between 5 and 86400
seconds.
Example: 10
EA-Site String No Extensible extensible_attributes EA-Site is an example of a predefined

attribute 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 List No Extensible extensible_attributes EA-Users is an example of a user defined

attribute 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 String No Permissions permission ADMGRP-JoeSmith is an example of an admin

Admin permission of a specific admin group. For
Group/Role information about data format and examples,
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
This example shows how to create a data file to add an IPv4 reverse mapping zone, 100.0.0.0/8, with a grid primary
and an external secondary, where the external secondary = name/ip/stealth/use_2x_tsig/use_tsig/
tsig_name/tsig_key.
header-authzone,fqdn*,zone_format*,external_secondaries,grid_primary,
grid_primary_stealth
authzone,100.0.0.0/8,IPV4,ns2.com/2.2.2.2/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/1.1.1.1/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”.
authzone,100.0.0.0/8,IPV4,ns2.com/2.2.2.2/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/2.2.2.2/False/False/False/None/None”.

authzone,100.0.0.0/8,IPV4,ns2.com/2.2.2.2/False/False/False/None/None,ns3.com/2.2.2.2/
False/False/False/None/None,FALSE
A Record
Required Associated GUI

Field Name Data Type Associated PAPI Method Usage and Guidelines
(Yes/No) Field
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 ipv4addr Example: 192.138.1.1
_new_address IP address No Add this field to overwrite the address

field when you select the overwrite or
merge option.
ttl Unsigned No TTL ttl This is an inherited field. For information,

integer see Data Specific Guidelines on page 8.
Example: 7200

attribute Site extensible attribute. You can add other
information about data format and
examples, see Data Specific Guidelines
on page 8.

attribute Users attribute. You can add other user defined
about data format and examples, see
Data Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions permission ADMGRP-JoeSmith is an example of an

Admin admin permission of a specific admin
Group/Role 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.
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,100.0.0.1,bind_a.corp100.com,RO,Infoblox
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,100.0.0.1,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,100.0.0.1,bind_a.corp100.com,1280
AAAA Record

Field Name Data Type (Yes/No) Field Associated PAPI Method Usage and Guidelines
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

option.
used. Example: Default
address IPv6 address Yes IP Address ipv6addr Example: 100::10
_new_address IPv6 address No Add this field to overwrite the address

merge option.
disabled Boolean No Disable disabled Example: FALSE

Example: 7200

on page 8.

attribute Users attribute. You can add other user defined


(Yes/No) Field

Examples
This section contains examples of how to create data files for AAAA records. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an AAAA Record

This example shows how to add an AAAA record, bind_aaaa.corp100.com, with a comment = add by superuser, and
TTL = 3600.
header-aaaarecord,address*,fqdn*,comment,ttl
aaaarecord,1234:1234::1,bind_aaaa.corp100.co,add by superuser,3600
Overwriting AAAA Record Data

This example shows how to modify an existing AAAA record from address 1234:1234::1 to 1234:1234::2, and TTL
from 3600 to 3800.
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
Required Associated GUI Associated PAPI

(Yes/No) Field Method
Header-CnameRecord String Yes Example: CnameRecord
fqdn FQDN Yes Alias zone This field combines the CNAME record
FQDN. Example: c1.corp100.com

option.
canonical_name Domain Yes Canonical Name canonical Example: www.corp100.com

name



Example: 28800

on page 8.

Examples
This section contains examples of how to create data files for CNAME records. All examples use comma as the
Adding a CNAME Record

This example shows how to add a CNAME record, bind_cname.corp100.com, to the Default DNS view.
header-cnamerecord,fqdn*,canonical_name*,view
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

Header-DnameRecord String Yes Example: DnameRecord
fqdn FQDN Yes Alias zone This field combines the DNAME record
FQDN. Example: d1.corp100.com

option.


(Yes/No) Field
target Domain Yes Target target Example: d1.foo.com

name

Example: 28800

on page 8.

Examples
This section contains examples of how to create data files for DNAME records. All examples use comma as the
Adding a DNAME Record

This example shows how to add a DNAME record, bind_dname.corp100.com, with target =
bind_dname.corp200.com, extensible attribute Site = HQ, and disabled = TRUE.
header-dnamerecord,fqdn*,target*,disabled,EA-Site
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 3860.
header-dnamerecord,fqdn,target*,comment,ttl
dnamerecord,bind_dname.corp100.com,bind_dname.corp200.com,Add by DNS admin,3860

MX Record

Header-MxRecord String Yes Example: MxRecord
fqdn FQDN Yes Mail zone This field combines the MX record name
Destination and the zone name to form the FQDN.
Example: MX1.corp100.com

option.
mx Domain Yes Mail Exchange exchanger Example: mailer.foo.com

name
_new_mx Domain No Add this field to overwrite the mx field

name when you select the overwrite or merge
option.
priority Unsigned Yes Preference pref Example: 10

integer
_new_priority Unsigned No Add this field to overwrite the priority

integer field when you select the overwrite or
merge option.

Example: 28800

on page 8.
EA-Users String No Extensible extensible_attributes EA-Users is an example of a user defined

attribute attribute. You can add other user defined
Country attributes to the data file. For information

Examples
This section contains examples of how to create data files for MX records. All examples use comma as the separator.

Adding an MX Record
This example shows how to add an MX record, bind_mx.corp100.com, with a mail exchanger, exchange.corp100.com
and priority = 20.
header-mxrecord,fqdn*,mx*,priority*
mxrecord,bind_mx.corp100.com,exchange.corp100.com,20
Overwriting MX Record Data

This example shows how to overwrite an existing MX record with a new fqdn, bind_mx2.corp100.com, and a new mail
exchanger, new_exchange.corp100.com.
header-mxrecord,fqdn*,_new_fqdn,mx*,_new_mx
mxrecord,bind_mx.corp100.com,bind_mx2.corp100.com,exchange.corp100.com,new_exchange.co
rp100.com
Merging MX Record Data

This example shows how to merge data to the existing MX record, bind_mx2.corp100.com, by adding inherited TTL
value and extensible attributes Site = USA.
header-mxrecord,fqdn*,mx*,priority*,ttl,EA-Site
mxrecord,bind_mx2.corp100.com,new_exchange.corp100.com,20,USA
NAPTR Record

Field Name Data Type (Yes/No) Field Object Usage and Guidelines
Header-NaptrRecord String Yes Example: NaptrRecord
fqdn FQDN Yes Domain name This field combines the domain name and
the zone name to form the FQDN. 
Example: aptr1.corp100.com

option.
order Unsigned integer Yes Order order Example: 10
_new_order Unsigned integer No Add this field to overwrite the order field
option.
preference Unsigned integer Yes Preference preference Example: 20
_new_preference Unsigned integer No Add this field to overwrite the preference

merge option.
flags String Yes Flags flags You can leave this field empty. 
Example: U
_new_flags String No Add this field to overwrite the flags field

option.
services String Yes Service services You can leave this field empty. 
Example: SIP+D2U


(Yes/No) Field Object
_new_services String No Add this field to overwrite the services field

option.
regexp String Yes REGEX regexp You can leave this field empty. 
Example: http://([^/:]+)!\1!i
_new_regexp String No Add this field to overwrite the regexp field

option.
replacement String Yes Replacement replacement Example: corp100.com
_new_replacement String No Add this field to overwrite the replacement

merge option.
ttl Unsigned integer No TTL ttl This is an inherited field. For information,
see Data Specific Guidelines on page 8.
Example: 28800
EA-Site String No Extensible extensible_attrib EA-Site is an example of a predefined

attribute Site utes extensible attribute. You can add other
examples, see Data Specific Guidelines on
page 8.
EA-Users String No Extensible extensible_attrib EA-Users is an example of a user defined

attribute Country utes attribute. You can add other user defined

Examples
This section contains examples of how to create data files for NPATR records. All examples use comma as the
Adding a NAPTR Record

This example shows how to add a NAPTR record, bind_naptr.corp100.com, with order = 10, preference = 20, and
replacement = corp200.com.
header-naptrrecord,fqdn*,order*,preference*,replacement*
naptrrecord,bind_naptr.corp100.com,10,20,corp200.com
Overwriting NAPTR Record Data

This example shows how to overwrite the FQDN of an existing NAPTR record from bind_naptr.corp100.com to
bind_naptr2.corp100.com.
header-naptrrecord,fqdn*,_new_fqdn order*,preference*,replacement*
naptrrecord,bind_naptr.corp100.com,bind_naptr2.corp100.com,10,20,corp200.com

This example shows how to override the preference of an existing NAPTR record from 20 to 25 and replacement from
corp200.com to corp300.com.
header-naptrrecord,fqdn*,order*,preference*,_new_preference,replacement*,_new_replacem
ent
naptrrecord,bind_naptr.corp100.com,10 20 25,corp200.com,corp300.com
Merging NAPTR Record Data

This example shows how to merge Service = http+E2U and TTL = 3600 seconds to an existing NAPTR record.
header-naptrrecord,fqdn*,order*,preference*,replacement*,services,ttl
naptrrecord,bind_naptr.corp100.com,10,25,Corp300.com,http+E2U,3600
NS Record
Required Associated PAPI

Field Name Data Type Associated GUI Field Usage and Guidelines
(Yes/No) Object
Header-NsRecord String Yes Example: NsRecord
fqdn FQDN Yes Zone name This field combines the domain name
and the zone name to form the FQDN.
Example: test.corp100.com
view String No DNS View views If no view is specified, the Default view
is used. Example: Default
dname Domain name Yes Name Server nameserver Example: ns1.corp100.com
_new_dname Domain name No Add this field to overwrite the dname

merge option.
zone_nameservers Server list Yes Name server list addresses Data must be in the following format:
“IPAddress1/auto_create_ptr1,
IPAddress2/auto_create_ptr2”
Example: “10.0.0.4/TRUE,
10.0.0.44/FALSE, 10.0.0.55/TRUE”
Examples
This section contains examples of how to create data files for NS records. All examples use comma as the separator.
Adding an NS Record
This example shows how to add an NS record corp100.com in the Default DNS view with DNAME (name server) =
ns1.corp100.com, name server address = 100.0.0.101, and TRUE for adding a PTR Record.
header-nsrecord,fqdn*,view,dname*,zone_nameservers*
nsrecord,corp100.com,default,ns1.corp100.com,“100.0.0.101/TRUE”
This example shows how to add an NS record corp200.com in the Internal DNS view with DNAME (name server) =
ns1.corp200.com and two name server addresses: 200.0.0.101 with TRUE for adding a PTR Record and 200.0.0.102
with TRUE for adding a PTR record.
header-nsrecord,fqdn*,view,dname*,zone_nameservers*
nsrecord,corp200.com,Internal,ns1.corp200.com,“200.0.0.101/TRUE,200.0.0.102/TRUE”

Overwriting NS Record Data

This example shows how to overwrite the DNAME of an existing NS record from ns1.corp100.com to
ns2.corp100.com.
header-nsrecord,fqdn*,dname*,_new_dname,zone_nameservers*
nsrecord,corp100.com,ns1.corp100.com,ns2.corp100.com,“100.0.0.101/TRUE”
This example shows how to overwrite the zone name servers of an existing NS record to 100.0.0.101/TRUE and
100.0.0.102/TRUE.
header-nsrecord,fqdn*,dname*,zone_nameservers*
nsrecord,corp100.com,ns2.corp100.com,“100.0.0.101/TRUE,100.0.0.102/TRUE”
Merging NS Record Data

This example shows how to merge zone name servers 100.0.0.101/TRUE and 100.0.0.102/TRUE to an NS record.
header-nsrecord,fqdn*,dname*,zone_nameservers*
nsrecord,corp200.com,ns1.corp200.com,“100.0.0.101/TRUE,100.0.0.102/TRUE”
PTR Record
Field Name Data Type Required Associated GUI Field Associated PAPI Usage and Guidelines
(Yes/No) Object
Header-PtrRecord String Yes Example: PtrRecord
fqdn FQDN No Domain Name name This field is required if you do not use
zone the address field. Either the IP address
or FQDN is required. Example:
10.0.0.10.in.addr.arpa
_new_fqdn Reverse FQDN No Add this field to overwrite the fqdn

field when you use the overwrite or
merge option.
view String No DNS View views If no view is specified, the Default view
is used. Example: Default
address IP address No IP Address ipv4addr This field is required if you do not use
ipv6addr the fqdn field. Either the IP address or
FQDN is required. Example: 10.0.0.11
If the PTR record belongs to a
forward-mapping zone, this field is
empty.
_new_address IP address No Add this field to overwrite the address

field when you use the overwrite or
merge option.
dname FQDN Yes Name ptrdname Example: ss.dd.ff
_new_dname FQDN No Add this field to overwrite the dname

merge option.
ttl Unsigned No TTL ttl This is an inherited field.

integer Example: 28800


(Yes/No) Object
EA-Site String No Extensible attribute extensible_attributes EA-Site is an example of a predefined

Site extensible attribute. You can add other
predefined attributes to the data file.
For information about data format and
examples, see Data Specific
ADMGRP-JoeSmith String No Permissions Admin permission ADMGRP-JoeSmith is an example of an

Group/Role admin permission of a specific admin
group. For information about data
format and examples, see Data
Examples
This section contains examples of how to create data files for PTR records. All examples use comma as the separator.
Adding a PTR Record

This example shows how to add a PTR record.
header-ptrrecord,dname*,fqdn
ptrrecord,ptr.corp100.com,1.0.0.100.in-addr.arpa
Overwriting PTR Record Data

This example shows how to overwrite an existing PTR record with a new FQDN, 2.0.0.100.in-addr.arpa.
header-ptrrecord,dname*,fqdn
ptrrecord,ptr.corp100.com,2.0.0.100.in-addr.arpa
This example shows how to overwrite an existing PTR record with a new IP address, 100.0.0.3.
header-ptrrecord,dname*,address
ptrrecord,ptr.corp100.com,100.0.0.3
Merging PTR Record Data

This example shows how to change the DNAME of a PTR record from ptr.corp100.com to ptr2.corp100.com, and to
add comment = East Asia.
header-ptrrecord,dname*,_new_dname,comment
ptrrecord,ptr.corp100.com,ptr2.corp100.com,East Asia
TXT Record

Field Name Data Type (Yes/No) Associated GUI Field Object Usage and Guidelines
Header-TxtRecord String Yes Example: TxtRecord
fqdn FQDN Yes Name name This field combines the record name and
zone the zone name to form the FQDN.
Example: t1.corp100.com

option.


(Yes/No) Object
text String No Text text You can leave this field empty.
_new_txt String No Add this field to overwrite the txt field

option.

Example: 28800
EA-Site String No Extensible attribute extensible_attributes EA-Site is an example of a predefined

on page 8.

group. For information about data format
Examples
This section contains examples of how to create data files for TXT record data import. All examples use comma as the
Adding a TXT Record

This example shows how to add a TXT record, bind_txt.corp100.com, with text = this is a TXT record and TTL set to
3600 seconds.
header-txtrecord,fqdn*,text,ttl
txtrecord,bind_txt.corp100.com,this is a TXT record,3600
Overwriting TXT Record Data

This example shows how to overwrite the text field of a TXT record.
header-txtrecord,fqdn*,text,_new_text
txtrecord,bind_txt.corp100.com,this is a TXT record,this is a new TXT record
Merging TXT Record Data

This example shows how to add comment = USA and disabled = TRUE to an existing TXT record.
header-txtrecord,fqdn*,text,comment,disabled
txtrecord,bind_txt.corp100.com,this is a TXT record,USA,TRUE

SRV Record

Header-SrvRecord String Yes Example: SrvRecord
fqdn FQDN Yes Service name This field combines the service name and the
zone zone name to form the FQDN.
Example: _http._tcp.corp100.com

option.
priority Unsigned Yes Priority priority Example: 10

integer
_new_priority Unsigned No Add this field to overwrite the priority field

integer when you select the overwrite or merge
option.
weight Unsigned Yes Weight weight Example: 20

integer
_new_weight Unsigned No Add this field to overwrite the weight field

integer when you select the overwrite or merge
option.
port Unsigned Yes Port port Example: 80

integer
_new_port Unsigned No Add this field to overwrite the port field when
integer you select the overwrite or merge option.
target Domain name Yes Target target Example: foo.test.com
_new_target Domain name No Add this field to overwrite the target field
option.
ttl Unsigned No TTL ttl This is an inherited field. For information, see
integer Data Specific Guidelines on page 8.
Example: 28800
EA-Site String No Extensible extensible_ EA-Site is an example of a predefined

attribute Site attributes extensible attribute. You can add other
page 8.

Admin admin permission of a specific admin group.
Group/Role For information about data format and
page 8.

Examples
This section contains examples of how to create data files for SRV records. All examples use comma as the separator.
Adding a SRV Record

This example shows how to add a new SRV record.
header-srvrecord,fqdn*,port*,priority*,target*,weight*
srvrecord,bind_srv.corp100.com,80,10,srv.corp100.com,20
Overwriting SRV Record Data

This example shows how to overwrite the following data of a SRV record: port from 80 to 88 and priority from 10 to 20.
header-srvrecord,fqdn*,port*,_new_port,priority*,_new_priority,target*,weight*
srvrecord,bind_srv.corp100.com,80,88,10,20,srv.corp100.com,20
This example shows how to overwrite the following data of a SRV record: target from srv.corp100.com to
srv2corp100.com and weight from 20 to 30.
header-srvrecord,fqdn*,port*,priority*,target*,_new_target,weight*,_new_weight
srvrecord,bind_srv.corp100.com,88,20,srv.corp100.com,sv2.corp100.com,20,30
Merging SRV Record Data

This example shows how to merge the following data to a SRV record: comment = USA and disabled = TRUE.
header-srvrecord,fqdn*,port*,priority*,target*,weight*,comment,disabled
srvrecord,bind_srv.corp100.com,80,10,srv.corp100.com,20,USA,TRUE
Host Record
If only one IPv4 address is specified in the host record, you can add DHCP options to the host address.

Header-HostRecord String Yes Example: HostRecord
fqdn FQDN Yes Name name This field combines the host record name and
zone the zone name to form the FQDN.
Example: h2.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
addresses IP address or IP No IP Addresses ipv4addr You must specify a value in this field or in the
address list ipv6_addresses field. Example: ‘1.2.3.4’ or
“1.2.3.4, 5.6.7.8”. If there are multiple
addresses in the host record, use HostAddress
to specify the parameters for each address. For
information, see IPv4 Host Address on page 32
and IPv6 Host Address on page 34.
ipv6_addresses IP address or IP No IP Addresses ipv6addr You must specify a value in this field or in the
address list addresses field. If there are multiple addresses
in the host record, use HostAddress to specify
the parameters for each address. For
information, see IPv4 Host Address on page 32
and IPv6 Host Address on page 34.
aliases Alias list No Aliases aliases Example: www.infoblox.com


configure_for_dns Boolean No Enable in DNS configure_for_ Example: TRUE

dns
_new_configure_for_ Boolean No Enable in DNS configure_for_ Add this field to overwrite the
dns dns configure_for_dns field when you select the
overwrite or merge option.
ttl Unsigned No TTL ttl This is an inherited field. For information, see
integer Data Specific Guidelines on page 8.
Example: 28800
mac_address MAC address No MAC Address mac_address This field applies to the host address. This is
required if the IP address is configured for DHCP.
Example: aA:Bb:c2:DD:E1:FF
configure_for_dhcp Boolean No DHCP check box configure_for_ This field applies to the host address. 
dhcp Example: TRUE
deny_bootp Boolean No Deny BOOTP deny_bootp This field applies to the host address. 
Requests Example: FALSE
broadcast_address String No Broadcast This field applies to the host address.

Address
boot_file String No Boot File boot_file This field applies to the host address.
boot_server String No Boot Server boot_server This field applies to the host address.
next_server String No Next Server next_server This field applies to the host address.
lease_time Unsigned No Lease Time lease_time This field applies to the host address.
integer
pxe_lease_time_ Boolean No Enable PXE This field applies to the host address.
enabled Lease Time
pxe_lease_time Unsigned No PXE Lease Time pxe_lease_time This field applies to the host address.
integer
domain_name FQDN No Domain Name domain_name This field applies to the host address.
domain_name_ IP list No Name Server This field applies to the host address.
servers Example: “5.6.7.8,1.2.3.4”
routers IP list No Router This field applies to the host address.

Example: “2.0.0.2,1.2.3.4”
match_option String No match_client This field applies to the host address. Data must
be in the following format:
MAC_ADDRESS/RESERVED
ignore_dhcp_param Boolean No Ignore ignore-dhcp_ This field applies to the host address.
_request_list Optionalist option_list_
request
OPTION-1 String No Custom DHCP options This field applies to the host address.
Options Example: ‘255.0.0.0’ name implies
vendor_class=’DHCP’ (default)
OPTION-XXXX-200 Option No Custom DHCP options This field applies to the host address.
information Options Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, optioncode/number 200


EA-Site String No Extensible extensible_ EA-Site is an example of a predefined extensible

attribute Site attributes attribute. You can add other predefined
attributes to the data file. For information about
data format and examples, see Data Specific

Examples
This section contains examples of how to create data files for host records. All examples use comma as the separator.
Adding a Host Record

This example shows how to add a new host record, host1, in zone corp100.com and DNS view Initial.
header-hostrecord,addresses,configure_for_dns*,fqdn*,view
hostrecord,100.0.0.101,TRUE,host1.corp100.com,Inital
This example shows how to add a new host record, host2, in zone corp100.com with aliases = www.corp100.com,
comment = USA, and TTL = 3600 seconds.
header-hostrecord,addresses,configure_for_dns*,fqdn*,aliases,comment,ttl
hostrecord,100.0.0.102,TRUE,host2.corp100.com,www.corp100.com,USA,3600
Overwriting Host Record Data

This example shows how to overwrite the FQDN of an existing host record from host1.corp100.com to
new_host1.corp100.com, and to change the TTL to 128 seconds.
header-hostrecord,addresses,configure_for_dns*,fqdn*,_new_fqdn,ttl
hostrecord,100.0.0.101,TRUE,host1.corp100.com,new_host1.corp100.com,1280
This example shows how to overwrite the aliases of a host record from www.corp100.com to www.corp200.com and
comment from USA to Japan.
header-hostrecord,addresses*,configure_for_dns*,fqdn*,aliases,comment
hostrecord,100.0.0.102,TRUE,host2.corp100.com,www.corp200.com,Japan
Merging Host Record Data

This example shows how to disable an existing host record.
header-hostrecord,configure_for_dns*,addresses*,fqdn*,disabled
hostrecord,100.0.0.101,TRUE,new_host1.corp100.com,TRUE
This example shows how to add additional aliases to a host record.
header-hostrecord,configure_for_dns*,addresses*,fqdn*,aliases
hostrecord,100.0.0.102,TRUE,host2.corp100.com,”www.corp200.com,http.corp200.com”
IPv4 Host Address

Use this object type to define parameters for each IP address in an IPv4 host record. The appliance updates an
existing host address when you use the “add” mode in an import. For information about host records, refer to the
Infoblox Administrator Guide.

Field Name Data Type Required Associated GUI Associated PAPI Usage and Guidelines
Header-HostAddress String Yes Example: HostAddress
parent FQDN Yes Example: h1.corp100.com
view String No DNS View views If no view is specified, the Default view is used.
Example: Default
address IP address Yes IP Address ipv4addr Example: 10.0.0.11
_new_address IP address No Add this field to overwrite the address field

when you select the overwrite or merge option.
mac_address MAC address No MAC Address mac_address This is required if the IP address is configured
for DHCP. Example: aA:Bb:c2:DD:E1:FF
configure_for_dhcp Boolean No DHCP check box configure_for_ Example: TRUE

dhcp
deny_bootp Boolean No Deny BOOTP deny_bootp Example: FALSE

Requests
broadcast_address String No Broadcast

Address
boot_file String No Boot File boot_file
boot_server String No Boot Server boot_server
next_server String No Next Server next_server
lease_time Unsigned No Lease Time lease_time

integer
pxe_lease_time_ Boolean No Enable PXE Lease Example: TRUE

enabled Time
pxe_lease_time Unsigned No PXE Lease Time pxe_lease_time

integer
domain_name FQDN No Domain Name domain_name
domain_name_ IP list No Name Server Example: [5.6.7.8,1.2.3.4]

servers
routers IP list No Router Example: [2.0.0.2,1.2.3.4]
match_option String No match_client Data must be in the following format:

MAC_ADDRESS/CLIENT_IDENTIFIER/RESERVED
ignore_dhcp_param_ Boolean No Ignore Optionlist ignore-dhcp_

request_list option_list_
request
OPTION-1 String No Custom DHCP options This is an example of a DHCP option. For
Options information, see Data Specific Guidelines on
page 8.
Example: ‘255.0.0.0’ implies
OPTION-XXXX-200 Option No Custom DHCP options This is an example of a DHCP option. For
information Options information, see Data Specific Guidelines on
page 8.
Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, optioncode/number 200

Examples
This section contains examples of how to create data files for host addresses. All examples use comma as the
Adding an IPv4 Host Address

This example shows how to import the host address 100.0.0.1 in host record h1.corp100.com with a MAC address,
enabled DHCP, and a domain name.
header-hostaddress,parent*,address*,mac_address,configure_for_dhcp,domain_name
hostaddres,h1.corp100.com,100.0.0.1,aa:aa:aa:aa:aa:aa,TRUE,corp200.com
This example shows how to import the host address 100.0.0.2 in host record h2.corp100.com with a MAC address,
and two routers with addresses 1.1.1.1 and 2.2.2.2.
header-hostaddress,parent*,address*,mac_address,configure_for_dhcp,routers
hostaddress,h2.corp100.com,100.0.0.2,bb:aa:aa:aa:aa:aa,False,1.1.1.1,2.2.2.2
Overwriting IPv4 Host Address Data

This example shows how to overwrite the MAC address and domain name of a host address, and to set configure
DHCP to TRUE.
header-hostaddress,parent*,address*,mac_address,configure_for_dhcp,domain_name
hostaddress,h1.corp100.com,100.0.0.1,cc:aa:aa:aa:aa:aa,FALSE,corp300.com
This example shows how to overwrite the router address of a host address from 1.1.1.1,2.2.2.2 to 1.1.1.1.
header-hostaddress,parent*,address*,routers
hostaddress,h2.corp100.com,100.0.0.2,1.1.1.1
Merging IPv4 Host Address Data

This example shows how to merge the following data of a host address: change a new address from 100.0.0.1 to
100.0.0.10, change bootp to DENY, and add lease time.
header-hostaddress,parent*,address*,_new_address,deny_bootp,lease_time
hostaddress,h1.corp100.com,100.0.0.1,100.0.10,FALSE,3600
This example shows how to merge the broadcast address, PXE lease time, and enabled ignore option list to an IPv4
host address.
header-hostaddress,parent*,address*,broadcast_address,pxe_lease_time,ignore_dhcp_param
_request_list
hostaddress,h2.corp100.com,100.0.0.2,6.6.6.6,1280,TRUE
IPv6 Host Address
Required Associated GUI Associated

Field Name Data Type (Yes/No) Field PAPI Method Usage and Guidelines
Header-IPv6HostAddress String Yes Example: IPv6hostaddress
view String No DNS View view If no view is specified, the Default view is
parent String Yes Example: 2000::/64
address_type Enumeration No address_type Valid values are ADDRESS, PREFIX, or BOTH. If

no value is specified, ‘ADDRESS’ (default) is
used. Example: PREFIX
address IPv6 address Yes IPv6 Address ipv6addr Example: 1001::001


(Yes/No) Field PAPI Method
_new_address IPv6 address No Add this field to overwrite the address field
option.
ipv6_prefix IPv6 prefix No ipv6prefix This field is required if address_type is

‘ADDRESS’ or ‘BOTH’.
Example: 2000:1111::
_new_ipv6_prefix IPv6 prefix No Add this field to overwrite the ipv6_prefix field
option.
ipv6_prefix_bits Integer No IPv6_prefix_ This field is required if address_type is

bits ‘ADDRESS’ or ‘BOTH’.
Example: 32
configure_for_dhcp Boolean No DHCP check box configure_for_ Example: TRUE

dhcp
match_option String No match_client Only ‘DUID’ is allowed.

Example: DUID
duid String No DUID duid Example: 0001
domain_name FQDN No Domain Name
domain_name_servers IPv6 address No Name Server Example: ‘2000::10,3000::10’

list
valid_lifetime Unsigned No Valid Lifetime valid_lifetime Example: 43200

integer
preferred_lifetime Unsigned No Preferred preferred_ Example: 604800

integer Lifetime lifetime
OPTION-7 Integer No Custom DHCP override_ This is an example of a DHCP option. For
Options options information, see Data Specific Guidelines on
page 8.
Example: ‘12’ name implies option space =
‘DHCPv6’, option code/number 7
OPTION-XXXX-200 Option No Custom DHCP override_ This is an example of a DHCP option. For
information Options options information, see Data Specific Guidelines on
page 8.
vendor_class=’XXXX’, option
code/number 200
Examples
This section contains examples of how to create data files for IPv6 host addresses. All examples use comma as the
Adding an IPv6 Host Address

This example shows how to import an IPv6 host address to a host record in the Default DNS view.
header-IPv6hostaddress,parent*,address*,view
IPv6hostaddress,h1.corp100.com,1001::001,Default
Overwriting IPv6 Host Address Data

This example shows how to overwrite an IPv6 host address.
header-IPv6hostaddress,parent*,address*,_new_address
IPv6hostaddress,h1.corp100.com,1001::001,2000::10

Merging IPv6 Host Address Data

This example shows how to merge a DUID to an IPv6 host address.
header-IPv6hostaddress,parent*,address*,duid
IPv6hostaddress,h1.corp100.com,2000::10,0001
NXDOMAIN and Blacklist Rulesets

Field Name Data Type (Yes/No) Field PAPI Method Usage and Guidelines
Header-Ruleset String Yes Example: Ruleset
name String Yes Name name Example: ruleset1
_new_name String No Example: ruleset1-new
type String Yes type You can use this field for NXDOMAIN rules or
blacklist rules. Valid value is NXDOMAIN or
BLACKLIST.
Example: NXDOMAIN

Examples
This section contains examples of how to create data files for NXDOMAIN and blacklist rulesets. All examples use
comma as the separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an NXDOMAIN Ruleset

This example shows how to import an NXDOMAIN ruleset.
header-Ruleset,name*,type*,comment,disabled
ruleset,NXD,NXDOMAIN,This is an NXDOMAIN ruleset,FALSE
Adding a Blacklist Ruleset

This example shows how to import a blacklist ruleset.
header-Ruleset,name*,type*,disabled,comment
ruleset,blacklistrule1,BLACKLIST,FALSE,This is a blackset ruleset
Overwriting Blacklist Ruleset Data

This example shows how to overwrite the name of a blacklist ruleset.
header-Ruleset,name*,_new_name,type*
ruleSet,blacklistrule1,blacklistrule2,BLACKLIST
Merging NXDOMAIN Ruleset Data

This example shows how to merge an admin permission to a NXDOMAIN ruleset.
header-Ruleset,name*,type*,ADMGRP-JoeSmith
ruleSet,NXD,NXDOMAIN,RW

NXDOMAIN Rule

Field Name Data Type (Yes/No) Field Method Usage and Guidelines
Header-nxdomainrule String Yes Example: NxdomainRule
parent String Yes Name nxdomain_rules This field indicates the ruleset to which the
NXDOMAIN rule belongs. Example:
nxdomain-ruleset1
pattern String Yes Pattern pattern Use this to match domain names. You cannot
use the characters * and ,, in the domain
name. Example: foo
_new_pattern String No Example: foo-new
action String Yes Action action The valid value is PASS, MODIFY or REDIRECT.
Example: PASS
Examples
This section contains examples of how to create data files for NXDOMAIN rules. All examples use comma as the
Adding an NXDOMAIN Rule

This example shows how to import an NXDOMAIN rule.
header-nxdomainrule,action*,parent*,pattern*
nxdomainrule,REDIRECT,NXD,*foo.com
Overwriting NXDOMAIN Rule Data

This example shows how to overwrite the action of an NXDOMAIN rule.
header-nxdomainrule,action*,parent*,pattern*
nxdomainRule,REDIRCT,NXD,*bar.com
Blacklist Rule

Header-blacklistrule String Yes Example: BlacklistRule
parent String Yes Name blacklist_rulesets Example: blacklist-ruleset1
domain_name String Yes Domain Name Use this to match domain names. You
cannot use the characters * and ,, in the
domain name. The domain name cannot
exceed 255 characters. Example:
www.foo.com
_new_domain_name String No Example: www.bar.com
action String Yes Action blacklist_action The valid value is PASS or REDIRECT.
Example: PASS

Examples
This section contains examples of how to create data files for blacklist rules. All examples use comma as the
Adding a Blacklist Rule

This example shows how to import a blacklist rule.
header-blacklistrule,parent*,domain_name*,action*
BlacklistRule,BlackList,foobar.com,REDIRECT
Overwriting Blacklist Rule Data

This example shows how to overwrite the action of a blacklist rule.
header-blacklistrule,parent*,domain_name*,action*
BlacklistRule,BlackList,foobar.com,PASS
DNS64 Synthesis Group
Header-Dns64Synthesis String Yes Example: Dns64SynthesisGroup

Group
name String Yes Name name Example: group1
prefix IPv6 network Yes Prefix prefix Example: 64:FF9B::/96
clients Access No Name clients Valid values are IPv4 and IPv6 addresses and
control list networks only. The default value is ‘Any’.
Example: 2000::/64/Allow
mapped Access No Mapped IPv4 mapped Valid values are IPv4 addresses and networks
control list Address -> only. The default value is ‘Any’.
Name Example: 10.0.0.0/8/Allow
exclude Access No Excluded IPv6 exclude Valid values are IPv6 addresses and networks
control list Address -> only. The default is ‘None’. 
Name Example: 2000::/Allow
disabled Boolean No Disabled disable Example: FALSE
Examples
This section contains examples of how to create data files for DNS64 synthesis groups. All examples use comma as
the separator. You can use other supported separators, such as semicolon, space, or tab.
Adding a DNS64 Synthesis Group

This example shows how to import a DNS64 Synthesis Group.
header-Dns64SynthesisGroup,name*,prefix*,mapped
Dns64SynthesisGroup,DNS64Group1,64:FF9B::/96,10.0.0.0/8/Allow
Overwriting DNS64 Synthesis Group Data
This example shows how to overwrite the mapped IPv4 address of a DNS64 synthesis group.
header-Dns64SynthesisGroup,name*,prefix*,mapped
Dns64SynthesisGroup,DNS64Group1,64:FF9B::/96,10.1.1.0/24/Allow

IPv4 Network
Field Name Data Type Required Associated GUI Associated PAPI Usage and Comments
Header-Network String Yes Example: Network
address IP address Yes Address network Example: 10.0.0.11
netmask Netmask Yes Netmask network Example: 255.255.0.0
network_view String No Network View network_view If no view is specified, the Default view is
auto_create_ Boolean No Automatically auto_create_ Example: TRUE

reversezone create reverse reversezone
mapping zone
is_authoritative Boolean No Authoritative authority Example: FALSE
boot_file String No Boot File bootfile Example: bootfile1
boot_server String No Boot Server bootserver Example: abc.corp100.com
ddns_ String No DDNS Domain ddns_ Example: ddns.corp100.com

domainname Name domainname
generate_ Boolean No Generate Hostname ddns_generate_ Example: TRUE

hostname hostname
always_update_ Boolean No DNS Zones ddns_server_ Example: FALSE

dns Associations always_updates
update_static_ Boolean No Fixed Address ddns_update_fixed_ Example: FALSE

leases Updates address
update_dns_on_ Boolean No Update DNS on override_update_ Example: TRUE

lease_renewal DHCP Lease dns_on_lease_
Renewal renewal
ddns_ttl Unsigned No DDNS Update TTL ddns_ttl This is an inherited field. For information,
Example: 1200
enable_option81 Boolean No Option 81 Support ddns_use_option81 Example: TRUE

Requests
broadcast_ String No Broadcast Address

address
enable_ddns Boolean No Enable DDNS enable_ddns Example: FALSE

Updates
enable_thresholds Boolean No Enable DHCP enable_dhcp_ When you set this field to TRUE, you must
Thresholds thresholds enter values in the
range_high_water_mark and
range_low_water_mark fields. You cannot
leave those fields empty. Otherwise, the
appliance generates an error.


Field Name Data Type Usage and Comments
enable_threshold_ Boolean No Enable Email enable_email_ When you use the merge function, the
email_ warnings Warnings warnings appliance preserves the existing value in
this field. When you use the overwrite
function, you must include a value (TURE
or FALSE). Otherwise, the appliance
generates an error.
Example: TRUE
enable_threshold_ Boolean No Enable SNMP enable_snmp_ When you use the merge function, the
snmp_ warnings Warnings warnings appliance preserves the existing value in
Example: TRUE
range_high_water Integer No High Water Mark high_water_mark When you set enable_thresholds to TRUE,
_mark you must enter values in this field and in
the range_low_water_mark field. You
cannot leave these fields empty.
Otherwise, the appliance generates an
error.
Example: 80
ignore_client_ Boolean No Ignore Optionlist ignore_dhcp_ Example: TRUE

requested_ option_list_request
options
range_low_water_ Integer No Low Water Mark low_water_mark When you set enable_thresholds to TRUE,
mark you must enter values in this field and in
the range_high_water_mark field. You
error.
Example: 10
next_server String No Next Server nextserver Example: blue.domain.com
lease_time Unsigned No Lease Time Example: 1100

integer
enable_pxe_lease Boolean No Enable PXE lease Example: FALSE

_time time
pxe_lease_time Unsigned No PXE Lease Time pxe_lease_time Example: 1100

integer
recycle_leases Boolean No Lease Deletion recycle_leases This field is set to TRUE by default. Ensure
that you use the overwrite option if you
want to change the value to FALSE.
Merging data from an import preserves the
default value.
threshold_email_ email No Email Addresses Example:

addresses address list "'admin1@infoblox.com','admin2@somewh
ere.com'"
dhcp_members Grid member No Members members Example:

list "host1.infoblox.com,host2.infoblox.com"
routers IP address No Routers Example: "10.0.0.1,10.0.0.100,"

list
domain_name_ IP address No DNS Servers Example: "10.2.3.4,11.2.3.4"

servers list


Field Name Data Type Usage and Comments
zone_associations Zone list No Example: test.com/TRUE
Options information, see Data Specific Guidelines
on page 8. 
Example: ‘255.0.0.0’ name implies
information Options information, see Data Specific Guidelines
on page 8.
code/number 200
EA-Site String No Extensible Attribute extensible_attributes EA-Site is an example of a predefined

on page 8.
EA-Users String No Extensible Attribute extensible_attributes EA-Users is an example of a user defined

User attribute. You can add other user defined

Examples
This section contains examples of how to create data files for networks. All examples use comma as the separator.
Adding an IPv4 Network

This example shows how to import network 100.0.0.0/24 in the network view External with auto create reverse zone
enabled and a comment.
header-network,address*,netmask*,network_view,auto_create_reversezone,comment
network,100.0.0.0,255.255.255.0,External,TRUE,This is comment field
Overwriting IPv4 Network Data

This example shows how to overwrite the following data in an existing network: enable the network to be
“authoritative” and to add boot files bppt_file_001 and boot server 1.2.3.4.
header-network,address*,netmask*,is_authoritative,boot_file,boot_server
network,100.0.0.0,255.255.255.0,True,boot_file_001,1.2.3.4
Merging IPv4 Network Data

This example shows how to merge the following data to an existing network: DDNS domain name, enable generate
hostname, and disable always update DNS.
header-network,address*,netmask*,ddns_domainname,generate_hostname,always_update_dns
network,100.0.0.0,255.255.255.0,ddns.corp100.com,TRUE,FALSE

Adding IPv4 Networks with Zone Associations Enabled

This example shows how to add networks to a member in the default network view with zone association added as
the default. The first row adds a network “20.0.1.0/24” that maps to member “ib-10-34-43-2.infoblox.com” in the
“default” network view with zone association “dnszone1.com” added as the default zone association. The second
row adds a network “20.0.2.0/24” that maps to member “ib-10-34-43-2.infoblox.com” in the “default” network view
with zone associations “dnszone1.com” and “dnszone2.com” added, where zone “dnszone2.com” is configured as
the default zone association.
network,address*,netmask*,dhcp_members,network_view,zone_associations
network,20.0.1.0,255.255.255.0,ib-10-34-43-2.infoblox.com,default,dnszone1.com/True/default
network,20.0.2.0,255.255.255.0,ib-10-34-43-2.infoblox.com,default,dnszone1.com/False/default,
dnszone2.com/True/default
Overwriting IPv4 Network Data with Zone Associations Enabled

This example shows how to overwrite network data with zone association enabled. The first row modifies network
“20.0.1.0/24” zone association from “dnszone1.com” to “dnszone2.com”. The second row modifies network
“20.0.2.0/24” default zone association from “dnszone2.com” to “dnszone1.com”.
header-network,address*,netmask*,dhcp_members,network_view,zone_associations
network,20.0.1.0,255.255.255.0,ib-10-34-43-2.infoblox.com,default,dnszone2.com/True/default
network,20.0.2.0,255.255.255.0,ib-10-34-43-2.infoblox.com,default,dnszone1.com/True/default,
dnszone2.com/False/default
IPv6 Network

Header-IPv6Network String Yes Example: IPv6Network
address IPv6 address Yes Address ipv6addr Example: 2001::
cidr Prefix Yes Netmask Example: 32
network_view String No Network View network_view If no view is specified, the Default

view is used. 
Example: Default
comment String No Comment comment Example: This is an IPv6 network.
disabled Boolean No Disabled disable Example: TRUE
auto_create_reversezone Boolean No Automatically auto_create_ Example: TRUE

create reversezone
reverse-mapping
zone
zone_associations Zone list No DNS Zone zone_ Example: test.com/TRUE

Associations associations
dhcp_members Grid member No Members members Example: “host1.infoblox.com,

list host2.infoblox.com
domain_name String No Domain Name Example: testdomain.com
domain_name_servers IP address list No Name Server Example: ‘2000::10,3000::10’
valid_lifetime Integer No Valid Lifetime valid_lifetime Example: 43200
Preferred_lifetime Integer No Preferred preferred_ Example: 604800

Lifetime lifetime
recycle_leases Boolean No recycle_leases Example: FALSE


enable_ddns Boolean No Enable DDNS enable_ddns Example: TRUE

Updates
always_update_dns Boolean No FQDN Support ddns_server_ Example: TRUE

always_updates
ddns_domain_name String No DDNS Domain ddns_ Example: ddnsdomain.com

Name domainname
ddns_ttl Unsigned No DDNS Update ddns_ttl Example: 3600

integer TTL
generate_hostname Boolean No Generate override_ddns_ Example: TRUE

Hostname generate_
hostname
update_dns_on_lease_renewal Boolean No Lease Renewal override_ Example: TRUE

Update update_dns_
on_lease_
renewal
OPTION-7 Integer No Custom DHCP override_ This is an example of a DHCP option.

Options options For information, see Data Specific
Guidelines on page 8.
Example: ‘12’ name implies option
space = ‘DHCPv6’, option
code/number 7
OPTION-XXXX-200 Option No Custom DHCP override_ This is an example of a DHCP option.

information Options options For information, see Data Specific
code/number 200
EA-Site String No Extensible extensible_ EA-Site is an example of a

attribute Site attributes 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 String No Extensible extensible_ EA-Users is an example of a user

attribute Users attributes defined attribute. You can add other
user defined attributes to the data
file. For information about data
ADMGRP-JoeSmith String No Permissions permission ADMGRP-JoeSmith is an example of

Admin an admin permission of a specific
Group/Role admin group. For information about
data format and examples, see Data

Examples
This section contains examples of how to create data files for IPv6 networks. All examples use comma as the
Adding an IPv6 Network

This example shows how to import an IPv6 network 3333::/64 in the Default DHCP view.
header-IPv6network,address*,cidr*,network_view,comment,auto_create_reversezone
IPv6network,3333::,64,Default,This is a comment,TRUE
Overwriting IPv6 Network Data

This example shows how to overwrite the following data of an IPv6 network: address and cidr.
header-IPv6network,address*,_new_address,cidr*,_new_cidr
IPv6network,3333::,2222::,64,32
Merging IPv6 Network Data

This example shows how to merge the extensible attribute State and admin group USA_admins to an IPv6 network.
header-IPv6network.address*,cidr*,EA-State,ADMGRP-USA_admins
IPv6network,3333::,64,CA,RW
IPv4 Shared Network
Header-SharedNetwork String Yes Example: SharedNetwork
name String Yes Name name Example: Site Network
_new_name String No Add this field to overwrite the name field

option.
networks List Yes Example: “10.1.1.0/24,10.1.2.0/24,”
generate_hostname Boolean No Generate ddns_generate_ Example: TRUE

Hostname hostname
always_update_dns Boolean No DNS Zones ddns_server_ Example: FALSE

Associations always_updates
update_static_leases Boolean No Fixed Address ddns_update_ Example: FALSE

Updates fixed_address

Renewal renewal
ddns_ttl Integer No DDNS Update TTL ddns_ttl This is an inherited field.

Example: 1200


enable_option81 Boolean No Option 81 ddns_use_option Example: TRUE

Support 81

Requests

Updates

requested_ options option_list_reque
st

integer
enable_pxe_lease_ Boolean No Enable PXE lease Example: FALSE

time time

integer
routers IP address No Routers Example: "10.0.0.1,10.0.0.100"

list
domain_name_servers IP address No Name Server Example: "10.2.3.4,11.2.3.4"

list
OPTION-2 Integer No Custom DHCP options Example: 50

Options
on page 8.
OPTION-XXXX-200 Option No Extensible options This is an example of a DHCP option. For

information Attribute Site information, see Data Specific Guidelines
on page 8.
code/number 200
EA-Site String No Extensible extensible EA-Site is an example of a predefined

Attribute Users attributes extensible attribute. You can add other
page 8.
EA-Users String No Permissions extensible EA-Users is an example of a user defined

Admin attributes attribute. You can add other user defined
Group/Role attributes to the data file. For information



Examples
This section contains examples of how to create data files for shared networks. All examples use comma as the
Adding an IPv4 Shared Network

This example shows how to import a new shared Network in the Default DHCP view.
header-SharedNetwork,name*,networks*,network_view,comment,OPTION-2
SharedNetwork,Sharednetwork01,”10.0.0.0/24,20.0.0.0/24”,Default,This is a comment.,128
Overwriting IPv4 Shared Network Data

This example shows how to overwrite a shared network with additional networks.
header-SharedNetwork,name*,networks*
SharedNetwork,Sharednetwork01,”10.0.0.0/24,20.0.0.0/24,30.0.0.0/24”
Merging IPv4 Shared Network Data

This example shows how to merge the extensible attribute Site and a new admin group DHCP_admins with RW
permission to an IPv4 shared network.
header-SharedNetwork,name*,networks*,EA-Site,ADMGRP-DHCP_admins
SharedNetwork,Sharednetwork01,”10.0.0.0/24,20.0.0.0/24”,USA,RW
IPv6 Shared Network
Note: This object is supported in CSV export only.
Header-IPv6SharedNet String Yes Example: IPv6SharedNetwork

work
name String Yes Name name Example: IPv6Shared01

option.
networks List Yes Select Network networks Example: “2000::/64,3000::/64”
domain_name String No Domain Name Example: testdomain.com


domain_name_servers IP address No Name Server Example: “2000::10,3000::10”

list
valid_lifetime Integer No Valid Lifetime valid_lifetime Example: 43200
Preferred_lifetime Integer No Preferred Lifetime preferred_ Example: 604800

lifetime
enable_ddns Boolean No Enable DDNS enable_ddns Example: TRUE

Updates
always_update_dns Boolean No DNS Zones ddns_server_ Example: TRUE

Associations always_updates
ddns_domain_name String No DDNS Domain ddns_ Example: DDNSdomain

Name domainname
ddns_ttl Integer No DDNS Update TTL override_ddns_ttl This is an inherited field.

Example: 1200
generate_hostname Boolean No Generate override_ddns_ Example: TRUE

Hostname generate_
hostname

Renewal renewal
Options options information, see Data Specific Guidelines
on page 8.
Example: ‘12’ name implies option space =
‘DHCPv6’, option code/number 7
information Options options information, see Data Specific Guidelines
on page 8.
code/number 200

attribute Site attributes extensible attribute. You can add other
page 8.
EA-Users String No Extensible extensible_ EA-Users is an example of a user defined

attribute Users attributes attribute. You can add other user defined


IPv4 DHCP Range

Header-DhcpRange String Yes Example: DhcpRange
start_address IP address Yes Start start_addr Example: 10.0.0.11
_new_start_address IP address No Add this field to overwrite the

start_address field when you select the
Example: 10.0.0.55
end_address IP address Yes End end_addr Example: 10.0.0.22
_new_end_address IP address No Add this field to overwrite the

end_address field when you select the
Example: 10.0.0.66
name String No Name name
ddns_domainname String No DDNS Domain ddns_domainname Example: ddns.corp100.com

Name
generate_hostname Boolean No Generate ddns_generate_ Example: TRUE

Hostname hostname
deny_all_clients Boolean No deny_all_clients Example: FALSE

Requests
domain_name_servers IP address list No Name Servers Example: "10.2.3.4,11.2.3.4,"

Updates
enable_thresholds Boolean No Enable DHCP enable_dhcp_ When you set this field to TRUE, you must
Thresholds thresholds enter values in the
range_high_water_mark and
range_low_water_mark fields. You
cannot leave those fields empty.
error.
enable_threshold_ Boolean No Enable Email enable_email_ When you use the merge function, the
email_ warnings Warnings warnings appliance preserves the existing value in
Example: TRUE


enable_threshold_ Boolean No Enable SNMP enable_snmp_ When you use the merge function, the
snmp_ warnings Warnings warnings appliance preserves the existing value in
Example: TRUE
threshold_email_ email address No Email Addresses Example:

addresses list "'admin1@infoblox.com','admin2@somew
here.com'"
range_high_water_ Integer No High Water Mark high_water_mark When you set enable_thresholds to TRUE,
mark you must enter values in this field and in
the range_low_water_mark field. You
error.
Example: 80

requested_ options option_list_reques
t
range_low_water_mark Integer No Low Water Mark low_water_mark When you set enable_thresholds to TRUE,
you must enter values in this field and in
the range_high_water_mark field. You
error.
Example: 10

integer

time time

integer
use_unknown_clients Boolean No Allow/Deny unknown_client_ Example: FALSE

Clients: Unknown option
Clients
unknown_clients_ String No Unknown Clients unknown_client_ Example: Allow

option drop-down option
use_known_clients Boolean No Allow/Deny known_clients_ Example: TRUE

Clients: Known option
Clients
known_clients_option String No Known Clients known_clients_ Example: Deny

drop-down option
Merging data from an import preserves
the default value.



Renewal renewal
always_update_dns Boolean No DNS Zones always_update_ Example: FALSE

Associations dns
exclusion_ranges IP address No Exclusion Ranges exclude This field indicates the start to end
range address range. You can also include a
comment. The valid format is start
address-end address/comment.
Example: “10.1.0.200-10.1.0.254/’The
range for printers’,10.2.3.3-10.2.3.30/”
member Grid member No Served by Grid member Example: member.infoblox.com

Member
server_association_ Sting No Valid values are MEMBER, NONE, and

type FAILOVER
failover_association String No Served by failover_assoc

Failover
Association
broadcast_address IP address No Broadcast Example: 10.0.0.1

Address
routers IP address list No Routers Example: "10.0.0.1,10.0.0.100,"
mac_filter_rules List of MAC No Filter Type/Action Example: "MACfiltername1/allow,

filter rules MACfiltername2/deny"
nac_filter_rules List of NAC No Filter Type/Action Example: "NACfiltername1/allow,

Filter rules NACfiltername2/deny"
relay_agent_filter_rules List of relay Filter Type/Action Example: "RAfiltername1/allow,

agent filter RAfiltername2/deny"
rules
option_filter_rules List of option Filter Type/Action Example: "Optionfiltername1/allow,

filter rules Optionfiltername2/deny"
OPTION-2 Integer No Custom DHCP options This is an example of a DHCP option. For
on page 8.
Example: 50
on page 8.
information Options information, see Data Specific Guidelines
on page 8.
code/number 200



Attribute Site attributes extensible attribute. You can add other
on page 8.
EA-Users String No Extensible extensible EA-Users is an example of a user defined

Attribute Users attributes attribute. You can add other user defined

Examples
This section contains examples of how to create data files for DHCP ranges. All examples use comma as the separator.
Adding a DHCP Range

This example shows how to import a new DHCP range, Range01, with starting IP of 100.0.0.1 and ending IP
100.0.0.254. The range is assigned to a member, master.corp100.com.
header-DhcpRange,start_address*,end_address*,name,comment,member
DhcpRange,100.0.0.1,100.0.0.254,Range01,This is a comment.,master.corp100.com
Overwriting DHCP Range Data

This example shows how to overwrite the starting address and the name of an existing DHCP range,.
header-DhcpRange,start_address*,_new_start_address,end_address*,name
DhcpRange,100.0.0.100,100.0.0.150,100.0.0.254,Range02
Merging DHCP Range Data

This example shows how to merge an exclusion range 100.0.0.100 to 100.0.0.110 to an existing DHCP range, and to
replace a member assignment with a failover association, Failover01.
header-DhcpRange,start_address*,end_address*,exclusion_ranges,failover_association
DhcpRange,100.0.0.100,100.0.0.254,100.0.0.100-100.0.0.110,Fileaover01

IPv6 DHCP Range
Header-IPv6DhcpRange String Yes Example: IPv6DhcpRange
address_type Enumeration No address_type Valid values are ADDRESS, PREFIX, and

BOTH. If no value is specified, ‘ADDRESS’
(default) is used.
Example: PREFIX
parent String No Select Network network This field is required when address_type
is ‘PREFIX’.
Example: 2000::/16
start_address IP address No Address Start start_addr This field is required if address_type is

Example: 2000::1
_new_start_address IP address No Add this field to overwrite the

start_address field when you select the
end_address IP address No Address End end_addr This field is required if address_type is

Example: 2000::1
_new_end_address IP address No Add this field to overwrite the

end_address field when you select the
ipv6_start_prefix IPv6 address No Prefix Delegated ipv6_start_prefix This field is required if address_type is
prefix Start ‘PREFIX’ or ‘BOTH’.
Example: 2000:1111::
_new_ipv6_start_prefix IPv6 address No Add this field to overwrite the

prefix ipv6_start_address field when you select
the overwrite or merge option.
ipv6_end_prefix IPv6 address No Prefix Delegated ipv6_end_prefix This field is required if address_type is
prefix End ‘PREFIX’ or ‘BOTH’.
Example: 2000:1111::
_new_ipv6_end_prefix IPv6 address No Add this field to overwrite the

prefix ipv6_end_address field when you select
ipb6_prefix_bits Integer No ipv6_prefix_bits This field is required if address_type is

‘PREFIX’ or ‘BOTH’.
Example: 32
comment String No Comment comment Example: This is an IPv6 DHCP range.
member Grid member No Grid Member member Example: member.infoblox.com
server_association_ Sting No server_association Valid values are MEMBER and NONE. If no

type _type value is specified, None (default) is used.


exclusion_ranges IP address No Exclusion Ranges exclude This field indicates the start to end
range address range. You can also include a
comment. The valid format is: start
address-end address/comment.
Example: “2000::1-2000::5/’The range
for printers’”
Merging data from an import preserves
the default value.

on page 8.
EA-Users String No Extensible extensible EA-Users is an example of a user defined


IPv4 Fixed Address/Reservation
Note: You can use the fixed address header to import reservations. When you import a reservation, you must specify
00:00:00:00:00:00 in the mac_address field.
Header-FixedAddress String Yes Example: FixedAddress
ip_address IP address Yes IP Address ipv4addr Example: 10.0.0.11
_new_ip_address IP address No Add this field to overwrite the

ip_address field when you use the
always_update_dns Boolean No DNS Zones always_update_ Example: FALSE

Associations dns
prepared_zero Boolean No Example: FALSE


ddns_domainname String No DDNS Domain ddns_domainname Example: ddns.corp100.com

Name

Requests
broadcast_address IP address No Broadcast Address Example: 10.0.0.1
routers IP address No Routers Example: "10.0.0.1,10.0.0.100,"

list
domain_name_ IP address No Name Servers Example: "10.2.3.4,11.2.3.4,"

servers list
dhcp_client_ String No Client Identifier dhcp_client_

identifier identifier
enable_ddns Boolean No Enable DDNS Example: FALSE

Updates

requested_ options option_list_request
circuit_id String No agent_circuit_id This field is required when match_option

= CIRCUIT_ID.
Example: 11
remote_id String No agent_remote_id This field is required when match_option

= REMOTE_ID.
Example: xyz
mac_address MAC No MAC Address mac This field is required if match_option =
address Yes for MAC_ADDRESS, or if you are importing a
reservation reservation. For reservations, you must
enter 00:00:00:00:00:00 in this field.
Example: aa:bb:cc:dd:ee:ff
match_option String No match_client Data must be in the following format:

['MAC_ADDRESS','CLIENT_ID','CIRCUIT_I
D','REMOTE_ID']

integer

time time
ddns_hostname String No ddns_hostname Example: host1.test.com

integer
OPTION-2 Integer No Custom DHCP options This is an example of a DHCP option. For
Options information, see Data Specific
Example: 50
Options information, see Data Specific


information Options information, see Data Specific
Example: dfdfdfd’ name implies
code/number 200
EA-Site String No Extensible Attribute extensible_ EA-Site is an example of a predefined

Site attributes extensible attribute. You can add other
on page 8.
EA-Users String No Extensible Attribute extensible_ EA-Users is an example of a user defined

Users attributes attribute this is of a List type
(enumeration list). You can add other
user defined attributes to the data file.
on page 8.

Examples
This section contains examples of how to create data files for IPv4 fixed addresses. All examples use comma as the
Adding an IPv4 Fixed Address

This example shows how to import a new IPv4 fixed address.
header-FixedAddress,ip_address*,network_view,mac_address*,match_option,remote_id,
EA-Site
FixedAddress,100.0.0.1,Default,aa:aa:aa:aa:aa:aa,Remote_ID,xyz,USA
Overwriting IPv4 Fixed Address Data

This example shows how to overwrite the MAC address of an existing IPv4 fixed address from aa:aa:aa:aa:aa:aa to
bb:aa:aa:aa:aa:aa.
header-FixedAddress,ip_address*,mac_address*
FixedAddress,100.0.0.1,bb:aa:aa:aa:aa:aa
This example shows how to overwrite the address of an existing IPv4 fixed address from 100.0.0.1 to 100.0.0.10.
header-FixedAddress,ip_address*,_new_ip_address,mac_address*
FixedAddress,100.0.0.1,100.0.0.10,bb:aa:aa:aa:aa:aa

Merging IPv4 Fixed Address Data

This example shows how to merge a new comment to an existing IPv4 fixed address.
header-FixedAddress,ip_address,mac_address*,comment
FixedAddress,100.0.0.10,bb:aa:aa:aa:aa:aa,A new comment here.
This example shows how to merge new routers addresses and the domain name to an existing IPv4 fixed address.
header-FixedAddress,ip_address*,mac_address*,routers,domain_name
FixedAddress,100.0.0.10,bb:aa:aa:aa:aa:aa,”2.2.2.2,4.4.4.4”,ns1.corp100.com
Adding an IPv4 Reservation

This example shows how to import a new IPv4 reservation.
header-FixedAddress,ip_address*,network_view,mac_address*,EA-Site
FixedAddress,100.0.0.1,Default,00:00:00:00:00:00,USA
IPv6 Fixed Address
Header-IPv6FixedAdd String Yes Example: IPv6FixedAddress

ress
address_type Enumeration No Address address_type Valid values are ADDRESS, PREFIX, and
BOTH. If no value is specified, ADDRESS
(default) is used.
Example: PREFIX
parent String No Select Network network This field is required when address_type
is ‘PREFIX’. 
Example: 2000::/16
ip_address IP address No Address ipv6addr This field is required if address_type is

Example: 2000::5
_new_ip_address IP address No Add this field to overwrite the ip_address

merge option.
ipv6_prefix IPv6 address No Prefix Delegated ipv6prefix This field is required if address_type is
prefix ‘PREFIX’ or ‘BOTH’.
Example: 2000:1111::
_new_ipv6_prefix IPv6 address No Add this field to overwrite the ipv6_prefix

prefix field when you select the overwrite or
merge option.
ipv6_prefix_bits Integer No ipv6prefix_bits This field is required if address_type is

‘PREFIX’ or ‘BOTH’.
Example: 32
name String No Name name Example: IPv6FixedAddr


match_option String No match_client Only ‘DUID’ is allowed.

Example: DUID
duid String No DUID duid Example: 0001
domain_name FQDN No Domain Name Example: ns1.corp100.com
domain_name_ IPv6 address No Name Servers Example: 2000::10,3000::10

servers list
valid_lifetime Unsigned No Valid Lifetime valid_lifename Example: 43200

integer
preferred_lifetime Unsigned No Preferred Lifename preferred_lifetime Example: 604800

integer
Options options information, see Data Specific Guidelines
on page 8.
Example: ‘12’ name implies option space
= ‘DHCPv6’, option code/number 7
information Options options information, see Data Specific Guidelines
on page 8.
code/number 200

on page 8.
EA-Users String No Extensible Attribute extensible_ EA-Users is an example of a user defined

Users attributes attribute this is of a List type
(enumeration list). You can add other user
defined attributes to the data file. For
on page 8.

Examples
This section contains examples of how to create data files for IPv6 fixed addresses. All examples use comma as the
Adding an IPv6 Fixed Address

This example shows how to import a new IPv6 fixed address.
header-IPv6FixedAddress,address_type,ip_address,network_view,match_option,EA-Site
IPv6FixedAddress,ADDRESS,2000::5,Default,DUID,USA

Overwriting IPv6 Fixed Address Data

This example shows how to overwrite an existing IPv6 fixed address from 2000::5 to 2000::1.
header-IPv6FixedAddress,address_type,ip_address,_new_ip_address
IPv6FixedAddress,ADDRESS,2000::5,2000::1
Merging IPv6 Fixed Address Data

This example shows how to merge a new comment to an existing IPv6 fixed address.
header-IPv6FixedAddress,ip_address,comment
IPv6FixedAddress,2000::1,A new comment.
This example shows how to merge a new domain name to an existing IPv6 fixed address.
header-IPv6FixedAddress,ip_address,domain_name
IPv6FixedAddress,2000::1,ns1.corp100.com
DHCP MAC Filter
(Yes/No) Object
Header-DhcpMacFilter String Yes Example: DhcpMacFilter
name String Yes Name name Example: MAC filter 1
_new_name String No Add this field to overwrite the name

merge option.
never_expires Boolean No Never Expires Example: TRUE
expiration_interval Integer No Automatically expires default_mac_address Example: 3624

in _expiration
enforce_expiration_time Boolean No Enforce Expiration enforce_expiration_ Example: FALSE

Times times

Site extensible attribute. You can add
other predefined attributes to the
data file. For information about data
EA-Users String No Extensible Attribute extensible_attributes EA-Users is an example of a user

Users defined attribute. You can add other
user defined attributes to the data
file. For information about data
ADMGRP-JoeSmith String No Permissions Admin permission ADMGRP-JoeSmith is an example of

Group/Role an admin permission of a specific
admin group. For information about
data format and examples, see Data

Examples
This section contains examples of how to create data files for DHCP MAC filters. All examples use comma as the
Adding a DHCP MAC Filter

This example shows how to import a DHCP MAC filter.
header-dhcpmacfilter,name*,never_expires,expiration_interval,enforce_expiration_time,c
omment
dhcpmacfilter,MacFilter01,FALSE,3600,TRUE,This is a comment.
Overwriting DHCP MAC Filter Data

This example shows how to overwrite the MAC filter name from MacFilter01 to MacFilter02.
header-dhcpmacfilter,name*,_new_name
dhcpmacfilter,MacFilter01,MacFilter02
Merging DHCP MAC Filter Data

This example shows how to merge extensible attributes Site and Users, as well as admin group DHCP_admins with a
RO permission.
header-dhcpmacfilter,name*,EA-Site,EA-Users,ADMGRPDHCP_admins
dhcpmacfilter,MacFilter02,USA,John Smith,RO
MAC Filter Address

Header-MacFilterAddress String Yes Example: MacFilterAddress
parent String Yes MAC Address filter_name Example: MAC filter 1

Filter
mac_address MAC address Yes MAC Address mac_address Example: aa:bb:cc:dd:ee:ff
_new_mac_address MAC address No Add this field to overwrite the

mac_address field when you select the
is_registered_user Boolean No Register as User Example: TRUE
registered_user String No Register as User Example: John Doe
guest_first_name String No Register as Guest: Example: John

First Name
guest_middle_name String No Register as Guest: Example: Doe

Middle Name
guest_last_name String No Register as Guest: Example: Doe

Last Name
guest_email Email address No Register as Guest: Example: jdoe@infoblox.com

Email Address
guest_phone String No Register as Guest: Example: 408-111-1111

Phone Number
guest_custom_field1 String No Register as Guest:

Custom Field 1



Custom Field 2

Custom Field 3

Custom Field 4
never_expires Boolean No Never Expires Example: FALSE
expire_time Date/Time No Expires On Data must be in this format: 

"CCYY-MM-DDThh:mm:ss[Z(+-)hh:mm]"
Example: 2009-02-29T10:30:00Z

on page 8.


Examples
This section contains examples of how to create data files for DHCP MAC filters. All examples use comma as the
Adding a DHCP MAC Filter

This example shows how to import MAC filter address, aa:aa:aa:aa:aa:aa, to MacFilter01.
header-macfilteraddress,parent*,mac_address*,is_registered_user,never_expires,comment
macfilteraddress,MacFilter01,aa:aa:aa:aa:aa:aa,FALSE,TRUE,This is a comment.
Overwriting DHCP MAC Filter

This example shows how to overwrite a MAC filter address with an expiration time.
header-macfilteraddress,parent*,mac_address*,never_expires,expire_time
macfilteraddress,MacFilter01,aa:aa:aa:aa:aa:aa,FALSE,2010-12-30T10:30:00Z
Merging DHCP MAC Filter

This example shows how to merge extensible attributes Site and Users to an existing MAC filter address.
header-macfilteraddress,parent*mac_address*,EA-Site,EA-Users
macfilteraddress,MacFilter01,aa:aa:aa:aa:aa:aa,USA,John Smith

Option Filter
Header-OptionFilter String Yes Example: OptionFilter
name String Yes Name name Example: Option Filter 1

option.
boot_file String No Boot File boot_file Example: bootfile1
boot_server String No Boot Server boot_server Example: abc.corp100.com
lease_time Integer No Lease Time lease_time Example: 7200

integer
next_server String No Next Server next_server Example: blue.domain.com
option_space String No Option Space option_space Example: Infoblox_DHCP
OPTION-2 Integer No Custom DHCP option_list This is an example of a DHCP option. For
on page 8.
Example: 50
OPTION-1 String No Custom DHCP options_list This is an example of a DHCP option. For
on page 8.
OPTION-XXXX-200 Option Np Extensible options_list This is an example of a DHCP option. For

information Attribute Site information, see Data Specific Guidelines
on page 8.
code/number 200

page 8.


Examples
This section contains examples of how to create data files for option filters. All examples use comma as the separator.
Adding an Option Filter

This example shows how to import an option filter with boot file, boot server, and lease time.
header-OptionFilter name*,comment,boot_file,boot_server,lease_time
OptionFilter,OptionFilter01,This is a comment.,bootfile01 1.2.3.4,12800
Overwriting Option Filter Data

This example shows how to overwrite an option filter name and boot file name.
header-OptionFilter,name*,_new_name,boot_file
OptionFilter,OptionFilter01,OptionFilter02,bootfile02
Merging Option Filter Data

This example shows how to merge to an option filter the PXE lease time and next server domain name.
header-OptionFilter,name*,pxe_lease_time,next_server
OptionFilter,OptionFilter02,12800,next.corp100.com
Option Filter Match Rule
Header-OptionFileterMatchRule String Yes Example: OptionFilterMatchRule
parent Option filter Yes Option Filter filter The name of the parent option
Name filter. Example: Option filter 1
match_option String Yes Match Option num Example: OPTION-1 (option space
is DHCP)
match_value String Yes Match Value value Example: 255.0.0.0
_new_match_value String No Add this field to overwrite the

match_value field when you select
is_substring Boolean No Value is a is_substring Example: FALSE

substring
substring_offset Integer No Substring Offset substring_offset Example: 2
substring_length Unsigned No Substring Length substring_length Example: Doe

integer

Examples
This section contains examples of how to create data files for option filter match rules. All examples use comma as
the separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an Option Filter Match Rule

This example shows how to import an option filter match rule.
header-OptionFilterMatchRule,parent*,match_option*,match_value*,is_substring,substring
_offset
OptionFilterMatchRule,OptionFilter01,OPTION-1,2.2.2.2,FALSE,0
Overwriting Option Filter Match Rule Data

This example shows how to overwrite an existing match option with OPTION-2 and add a new match value of 3.3.3.3.
header-OptionFilterMatchRule,parent*,match_option*,match_value*,_new_match_value
OptionFilterMatchRule,OptionFilter01,OPTION-2,2.2.2.2,3.3.3.3
Merging Option Filter Match Rule Data

This example shows how to merge a substring length to an existing option filter match rule.
header-OptionFilterMatchRule,parent*,match_option*,match_value*,substring_length
OptionFilterMatchRule,OptionFilter02,OPTION-2,3.3.3.3,256

Relay Agent Filter

Field Name Data Type (Yes/No) Associated GUI Field Object Usage and Guidelines
Header-RelayAgentFilter String Yes Example: RelayAgentFilter
name String Yes Name name Example: Relay Agent Filter 1

merge option.
circuit_id_rule String No Circuit ID: Match is_circuit_id Example: MATCHES_VALUE

Value
circuit_id String No Circuit ID circuit_id_name
remote_id_rule String No Remote ID: Match is_remote_id Example: MATCHES_VALUE

Value
remote_id Integer No Remote ID remote_id_name Example: 50

predefined attributes to the data file.
on page 8.
EA-Users String No Extensible Attribute extensible_ EA-Users is an example of a user

Users attributes defined attribute. You can add other
user defined attributes to the data file.
on page 8.
Examples
This section contains examples of how to create data files for relay agent filters. All examples use comma as the
Adding a Relay Agent Filter

This example shows how to import a relay agent filter with a circuit ID and a remote ID.
header-RelayAgentFilter,name*,circuit_id_rule,circuit_id,remote_id_rule,remote_id
RelayAgentFilter,relayagent1,MATCHES_VALUE,123456,MATCHES_VALUE,abcd
Overwriting Relay Agent Filter Data

This example shows how to overwrite the circuit ID and remote ID of an existing relay agent filter.
header-RelayAgentFilter,name*,circuit_id_rule,circuit_id,remote_id_rule remote_id
RelayAgentFilter,relayagent1,MATCHES_VALUE,336699,MATCHES_VALUE,xyz
Merging Relay Agent Filter Data

This example shows how to merge a comment and extensible attribute Site to an existing relay agent filter.
header-RelayAgentFilter,name*,comment,EA-Site
RelayAgentFilter,relayagent1,This is a comment.,USA

NAC Filter
(Yes/No) Object
Header-NACFilter String Yes Example: NACFilter
name String Yes Name name Example: NAC Filter

option.
expression Option list No Match the following expression To include the option list in the Matching
rule the following rules table in Grid Manager,
you must enclose the expression in
brackets. 
Example:
(Sophos.ComplianceState="Compliant"
AND RADIUS.ServerError="TRUE")

on page 8.
EA-Users String No Extensible Attribute extensible_attributes EA-Users is an example of a user defined

Users attribute. You can add other user defined
Examples
This section contains examples of how to create data files for NAC filters. All examples use comma as the separator.
Adding a NAC Filter

This example shows how to import a new NAC filter.
header-NacFilter,name*,comment,expression,EA-Site
NacFilter,nacfilter01,This is a comment.,option ServerError="true",USA
Overwriting NAC Filter Data

This example shows how to overwrite the name and comment of an existing NAC filter.
header-NacFilter,name*,_new_name,comment
NacFilter,nacfilter01,nacfilter02,This is a new comment.
Merging NAC Filter Data

This example shows how to merge the extensible attribute Users to an existing NAC filter.
header-NacFilter,name*,EA-Users
NacFilter,nacfilter02,John Smith

IPv4 Option Space
(Yes/No) Object
Header-OptionSpace String Yes Example: OptionSpace
name String Yes Name name Example: ABC-co options

merge option.
Examples
This section contains examples of how to create data files for option spaces. All examples use comma as the
Adding an IPv4 Option Space

This example shows how to import a new IPv4 option space.
header-OptionSpace,name*,space_type
OptionSpace,Optionspace01,VENDOR_SPACE
Overwriting IPv4 Option Space Data

This example shows how to overwrite the IPv4 option space name with Optionspace02.
header-OptionSpace,name*,_new_name
OptionSpace,Optionspace01,Optionspace02
Merging IPv4 Option Space Data

This example shows how to merge a comment to the IPv4 option space Optionspace02.
header-OptionSpace,name*,comment
OptionSpace,Optionspace02,This is a comment.

IPv6 Option Space
(Yes/No) Object
Header-IPv6OptionS String Yes Example: IPv6OptionSpace

pace
name String Yes Name name Example: MySpace

merge option.
comment String No Comment comment Example: Custom option space
ipv6_enterprise_ String No Enterprise Number This is the vendor’s enterprise number

number that is registered with IANA.
Example: 7779
IPv4 Option Definition

Header-OptionDefinition String Yes Example: OptionDefinition
space String Yes Option Space space Example: ABC-co options
_new_space String No Add this field to overwrite the space field

option.
name String Yes Name name Example: Option one

when you use the overwrite or merge
option.
code String Yes Options: Code code
type String Yes Options: Type type Use any of the following values: T_FLAG,
T_STRING, T_TEXT, T_IP_ADDRESS,
T_ARRAY_IP_ADDRESS, T_DOMAIN,
T_ARRAY_DOMAIN, T_UINT8,T_UINT16,
T_UINT32, T_INT8, T_INT16
Example: T_TEXT
Examples
This section contains examples of how to create data files for option definitions. All examples use comma as the
Adding an IPv4 Option Definition

This example shows how to import an option definition to the IPv4 option space Space01.
header-OptionDefinition,space*,name*,code*,type*
OptionDefinition,Space01,Option99,99,T_IP_ADDRESS

Overwriting IPv4 Option Definition Data

This example shows how to overwrite the IPv4 option definition type from T_IP_ADDRESS to T_FLAG.
header-OptionDefinition,space*,name*,code*,type*
OptionDefinition,Space01,Option99,99,T_FLAG
Merging IPv4 Option Definition Data

This example shows how to merge a new space and a new name to an existing IPv4 option definition.
header-OptionDefinition,space*,_new_space,name*,_new_name
OptionDefinition,Space01,New_Space01,Option99,New_Option99
IPv6 Option Definition

Header-IPv6OptionDefin String Yes Example: IPv6OptionDefinition

ition
space String Yes Option Space space Example: MySpace
_new_space String No Add this field to overwrite the space field

option.
name String Yes Name name Example: MyOption1

when you use the overwrite or merge
option.
code String Yes Options: Code code Example: 10
type String Yes Options: Type type Use any of the following values:
'T_ARRAY_DOMAIN', 'T_ARRAY_INT16',
'T_ARRAY_INT32', 'T_ARRAY_INT8',
'T_ARRAY_IP_ADDRESS','T_ARRAY_IP_AD
DRESS_PAIR','T_ARRAY_UINT16',
'T_ARRAY_UINT32', 'T_ARRAY_UINT8',
'T_DOMAIN', 'T_FLAG',
'T_FLAG_IP_ADDRESS', 'T_FLAG_TEXT',
'T_INT16', 'T_INT32', 'T_INT8',
'T_IP_ADDRESS', 'T_STRING', 'T_TEXT',
'T_UINT16', 'T_UINT32', 'T_UINT8',
'T_UINT8_1_2_4_8' 
Example: T_INT8

Upgrade Groups and Schedules

Consider the following when you import upgrade groups and their distribution and upgrade schedules:
• The appliance imports a new upgrade group only when both the distribution and upgrade schedules are
inactive.
• You can modify members and the comment field of an existing upgrade group only when both the distribution
and upgrade schedules are inactive.
• You can modify distribution related fields of an existing upgrade group only when the distribution schedule is
inactive.
• You can modify upgrade related fields of an existing upgrade group only when the upgrade schedule is inactive.
• The Grid Master is the only member of the Grid Master group. You cannot move it to another upgrade group.
• You cannot change the members of the Reporting Member group nor move them to another upgrade group.
• When you remove a member from its original group, it will be placed in the Default group. You may notice
additional members in the Default group if you remove members from any upgrade groups.
• When you specify both dependency and distribution or upgrade time for an upgrade group, dependency takes
precedence.
Note: When you import an upgrade group and its distribution and upgrade schedules, you cannot control the
activation and deactivation of the schedules. You can activate and deactivate the schedules through the GUI
after the import.
(Yes/No) Field Object/Name
Header-upgrade_group String Yes UpgradeGroup Example: UpgradeGroup
name String Yes Name Example: UpgradeGp1
comment String No Comment comment Add this field to overwrite the

comment you entered for the
upgrade group.
members Grid No Member members Enter a list of Grid members

member Assignment separated by commas. Use the
list Name FQDNs of the Grid members.
Enclose the entire string in double
quotes.
Example:
“corp100.mktg.com,corp100.dev
.com”
time_zone String No Time Zone time_zone The value in this field applies to
both distribution_time and
upgrade_time. If you do not specify
a time zone, the Grid level time zone
is used.
distribution_dependent_group String No Name distribution_ Enter the name of the preceding

dependent_group upgrade group that this group
depends on during a distribution.
distribution_policy String No Distribute to distribution_policy Valid values are: SIMULTANEOUSLY

Members or SEQUENTIALLY.
distribution_time Time No Start distribution_time Enter the distribution start date and
Distribution time in YYYY-MM-DDTHH:MM:SS
(Date/Time) format.
upgrade_dependent_group String No Name upgrade_dependent_ Enter the name of the upgrade

group group that this group depends on
during an upgrade.


(Yes/No) Field Object/Name
upgrade_policy String No Upgrade upgrade_policy Valid values are: SIMULTANEOUSLY

Members or SEQUENTIALLY.
upgrade_time Time No Start Upgrade upgrade_time Enter the upgrade start date and
time in YYYY-MM-DDTHH:MM:SS
format.

Infoblox CSV Import Reference: NIOS 6.5 For Infoblox Core Network Services Appliances

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Infoblox CSV Import Reference: NIOS 6.5 For Infoblox Core Network Services Appliances

Transféré par

Droits d'auteur :

Formats disponibles

Infoblox CSV Import Reference

NIOS 6.5 CSV Import Reference (Rev. A) 3

4 CSV Import Reference (Rev. A) NIOS 6.5

NIOS 6.5 CSV Import Reference (Rev. A) 5

6 CSV Import Reference (Rev. A) NIOS 6.5

NIOS 6.5 CSV Import Reference (Rev. A) 7

Guidelines for CSV Import

Data Specific Guidelines

8 CSV Import Reference (Rev. A) NIOS 6.5

CSV File Format

NIOS 6.5 CSV Import Reference (Rev. A) 9

Table 1.1 CSV File Example 1

1 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Secondary Address

2 HEADER-HostRecord configure_for_dns* FQDN* ADDRESSES

3 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129

4 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0

5 HostRecord TRUE host1.dhcp.corp100.com 172.20.2.21

6 HostRecord TRUE host2.dhcp.corp100.com 172.20.2.22

Table 1.2 CSV File Example 2

1 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Secondary Address

2 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129

3 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0

4 HEADER-HostRecord configure_for_dns* FQDN* ADDRESSES

5 HostRecord TRUE host1.dhcp.corp100.com 172.20.2.21

6 HostRecord TRUE host2.dhcp.corp100.com 172.20.2.22

10 CSV Import Reference (Rev. A) NIOS 6.5

Table 1.3 CSV File Example 3

1 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Secondary Address

2 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129

3 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0

4 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Host Range

5 NETWORK 10.176.90.0 255.255.255.128 10.176.90.1 10.176.90.4-126

6 NETWORK 10.176.90.128 255.255.255.128 10.176.90.129 10.176.90.132-254

NIOS 6.5 CSV Import Reference (Rev. A) 11

Supported Object Types

Table 1.4 Supported DNS Object Types

DNS Object Type Required Fields & Syntax

Table 1.5 Supported DHCP Object Types

DHCP Object Type Required Fields & Syntax

12 CSV Import Reference (Rev. A) NIOS 6.5

DHCP Object Type Required Fields & Syntax

Table 1.6 Other Supported Objects

Upgrades Required Fields and Syntax

Authoritative DNS Zone

Required Associated Associated PAPI

Header-AuthZone String Yes

fqdn FQDN Yes Name name Example: test.com

zone_format String Yes Valid values are FORWARD, IPV4,and IPV6

prefix String No prefix Prefix is used for reverse-mapping RFC2317

grid_primary Grid member No Grid Primary primary

grid_primary_stealth Boolean No Stealth stealth Example: FALSE

NIOS 6.5 CSV Import Reference (Rev. A) 13

Required Associated Associated PAPI

grid_secondaries Member No Grid secondaries Data must be in the following format:

ns_group String No Name server ns_group Example: name-ns-group1

comment String No Comment comment

disabled Boolean No Disable disable Example: FALSE

create_underscore_ Boolean No Automatically create_underscore_ Example: FALSE

allow_active_dir List of IP No Allow enable_ad_server The Valid value is a list of IP addresses.

14 CSV Import Reference (Rev. A) NIOS 6.5

Required Associated Associated PAPI

soa_mname FQDN No SOA MNAME soa_mname Example: infoblox.localdomain

soa_email Email No Email address soa_email Example: root@test.com