NIOS CSV Ref 6.2

Infoblox CSV Import Reference
NIOS 6.2
for Infoblox Core Network Services Appliances
Copyright Statements
2011, 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: Infoblox-250-A, -550-A, -1050-A, -1550-A, -1552-A, -1852-A, -2000-A, and -4010
Document Number: 400-0374-000 Rev. A
Document Updated: July 25, 2011
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.2
CSV Import Reference (Rev. A)
Preface
Document Overview
The CSV import reference provides general guidelines and file format information about CSV import. It was last
updated on July 25, 2011. 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 CLI Guide

Infoblox API Documentation
Infoblox NIOS Administrator Guide
Infoblox IBOS Administrator Guide
Infoblox-500, Infoblox-1000 and Infoblox-1200 Quick Start
Infoblox User Guide for the Infoblox-1050, 1550, and 1552 Appliances
Infoblox User Guide for the Infoblox-500, -550 Appliance
Infoblox Installation Guide for the Infoblox-550, -1050, -1550, and -1552 Appliances
Infoblox Installation Guide for the Infoblox-550-A, -1050-A, -1550-A, and -1552-A Appliances
Infoblox Installation Guide for the Infoblox-1852-A Appliance
Infoblox Installation Guide for the Infoblox-250 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
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.
NIOS 6.2
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.
NIOS 6.2
Preface
NIOS 6.2
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 7

General Guidelines on page 7
Data Specific Guidelines on page 8
CSV File Format on page 9
Supported Object Types on page 11
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:
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.
NIOS 6.2
CSV Import Reference
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 123123, the imported data is
123123, 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 11. 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.
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.
NIOS 6.2
CSV File Format
CSV File Format

A CSV file is typically created and edited using a spreadsheet, though you can create a CSV file in a text editor using
any supported separator. You can include more than one object type in a single CSV file when you add or modify data.
For information, see Supported Object Types on page 11. 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 7.
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
D
EA-Gateway
HEADER-NETWORK
ADDRESS*
NETMASK*
EA-Secondary Address
HEADER-HostRecord
FQDN*
ADDRESSES
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
HostRecord
host1.dhcp.corp100.com
172.20.2.21
HostRecord
172.20.2.22
172.16.213.0
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
HEADER-NETWORK
ADDRESS*
NETMASK*
EA-Gateway
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
HEADER-HostRecord
FQDN*
ADDRESSES
HostRecord
172.20.2.21
HostRecord
172.20.2.22
NIOS 6.2
E
172.16.213.0
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
HEADER-NETWORK
ADDRESS*
NETMASK*
EA-Gateway
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-NETWORK
ADDRESS*
NETMASK*
EA-Gateway
EA-Host Range
NETWORK
10.176.90.0
255.255.255.128
10.176.90.1
10.176.90.4-126
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 9.
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
10
NIOS 6.2
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 12.
A Record
A Record on page 15
AAAA Record
AAAA Record on page 17
CNAME Record
CNAME Record on page 18
DNAME Record
DNAME Record on page 19
MX Record
MX Record on page 20
NAPTR Record
NAPTR Record on page 22
NS Record
NS Record on page 23
PTR Record
PTR Record on page 25
SRV Record
SRV Record on page 27
TXT Record
TXT Record on page 26
Host Record
Host Record on page 29
IPv4 Host Address
IPv4 Host Address on page 31
IPv6 Host Address
IPv6 Host Address on page 33
Rulesets
NXDOMAIN and Blacklist Rulesets on page 35
NXDOMAIN Rule
NXDOMAIN Rule on page 36
Blacklist Rule
Blacklist Rule on page 36
DNS64 Synthesis Group
DNS64 Synthesis Group on page 37
Table 1.5 Supported DHCP Object Types

DHCP Object Type
IPv4 Network
IPv4 Network on page 38
IPv6 Network
IPv6 Network on page 41
IPv4 Shared Network
IPv4 Shared Network on page 43
IPv6 Shared Network
IPv6 Shared Network on page 45
IPv4 DHCP Range
IPv4 DHCP Range on page 47
NIOS 6.2
11
DHCP Object Type
IPv6 DHCP Range
IPv6 DHCP Range on page 51
IPv4 Fixed Address and Reservation
IPv4 Fixed Address/Reservation on page 52
IPv6 Fixed Address
IPv6 Fixed Address on page 55
DHCP MAC Filter
DHCP MAC Filter on page 57
MAC Filter Address Item
MAC Filter Address on page 58
Option Filter
Option Filter on page 60
Option Filter Match Rule
Option Filter Match Rule on page 61
Relay Agent Filter
Relay Agent Filter on page 63
NAC Filter
NAC Filter on page 64
IPv4 Option Space
IPv4 Option Space on page 65
IPv6 Option Space
IPv6 Option Space on page 66
IPv4 Option Definition
IPv4 Option Definition on page 66
IPv6 Option Definition on page 67
Authoritative DNS Zone

Field Name
Data Type
Required
(Yes/N0)
Header-AuthZone
String
Yes
fqdn
FQDN
Yes
zone_format
String
Yes
view
String
No
prefix
String
No
_new_prefix
String
No
grid_primary
Grid member
No
Grid Primary
primary
Use the hostname of the grid member in this

field.
Example: infoblox.localdomain
grid_primary_stealth
Boolean
No
Stealth
stealth
Example: FALSE
external_primaries
Server list
No
External
Primary
primary
Data must be in the following format:

name/ip/stealth/use_2x_tsig/
use_tsig/tsig_name/tsig_key.
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 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"
12
Associated
GUI Field
Associated PAPI
Method
Usage and Guidelines
Name
name
Example: test.com
Valid values are FORWARD, IPV4,and IPV6
DNS view
views
If no view is specified, the Default view is used.
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.
Add this field to overwrite the prefix field when
you select the overwrite or merge option.
NIOS 6.2
Field Name
Data Type
grid_secondaries
Member
server list
Required
(Yes/N0)
Associated
GUI Field
Associated PAPI
Method
No
Grid
Secondary
secondaries

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
Secondary
secondaries

name/ip/stealth/use_2x_tsig/use_
tsig/tsig_name/tsig_key. 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 both use_2x_tsig and use_tsig are
TRUE, only use_tsig = TRUE and the tsig key
name and key are imported.
Example: "sec1.com/1.1.1.1/FALSE/FALSE/
FALSE/foo/sdfssdf86ew"
ns_group
String
No
Name server
group
ns_group
Example: name-ns-group1
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disable
Example: FALSE
create_underscore_
zones
Boolean
No
Automatically
create
underscore
zones
create_underscore_
zones
Example: FALSE
allow_active_dir
List of IP
addresses
No
Allow
unsigned
updates from
these domain
controllers
enable_ad_server
The Valid value is a list of IP addresses.
soa_refresh
Unsigned
integer
No
Refresh
soa_refresh
When you modify this field to override an

inherited value, you must include values for all
SOA timer fields. The appliance updates all the
SOA timers when you update any of them.
soa_retry
Unsigned
integer
No
Retry
soa_retry
Ensure that you include this field when you

override the soa_refresh field.
soa_expire
Unsigned
integer
No
Expire
soa_expire

soa_default_ttl
Unsigned
integer
No
Default TTL
soa_default_ttl

soa_negative_ttl
Unsigned
integer
No
Negativecaching TTL
soa_negative_ttl

soa_mname
FQDN
No
SOA MNAME
field
soa_mname
Example: infoblox.localdomain
soa_email
Email
address
No
Email address
for SOA
MNAME field
soa_email
Example: root@test.com
soa_serial_number
Unsigned
integer
No
Serial Number
soa_serial_number
disable_forwarding
Boolean
No
Dont user
forwarders...
disable_forwarding
NIOS 6.2
Example: 1.1.1.1, 10.0.0.1
Example: TRUE
13
Field Name
Data Type
Required
(Yes/N0)
Associated
GUI Field
Associated PAPI
Method
allow_update_
forwarding
Boolean
No
Allow updates
from
forward_to
Example: FALSE
update_forwarding
ACL
No
Allow updates
from...
Permission
table
forward_to
Data must be in the following formats:

ip address/permission
network/network cidr/permission
ANY/permission
TSIG-XXX/permission
Permission can be ALLOW or DENY
If the first value is not Any or TSIG-, it is
assumed to be an IP or network address.
Example:
"10.0.0.10/Allow,11.0.0.0/16/Deny,TSIG-foo
/sdfdsfwhsdgfsw8sdf/Allow"
allow_transfer
ACL
No
Allow zone
transfers to
allow_transfer
Example: "12.0.0.12/Deny,1234::/64/Allow"
allow_update
ACL
No
Allow updates
from
allow_update
Example: 13.0.0.0/8/Allow
allow_query
ACL
No
Allow queries
from
allow_query
Example: 127.0.0.1/Allow
notify_delay
Unsigned
integer
No
notify_delay
This field specifies the seconds of delay the

notify messages are sent to the secondaries.
The valid value is between 5 and 86400
seconds.
Example: 10
EA-Site
String
No
Extensible
attribute
extensible_attributes
EA-Site is an example of a predefined

extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and examples,
see Data Specific Guidelines on page 8.
EA-Users
List
No
Extensible
attribute
EA-Users is an example of a user defined

attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see Data
Specific Guidelines on page 8.
ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
ADMGRP-JoeSmith is an example of an admin

permission of a specific admin group. For
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/
False
14
NIOS 6.2
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,
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
Field Name
Data Type
Required
(Yes/No)
Header-ARecord
String
Yes
fqdn
FQDN
Yes
_new_fqdn
FQDN
No
view
String
No
NIOS 6.2
Associated GUI
Field
Associated PAPI Method

Example: ARecord
Name
name
This field combines the A record name

and the zone name to form the FQDN.
Example: a1.corp100.com
Add this field to overwrite the fqdn field
when you select the overwrite or merge
option.
DNS View
views
If no view is specified, the Default view is

used.
15
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
address
IP address
Yes
IP Address
ipv4addr
Example: 192.138.1.1
_new_address
IP address
No
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disable
Example: FALSE
ttl
Unsigned
integer
No
TTL
ttl
This is an inherited field. For information,

Example: 7200
EA-Site
String
No
Extensible
attribute Site

information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users
List
No
Extensible
attribute Users

about data format and examples, see
Data Specific Guidelines on page 8.
ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Add this field to overwrite the address

field when you select the overwrite or
merge option.
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
16
NIOS 6.2
AAAA Record
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Header-AaaaRecord
String
Yes
fqdn
FQDN
Yes
_new_fqdn
FQDN
No
view
String
No
DNS View
views

used. Example: Default
address
IPv6 address
Yes
IP Address
ipv6addr
Example: 100::10
_new_address
IPv6 address
No
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disabled
Example: FALSE
ttl
Unsigned
integer
No
TTL
ttl

Example: 7200
EA-Site
String
No
Extensible
attribute Site

on page 8.
EA-Users
List
No
Extensible
attribute Users

ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission

Example: AaaaRecord
Name
zone
This field combines the AAAA record

name and the zone name to form the
FQDN. Example: aaaa1.corp100.com
option.

merge option.
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
NIOS 6.2
17
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
Field Name
Data Type
Required
(Yes/No)
Header-CnameRecord
String
Yes
fqdn
FQDN
Yes
_new_fqdn
FQDN
No
view
String
No
DNS View
views

canonical_name
Domain
name
Yes
Canonical Name
canonical
Example: www.corp100.com
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disabled
Example: FALSE
ttl
Unsigned
integer
No
TTL
ttl

Example: 28800
EA-Site
String
No
Extensible
attribute Site

on page 8.
ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
18
Associated GUI
Field
Associated PAPI
Method

Example: CnameRecord
Alias
zone
This field combines the CNAME record

FQDN. Example: c1.corp100.com
option.
NIOS 6.2
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
Field Name
Data Type
Required
(Yes/No)
Header-DnameRecord
String
Yes
fqdn
FQDN
Yes
_new_fqdn
FQDN
No
view
String
No
DNS View
views

target
Domain
name
Yes
Target
target
Example: d1.foo.com
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disabled
Example: FALSE
ttl
Unsigned
integer
No
TTL
ttl

Example: 28800
EA-Site
String
No
Extensible
attribute Site

on page 8.
NIOS 6.2
Associated GUI
Field

Example: DnameRecord
Alias
zone
This field combines the DNAME record

FQDN. Example: d1.corp100.com
option.
19
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
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
Field Name
Data Type
Required
(Yes/No)
Header-MxRecord
String
Yes
fqdn
FQDN
Yes
_new_fqdn
FQDN
No
view
String
No
DNS View
views

mx
Domain
name
Yes
Mail Exchange
exchanger
Example: mailer.foo.com
_new_mx
Domain
name
No
20
Associated GUI
Field

Example: MxRecord
Mail
Destination
zone
This field combines the MX record name

Example: MX1.corp100.com
option.
Add this field to overwrite the mx field

option.
NIOS 6.2
Required
(Yes/No)
Associated GUI
Field
Unsigned
integer
Yes
Preference
pref
Example: 10
_new_priority
Unsigned
integer
No
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disable
Example: FALSE
ttl
Unsigned
integer
No
TTL
ttl

Example: 28800
EA-Site
String
No
Extensible
attribute Site

on page 8.
EA-Users
String
No
Extensible
attribute
Country

ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
Field Name
Data Type
priority
Add this field to overwrite the priority

merge option.
Examples
This section contains examples of how to create data files for MX records. All examples use comma as the separator.
Adding an MX Record
This example shows how to add an MX record, bind_mx.corp100.com, with a mail exchanger, exchange.corp100.com
and priority = 20.
header-mxrecord,fqdn*,mx*,priority*
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
NIOS 6.2
21
NAPTR Record
Field Name
Data Type
Required
(Yes/No)
Header-NaptrRecord
String
Yes
fqdn
FQDN
Yes
_new_fqdn
FQDN
No
view
String
No
DNS View
views

order
Unsigned integer
Yes
Order
order
Example: 10
_new_order
Unsigned integer
No
preference
Unsigned integer
Yes
_new_preference
Unsigned integer
No
flags
String
Yes
_new_flags
String
No
services
String
Yes
_new_services
String
No
regexp
String
Yes
_new_regexp
String
No
replacement
String
Yes
_new_replacement
String
No
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disable
Example: FALSE
ttl
Unsigned integer
No
TTL
ttl

Example: 28800
EA-Site
String
No
Extensible
attribute Site
extensible_attrib
utes

examples, see Data Specific Guidelines on
page 8.
22
Associated GUI
Field
Associated PAPI
Object

Example: NaptrRecord
Domain
name
This field combines the domain name and

the zone name to form the FQDN.
Example: aptr1.corp100.com
option.
Add this field to overwrite the order field

option.
Preference
preference
Example: 20
Add this field to overwrite the preference
merge option.
Flags
flags
You can leave this field empty.

Example: U
Add this field to overwrite the flags field
option.
Service
services

Example: SIP+D2U
Add this field to overwrite the services field
option.
REGEX
regexp

Example: http://([^/:]+)!\1!i
Add this field to overwrite the regexp field
option.
Replacement
replacement
Example: corp100.com
Add this field to overwrite the replacement
merge option.
NIOS 6.2
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
EA-Users
String
No
Extensible
attribute Country
extensible_attrib
utes

ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
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
Field Name
Data Type
Required
(Yes/No)
Header-NsRecord
String
Yes
fqdn
FQDN
Yes
Associated GUI Field
Associated PAPI
Object

Example: NsRecord
Zone
name
This field combines the domain name

Example: test.corp100.com
view
NIOS 6.2
String
No
DNS View
views
If no view is specified, the Default view

is used. Example: Default
23
Field Name
Data Type
Required
(Yes/No)
Associated PAPI
Object
dname
Domain name
Yes
Name Server
nameserver
Example: ns1.corp100.com
_new_dname
Domain name
No
zone_nameservers
Server list
Yes
Add this field to overwrite the dname

merge option.
Name server list
addresses

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
24
NIOS 6.2
PTR Record
Field Name
Data Type
Required
(Yes/No)
Header-PtrRecord
String
Yes
fqdn
FQDN
No
_new_fqdn
Reverse FQDN
No
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
ipv6addr
This field is required if you do not use

the fqdn field. Either the IP address or
FQDN is required. Example: 10.0.0.11
_new_address
IP address
No
dname
FQDN
Yes
_new_dname
FQDN
No
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disable
Example: FALSE
ttl
Unsigned
integer
No
TTL
ttl
This is an inherited field.

Example: 28800
EA-Site
String
No
Extensible attribute
Site

predefined attributes to the data file.
For information about data format and
examples, see Data Specific
ADMGRP-JoeSmith
String
No
Permissions Admin
Group/Role
permission
group. For information about data
format and examples, see Data
Associated PAPI
Object

Example: PtrRecord
Domain Name
name
zone
This field is required if you do not use

the address field. Either the IP address
or FQDN is required. Example:
10.0.0.10.in.addr.arpa
Add this field to overwrite the fqdn
field when you use the overwrite or
merge option.

field when you use the overwrite or
merge option.
Name
ptrdname
Example: ss.dd.ff
Add this field to overwrite the dname
merge option.
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
NIOS 6.2
25
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
Required
(Yes/No)
Header-TxtRecord
String
Yes
fqdn
FQDN
Yes
_new_fqdn
FQDN
No
view
String
No
DNS View
views

text
String
No
Text
text
_new_txt
String
No
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disable
Example: FALSE
ttl
Unsigned
integer
No
TTL
ttl

Example: 28800
EA-Site
String
No
Extensible attribute
Site

on page 8.
ADMGRP-JoeSmith
String
No
Permissions Admin
Group/Role
permission
26
Associated PAPI
Object

Example: TxtRecord
Name
name
zone
This field combines the record name and

Example: t1.corp100.com
option.
Add this field to overwrite the txt field

option.
NIOS 6.2
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
Field Name
Data Type
Required
(Yes/No)
Header-SrvRecord
String
Yes
fqdn
FQDN
Yes
_new_fqdn
FQDN
No
view
String
No
DNS View
views

priority
Unsigned
integer
Yes
Priority
priority
Example: 10
_new_priority
Unsigned
integer
No
weight
Unsigned
integer
Yes
_new_weight
Unsigned
integer
No
port
Unsigned
integer
Yes
_new_port
Unsigned
integer
No
target
Domain name
Yes
NIOS 6.2
Associated GUI
Field
Associated PAPI
Object

Example: SrvRecord
Service
name
zone
This field combines the service name and the

zone name to form the FQDN.
Example: _http._tcp.corp100.com
option.
Add this field to overwrite the priority field

option.
Weight
weight
Example: 20
Add this field to overwrite the weight field
option.
Port
port
Example: 80
Add this field to overwrite the port field when
Target
target
Example: foo.test.com
27
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
_new_target
Domain name
No
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disable
ttl
Unsigned
integer
No
TTL
ttl

Add this field to overwrite the target field
option.
Example: FALSE
This is an inherited field. For information, see

Example: 28800
EA-Site
String
No
Extensible
attribute Site
extensible_
attributes

page 8.
ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
admin permission of a specific admin group.
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
28
NIOS 6.2
Host Record
If only one IPv4 address is specified in the host record, you can add DHCP options to the host address.
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
Header-HostRecord
String
Yes
fqdn
FQDN
Yes
_new_fqdn
FQDN
No
view
String
No
DNS View
views

Example: Default
addresses
IP address or IP
address list
No
IP Addresses
ipv4addr
You must specify a value in this field or in the

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 31
and IPv6 Host Address on page 33.
ipv6_addresses
IP address or IP
address list
No
IP Addresses
ipv6addr
You must specify a value in this field or in the

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 31
and IPv6 Host Address on page 33.
aliases
Alias list
No
Aliases
aliases
Example: www.infoblox.com
configure_for_dns
Boolean
No
Enable in DNS
configure_for_
dns
Example: TRUE
comment
String
No
Comment
comment
disabled
Boolean
No
Disable
disabled
ttl
Unsigned
integer
No
TTL
ttl

Example: HostRecord
Name
name
zone
This field combines the host record name and

Example: h2.corp100.com
Add this field to overwrite the fqdn field when
Example: FALSE
This is an inherited field. For information, see

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_
dhcp
This field applies to the host address.

Example: TRUE
deny_bootp
Boolean
No
Deny BOOTP
Requests
deny_bootp

Example: FALSE
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
integer
No
Lease Time
lease_time
pxe_lease_time_
enabled
Boolean
No
Enable PXE
Lease Time
NIOS 6.2
29
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
Unsigned
integer
No
PXE Lease Time
pxe_lease_time
domain_name
FQDN
No
Domain Name
domain_name
domain_name_
servers
IP list
No
Name Server

Example: 5.6.7.8,1.2.3.4
routers
IP list
No
Router

Example: 2.0.0.2,1.2.3.4
match_option
String
No
ignore_dhcp_param
_request_list
Boolean
No
OPTION-1
String
OPTION-XXXX-200
Field Name
Data Type
pxe_lease_time
match_client
This field applies to the host address. Data must

be in the following format:
MAC_ADDRESS/RESERVED
Ignore
Optionalist
ignore-dhcp_
option_list_
request
No
Custom DHCP
Options
options

Example: 255.0.0.0 name implies
vendor_class=DHCP (default)
Option
information
No
Custom DHCP
Options
options

Example: dfdfdfd name implies
vendor_class=XXXX, optioncode/number 200
EA-Site
String
No
Extensible
attribute Site
extensible_
attributes
EA-Site is an example of a predefined extensible

attribute. You can add other predefined
attributes to the data file. For information about
data format and examples, see Data Specific
ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission

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,fqdn*,view
hostrecord,100.0.0.101,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,fqdn*,aliases,comment,ttl
hostrecord,100.0.0.102,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,fqdn*,_new_fqdn,ttl
hostrecord,100.0.0.101,host1.corp100.com,new_host1.corp100.com,1280
30
NIOS 6.2
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*,fqdn*,aliases,comment
hostrecord,100.0.0.102,host2.corp100.com,www.corp200.com,Japan
Merging Host Record Data

This example shows how to disable an existing host record.
header-hostrecord,addresses*,fqdn*,disabled
hostrecord,100.0.0.101,new_host1.corp100.com,TRUE
This example shows how to add additional aliases to a host record.

header-hostrecord,addresses*,fqdn*,aliases
hostrecord,100.0.0.102,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
(Yes/No)
Header-HostAddress
String
Yes
Example: HostAddress
parent
FQDN
Yes
Example: h1.corp100.com
view
String
No
DNS View
views

Example: Default
address
IP address
Yes
IP Address
ipv4addr
Example: 10.0.0.11
_new_address
IP address
No
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_
dhcp
Example: TRUE
deny_bootp
Boolean
No
Deny BOOTP
Requests
deny_bootp
Example: FALSE
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
integer
No
Lease Time
lease_time
pxe_lease_time_
enabled
Boolean
No
Enable PXE Lease

Time
pxe_lease_time
Unsigned
integer
No
PXE Lease Time
pxe_lease_time
domain_name
FQDN
No
Domain Name
domain_name
domain_name_
servers
IP list
No
Name Server
NIOS 6.2
Associated GUI
Field
Associated PAPI
Method
Add this field to overwrite the address field

when you select the overwrite or merge option.
Example: TRUE
Example: [5.6.7.8,1.2.3.4]
31
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Method
routers
IP list
No
Router
match_option
String
No
ignore_dhcp_param_
request_list
Boolean
No
Ignore Optionlist
ignore-dhcp_
option_list_
request
OPTION-1
String
No
Custom DHCP
Options
options
This is an example of a DHCP option. For

information, see Data Specific Guidelines on
page 8.
Example: 255.0.0.0 implies
OPTION-XXXX-200
Option
information
No
Custom DHCP
Options
options

page 8.
vendor_class=XXXX, optioncode/number 200

Example: [2.0.0.2,1.2.3.4]
match_client

MAC_ADDRESS/CLIENT_IDENTIFIER/RESERVED
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
32
NIOS 6.2
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

Field Name
Data Type
Required
(Yes/No)
Header-IPv6HostAddress
String
Yes
view
String
No
parent
String
Yes
address_type
Enumeration
No
address
IPv6 address
Yes
_new_address
IPv6 address
No
ipv6_prefix
IPv6 prefix
No
_new_ipv6_prefix
IPv6 prefix
No
ipv6_prefix_bits
Integer
No
configure_for_dhcp
Boolean
No
match_option
String
No
duid
String
No
DUID
domain_name
FQDN
No
Domain Name
domain_name_servers
IPv6 address
list
No
Name Server
valid_lifetime
Unsigned
integer
No
Valid Lifetime
valid_lifetime
Example: 43200
preferred_lifetime
Unsigned
integer
No
Preferred
Lifetime
preferred_
lifetime
Example: 604800
OPTION-7
Integer
No
Custom DHCP
Options
override_
options

page 8.
Example: 12 name implies option space =
DHCPv6, option code/number 7
NIOS 6.2
Associated GUI
Field
Associated
PAPI Method

Example: IPv6hostaddress
DNS View
view

Example: 2000::/64
IPv6 Address
address_type
Valid values are ADDRESS, PREFIX, or BOTH. If

no value is specified, ADDRESS (default) is
used. Example: PREFIX
ipv6addr
Example: 1001::001
Add this field to overwrite the address field
option.
ipv6prefix
This field is required if address_type is

ADDRESS or BOTH.
Example: 2000:1111::
Add this field to overwrite the ipv6_prefix field
option.
DHCP check box
IPv6_prefix_
bits

ADDRESS or BOTH.
Example: 32
configure_for_
dhcp
Example: TRUE
match_client
Only DUID is allowed.

Example: DUID
duid
Example: 0001
Example: 2000::10,3000::10
33
Field Name
Data Type
OPTION-XXXX-200
Option
information
Required
(Yes/No)
Associated GUI
Field
Associated
PAPI Method
No
Custom DHCP
Options
override_
options

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
34
NIOS 6.2
NXDOMAIN and Blacklist Rulesets

Field Name
Data Type
Required
(Yes/No)
Header-Ruleset
String
Yes
name
String
Yes
_new_name
String
No
type
String
Yes
Associated GUI
Field
Associated
PAPI Method

Example: Ruleset
Name
name
Example: ruleset1
Example: ruleset1-new
type
You can use this field for NXDOMAIN rules or

blacklist rules. Valid value is NXDOMAIN or
BLACKLIST.
Example: NXDOMAIN
disabled
Boolean
No
Disable
disabled
comment
String
No
Comment
comment
ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
Example: FALSE

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
nxdomainruleset,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
blacklistruleset,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*
blacklistruleSet,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
nxdomainruleSet,NXD,NXDOMAIN,RW
NIOS 6.2
35
NXDOMAIN Rule
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Method
Header-nxdomainrule
String
Yes
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
action
String
Yes

Example: NxdomainRule
Example: foo-new
Action
action
The valid value is PASS 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
Field Name
Data Type
Required
(Yes/No)
Header-blacklistrule
String
Yes
parent
String
Yes
Name
domain_name
String
Yes
Domain Name
_new_domain_name
String
No
action
String
Yes
36
Associated GUI
Field
Associated PAPI
Method

Example: BlacklistRule
blacklist_rulesets
Example: blacklist-ruleset1
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
Example: www.bar.com
Action
blacklist_action
The valid value is PASS or REDIRECT.

Example: PASS
NIOS 6.2
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

Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Method
Header-Dns64Synthesis
Group
String
Yes
name
String
Yes
Name
name
Example: group1
prefix
IPv6 network
Yes
Prefix
prefix
Example: 64:FF9B::/96
comment
String
No
Comment
comment
clients
Access
control list
No
Name
clients
Valid values are IPv4 and IPv6 addresses and

networks only. The default value is Any.
Example: 2000::/64/Allow
mapped
Access
control list
No
Mapped IPv4
Address ->
Name
mapped
Valid values are IPv4 addresses and networks

only. The default value is Any.
Example: 10.0.0.0/8/Allow
exclude
Access
control list
No
Excluded IPv6
Address ->
Name
exclude
Valid values are IPv6 addresses and networks

only. The default is None.
Example: 2000::/Allow
disabled
Boolean
No
Disabled
disable
Example: FALSE

Example: Dns64SynthesisGroup
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
NIOS 6.2
37
IPv4 Network
Field Name
Data Type
Required
(Yes/No)
Header-Network
String
Yes
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

comment
String
No
Comment
comment
auto_create_
reversezone
Boolean
No
Automatically
create reverse
mapping zone
auto_create_
reversezone
Example: TRUE
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_
domainname
String
No
DDNS Domain
Name
ddns_
domainname
Example: ddns.corp100.com
generate_
hostname
Boolean
No
Generate Hostname
ddns_generate_
hostname
Example: TRUE
always_update_
dns
Boolean
No
DNS Zones
Associations
ddns_server_
always_updates
Example: FALSE
update_static_
leases
Boolean
No
Fixed Address
Updates
ddns_update_fixed_
address
Example: FALSE
update_dns_on_
lease_renewal
Boolean
No
Update DNS on
DHCP Lease
Renewal
override_update_
dns_on_lease_
renewal
Example: TRUE
ddns_ttl
Unsigned
integer
No
DDNS Update TTL
ddns_ttl

Example: 1200
enable_option81
Boolean
No
Option 81 Support
ddns_use_option81
Example: TRUE
deny_bootp
Boolean
No
Deny BOOTP
Requests
deny_bootp
Example: FALSE
broadcast_
address
String
No
Broadcast Address
disabled
Boolean
No
Disabled
disable
Example: FALSE
enable_ddns
Boolean
No
Enable DDNS
Updates
enable_ddns
Example: FALSE
enable_thresholds
Boolean
No
Enable DHCP
Thresholds
enable_dhcp_
thresholds
When you set this field to TRUE, you must

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.
38
Associated GUI
Field
Associated PAPI
Method
Usage and Comments

Example: Network
NIOS 6.2
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Method
enable_threshold_
email_ warnings
Boolean
No
Enable Email
Warnings
enable_email_
warnings
When you use the merge function, the

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_
snmp_ warnings
Boolean
No
Enable SNMP
Warnings
enable_snmp_
warnings

generates an error.
Example: TRUE
range_high_water
_mark
Integer
No
High Water Mark
high_water_mark
When you set enable_thresholds to TRUE,

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.
Usage and Comments
Example: 80
ignore_client_
requested_
options
Boolean
No
Ignore Optionlist
ignore_dhcp_
option_list_request
Example: TRUE
range_low_water_
mark
Integer
No
Low Water Mark
low_water_mark

the range_high_water_mark field. You
error.
Example: 10
next_server
String
No
Next Server
lease_time
Unsigned
integer
No
Lease Time
Example: 1100
enable_pxe_lease
_time
Boolean
No
Enable PXE lease

time
Example: FALSE
pxe_lease_time
Unsigned
integer
No
PXE Lease Time
pxe_lease_time
Example: 1100
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_
addresses
email
address list
No
Email Addresses
dhcp_members
Grid member
list
No
Members
routers
IP address
list
No
Routers
domain_name
FQDN
No
Domain Name
domain_name_
servers
IP address
list
No
DNS Servers
NIOS 6.2
nextserver
Example: blue.domain.com
Example:
"'admin1@infoblox.com','admin2@somewh
ere.com'"
members
Example:
"host1.infoblox.com,host2.infoblox.com"
Example: "10.0.0.1,10.0.0.100,"
Example: "10.2.3.4,11.2.3.4"
39
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Method
zone_associations
Zone list
No
OPTION-1
String
No
Custom DHCP
Options
options

information, see Data Specific Guidelines
on page 8.
OPTION-XXXX-200
Option
information
No
Custom DHCP
Options
options

on page 8.
Usage and Comments

Example: test.com/TRUE
code/number 200
EA-Site
String
No
Extensible Attribute
Site

on page 8.
EA-Users
String
No
User

ADMGRP-JoeSmith
String
No
Permissions Admin
Group/Role
permission
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
40
NIOS 6.2
IPv6 Network
Field Name
Data Type
Required
(Yes/No)
Header-IPv6Network
String
Yes
address
IPv6 address
Yes
Address
cidr
Prefix
Yes
Netmask
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
create
reverse-mapping
zone
auto_create_
reversezone
Example: TRUE
zone_associations
Zone list
No
DNS Zone
Associations
zone_
associations
Example: test.com/TRUE
dhcp_members
Grid member
list
No
Members
members
Example: host1.infoblox.com,
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
Lifetime
preferred_
lifetime
Example: 604800
recycle_leases
Boolean
No
recycle_leases
Example: FALSE
enable_ddns
Boolean
No
Enable DDNS
Updates
enable_ddns
Example: TRUE
always_update_dns
Boolean
No
FQDN Support
ddns_server_
always_updates
Example: TRUE
ddns_domain_name
String
No
DDNS Domain
Name
ddns_
domainname
Example: ddnsdomain.com
ddns_ttl
Unsigned
integer
No
DDNS Update
TTL
ddns_ttl
Example: 3600
generate_hostname
Boolean
No
Generate
Hostname
override_ddns_
generate_
hostname
Example: TRUE
update_dns_on_lease_renewal
Boolean
No
Lease Renewal
Update
override_
update_dns_
on_lease_
renewal
Example: TRUE
OPTION-7
Integer
No
Custom DHCP
Options
override_
options
This is an example of a DHCP option.

For information, see Data Specific
Example: 12 name implies option
space = DHCPv6, option
code/number 7
NIOS 6.2
Associated GUI
Field
Associated PAPI
Method

Example: IPv6Network
ipv6addr
Example: 2001::
Example: 32
41
Field Name
Data Type
OPTION-XXXX-200
Option
information
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Method
No
Custom DHCP
Options
override_
options

This is an example of a DHCP option.
For information, see Data Specific
code/number 200
EA-Site
String
No
Extensible
attribute Site
extensible_
attributes
EA-Site is an example of a
predefined extensible attribute. You
can add other predefined attributes
to the data file. For information
about data format and examples,
see Data Specific Guidelines on
page 8.
EA-Users
String
No
Extensible
attribute Users
extensible_
attributes
EA-Users is an example of a user

defined attribute. You can add other
user defined attributes to the data
file. For information about data
ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
ADMGRP-JoeSmith is an example of
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 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
42
NIOS 6.2
IPv4 Shared Network

Field Name
Data Type
Required
(Yes/No)
Header-SharedNetwork
String
Yes
name
String
Yes
_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,
network_view
String
No
Network View
network_view

is_authoritative
Boolean
No
Authoritative
authority
Example: FALSE
boot_file
String
No
Boot File
bootfile
Example: bootfile1
boot_server
String
No
Boot Server
bootserver
comment
String
No
Comment
comment
generate_hostname
Boolean
No
Generate
Hostname
ddns_generate_
hostname
Example: TRUE
always_update_dns
Boolean
No
DNS Zones
Associations
ddns_server_
always_updates
Example: FALSE
update_static_leases
Boolean
No
Fixed Address
Updates
ddns_update_
fixed_address
Example: FALSE
update_dns_on_
lease_renewal
Boolean
No
Update DNS on
DHCP Lease
Renewal
override_update_
dns_on_lease_
renewal
Example: TRUE
ddns_ttl
Integer
No
DDNS Update TTL
ddns_ttl

Example: 1200
enable_option81
Boolean
No
Option 81
Support
ddns_use_option
81
Example: TRUE
deny_bootp
Boolean
No
Deny BOOTP
Requests
deny_bootp
Example: FALSE
disabled
Boolean
No
Disable
disable
Example: FALSE
enable_ddns
Boolean
No
Enable DDNS
Updates
enable_ddns
Example: FALSE
ignore_client_
requested_ options
Boolean
No
Ignore Optionlist
ignore_dhcp_
option_list_reque
st
Example: TRUE
next_server
String
No
Next Server
nextserver
lease_time
Unsigned
integer
No
Lease Time
Example: 1100
enable_pxe_lease_
time
Boolean
No
Enable PXE lease

time
Example: FALSE
pxe_lease_time
Unsigned
integer
No
PXE Lease Time
routers
IP address
list
No
Routers
NIOS 6.2
Associated GUI
Field
Associated PAPI
Method

Example: SharedNetwork
Name
name
pxe_lease_time
Example: Site Network
Example: 1100
Example: "10.0.0.1,10.0.0.100"
43
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Method
domain_name
FQDN
No
Domain Name
domain_name
domain_name_servers
IP address
list
No
Name Server
OPTION-2
Integer
No
Custom DHCP
Options
options
Example: 50
OPTION-1
String
No
Custom DHCP
Options
options

on page 8.
OPTION-XXXX-200
Option
information
No
Extensible
Attribute Site
options

on page 8.
Example: "10.2.3.4,11.2.3.4"
code/number 200
EA-Site
String
No
Extensible
Attribute Users
extensible
attributes

page 8.
EA-Users
String
No
Permissions
Admin
Group/Role
extensible
attributes

ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
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
44
NIOS 6.2
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.
Field Name
Data Type
Required
(Yes/No)
Header-IPv6SharedNet
work
String
Yes
name
String
Yes
_new_name
String
No
networks
List
Yes
Select Network
networks
Example: 2000::/64,3000::/64
network_view
String
No
Network View
network_view

comment
String
No
Comment
comment
disabled
Boolean
No
Disabled
disable
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 Lifetime
preferred_
lifetime
Example: 604800
enable_ddns
Boolean
No
Enable DDNS
Updates
enable_ddns
Example: TRUE
always_update_dns
Boolean
No
DNS Zones
Associations
ddns_server_
always_updates
Example: TRUE
ddns_domain_name
String
No
DDNS Domain
Name
ddns_
domainname
Example: DDNSdomain
ddns_ttl
Integer
No
DDNS Update TTL
override_ddns_ttl

Example: 1200
generate_hostname
Boolean
No
Generate
Hostname
override_ddns_
generate_
hostname
Example: TRUE
update_dns_on_
lease_renewal
Boolean
No
Update DNS on
DHCP Lease
Renewal
override_update_
dns_on_lease_
renewal
Example: TRUE
NIOS 6.2
Associated GUI
Field
Associated PAPI
Method

Example: IPv6SharedNetwork
Name
name
Example: IPv6Shared01
option.
Example: FALSE
45
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Method
OPTION-7
Integer
No
Custom DHCP
Options
override_
options

on page 8.
Example: 12 name implies option space =
DHCPv6, option code/number 7
OPTION-XXXX-200
Option
information
No
Custom DHCP
Options
override_
options

on page 8.
code/number 200
EA-Site
String
No
Extensible
attribute Site
extensible_
attributes

page 8.
EA-Users
String
No
Extensible
attribute Users
extensible_
attributes

ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
46
NIOS 6.2
IPv4 DHCP Range

Field Name
Data Type
Required
(Yes/No)
Header-DhcpRange
String
Yes
start_address
IP address
Yes
_new_start_address
IP address
No
Associated GUI
Field
Associated PAPI
Object

Example: DhcpRange
Start
start_addr
Example: 10.0.0.11
Add this field to overwrite the
start_address field when you select the
overwrite or merge option.
Example: 10.0.0.55
end_address
IP address
Yes
_new_end_address
IP address
No
End
end_addr
Example: 10.0.0.22
end_address field when you select the
Example: 10.0.0.66
network_view
String
No
Network View
network_view
name
String
No
Name
name
comment
String
No
Comment
comment
is_authoritative
Boolean
No
Authoritative
authority
Example: FALSE
boot_file
String
No
Boot File
bootfile
Example: bootfile1
boot_server
String
No
Boot Server
bootserver
ddns_domainname
String
No
DDNS Domain
Name
ddns_domainname
generate_hostname
Boolean
No
Generate
Hostname
ddns_generate_
hostname
Example: TRUE
deny_all_clients
Boolean
No
deny_all_clients
Example: FALSE
deny_bootp
Boolean
No
Deny BOOTP
Requests
deny_bootp
Example: FALSE
disabled
Boolean
No
Disabled
disable
Example: FALSE
domain_name_servers
IP address list
No
Name Servers
enable_ddns
Boolean
No
Enable DDNS
Updates
enable_ddns
Example: FALSE
enable_thresholds
Boolean
No
Enable DHCP
Thresholds
enable_dhcp_
thresholds
When you set this field to TRUE, you must

enter values in the
range_high_water_mark and
range_low_water_mark fields. You
cannot leave those fields empty.
error.
enable_threshold_
email_ warnings
Boolean
No
Enable Email
Warnings
enable_email_
warnings

generates an error.
Example: TRUE
NIOS 6.2

Example: "10.2.3.4,11.2.3.4,"
47
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
enable_threshold_
snmp_ warnings
Boolean
No
Enable SNMP
Warnings
enable_snmp_
warnings
threshold_email_
addresses
email address
list
No
Email Addresses
range_high_water_
mark
Integer
No
High Water Mark

generates an error.
Example: TRUE
Example:
"'admin1@infoblox.com','admin2@somew
here.com'"
high_water_mark

the range_low_water_mark field. You
error.
Example: 80
ignore_client_
requested_ options
Boolean
No
Ignore Optionlist
ignore_dhcp_
option_list_reques
t
Example: TRUE
range_low_water_mark
Integer
No
Low Water Mark
low_water_mark

the range_high_water_mark field. You
error.
Example: 10
next_server
String
No
Next Server
lease_time
Unsigned
integer
No
Lease Time
Example: 1100
enable_pxe_lease_
time
Boolean
No
Enable PXE lease

time
Example: FALSE
pxe_lease_time
Unsigned
integer
No
PXE Lease Time
pxe_lease_time
Example: 1100
use_unknown_clients
Boolean
No
Allow/Deny
Clients: Unknown
Clients
unknown_client_
option
Example: FALSE
unknown_clients_
option
String
No
Unknown Clients
drop-down
unknown_client_
option
Example: Allow
use_known_clients
Boolean
No
Allow/Deny
Clients: Known
Clients
known_clients_
option
Example: TRUE
known_clients_option
String
No
Known Clients
drop-down
known_clients_
option
Example: Deny
recycle_leases
Boolean
No
Lease Deletion
recycle_leases

Merging data from an import preserves
the default value.
48
nextserver
NIOS 6.2
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
update_dns_on_
lease_renewal
Boolean
No
Update DNS on
DHCP Lease
Renewal
override_update_
dns_on_lease_
renewal
Example: TRUE
always_update_dns
Boolean
No
DNS Zones
Associations
always_update_
dns
Example: FALSE
exclusion_ranges
IP address
range
No
Exclusion Ranges
exclude
This field indicates the start to end

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
member
Example: member.infoblox.com
server_association_
type
Sting
No
failover_association
String
No
Served by
Failover
Association
broadcast_address
IP address
No
Broadcast
Address
Example: 10.0.0.1
routers
IP address list
No
Routers
Example: "10.0.0.1,10.0.0.100,"
domain_name
FQDN
No
Domain Name
mac_filter_rules
List of MAC
filter rules
No
Filter Type/Action
Example: "MACfiltername1/allow,
MACfiltername2/deny"
nac_filter_rules
List of NAC
Filter rules
No
Filter Type/Action
Example: "NACfiltername1/allow,
NACfiltername2/deny"
relay_agent_filter_rules
List of relay
agent filter
rules
Filter Type/Action
Example: "RAfiltername1/allow,
RAfiltername2/deny"
option_filter_rules
List of option
filter rules
Filter Type/Action
Example: "Optionfiltername1/allow,
Optionfiltername2/deny"
OPTION-2
Integer
No
Custom DHCP
Options
options

on page 8.
Example: 50
OPTION-1
String
No
Custom DHCP
Options
options

on page 8.
OPTION-XXXX-200
Option
information
No
Custom DHCP
Options
options

on page 8.
Valid values are MEMBER, NONE, and

FAILOVER
failover_assoc
domain_name
code/number 200
NIOS 6.2
49
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
EA-Site
String
No
Extensible
Attribute Site
extensible
attributes

on page 8.
EA-Users
String
No
Extensible
Attribute Users
extensible
attributes

ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
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
50
NIOS 6.2
IPv6 DHCP Range

Field Name
Data Type
Required
(Yes/No)
Header-IPv6DhcpRange
String
Yes
address_type
Enumeration
No
parent
String
No
start_address
IP address
No
_new_start_address
IP address
No
end_address
IP address
No
_new_end_address
IP address
No
ipv6_start_prefix
IPv6 address
prefix
No
_new_ipv6_start_prefix
IPv6 address
prefix
No
ipv6_end_prefix
IPv6 address
prefix
No
_new_ipv6_end_prefix
IPv6 address
prefix
No
ipb6_prefix_bits
Integer
No
network_view
String
No
name
String
comment
Associated GUI
Field
Associated PAPI
Object

Example: IPv6DhcpRange
address_type
Valid values are ADDRESS, PREFIX, and

BOTH. If no value is specified, ADDRESS
(default) is used.
Example: PREFIX
Select Network
network
This field is required when address_type

is PREFIX.
Example: 2000::/16
Address Start
start_addr

ADDRESS or BOTH.
Example: 2000::1
start_address field when you select the
Address End
end_addr

ADDRESS or BOTH.
Example: 2000::1
end_address field when you select the
Prefix Delegated
Start
ipv6_start_prefix

PREFIX or BOTH.
Example: 2000:1111::
ipv6_start_address field when you select
the overwrite or merge option.
Prefix Delegated
End
ipv6_end_prefix

PREFIX or BOTH.
Example: 2000:1111::
ipv6_end_address field when you select
ipv6_prefix_bits

PREFIX or BOTH.
Example: 32
Network View
network_view

No
Name
name
String
No
Comment
comment
Example: This is an IPv6 DHCP range.
disabled
Boolean
No
Disabled
disable
Example: FALSE
member
Grid member
No
Grid Member
member
Example: member.infoblox.com
server_association_
type
Sting
No
server_association
_type
Valid values are MEMBER and NONE. If no

value is specified, None (default) is used.
NIOS 6.2
51
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
IP address
range
No
Exclusion Ranges
exclude
This field indicates the start to end

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
recycle_leases
Boolean
No
Lease Deletion
recycle_leases

Merging data from an import preserves
the default value.
EA-Site
String
No
Extensible
Attribute Site
extensible
attributes

on page 8.
EA-Users
String
No
Extensible
Attribute Users
extensible
attributes

ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
Field Name
Data Type
exclusion_ranges
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.
Field Name
Data Type
Required
(Yes/No)
Header-FixedAddress
String
Yes
ip_address
IP address
Yes
_new_ip_address
IP address
No
network_view
String
No
Network View
network_view
name
String
No
Name
name
always_update_dns
Boolean
No
DNS Zones
Associations
always_update_
dns
Example: FALSE
boot_file
String
No
Boot File
bootfile
Example: bootfile1
boot_server
String
No
Boot Server
bootserver
prepared_zero
Boolean
No
52
Associated GUI
Field
Associated PAPI
Object

Example: FixedAddress
IP Address
ipv4addr
Example: 10.0.0.11
ip_address field when you use the
Example: FALSE
NIOS 6.2
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
comment
String
No
Comment
comment
ddns_domainname
String
No
DDNS Domain
Name
ddns_domainname
deny_bootp
Boolean
No
Deny BOOTP
Requests
deny_bootp
Example: FALSE
broadcast_address
IP address
No
Broadcast Address
Example: 10.0.0.1
routers
IP address
list
No
Routers
Example: "10.0.0.1,10.0.0.100,"
domain_name
FQDN
No
Domain Name
domain_name_
servers
IP address
list
No
Name Servers
dhcp_client_
identifier
String
No
Client Identifier
dhcp_client_
identifier
disabled
Boolean
No
Disabled
disable
enable_ddns
Boolean
No
Enable DDNS
Updates
ignore_client_
requested_ options
Boolean
No
Ignore Optionlist
circuit_id
String
remote_id
Example: "10.2.3.4,11.2.3.4,"
Example: FALSE
Example: FALSE
ignore_dhcp_
option_list_request
Example: TRUE
No
agent_circuit_id
This field is required when match_option

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

= REMOTE_ID.
Example: xyz
mac_address
MAC
address
No
Yes for
reservation
mac
This field is required if match_option =

MAC_ADDRESS, or if you are importing a
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
MAC Address
match_client

['MAC_ADDRESS','CLIENT_ID','CIRCUIT_I
D','REMOTE_ID']
next_server
String
No
Next Server
lease_time
Unsigned
integer
No
Lease Time
Example: 1100
enable_pxe_lease_
time
Boolean
No
Enable PXE lease

time
Example: FALSE
ddns_hostname
String
No
pxe_lease_time
Unsigned
integer
No
OPTION-2
Integer
OPTION-1
String
NIOS 6.2
nextserver
ddns_hostname
Example: host1.test.com
PXE Lease Time
pxe_lease_time
Example: 1100
No
Custom DHCP
Options
options

information, see Data Specific
Example: 50
No
Custom DHCP
Options
options

53
Field Name
Data Type
OPTION-XXXX-200
Option
information
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
No
Custom DHCP
Options
options

code/number 200
EA-Site
String
No
Site
extensible_
attributes

on page 8.
EA-Users
String
No
Users
extensible_
attributes

attribute this is of a List type
(enumeration list). You can add other
user defined attributes to the data file.
on page 8.
ADMGRP-JoeSmith
String
No
Permissions Admin
Group/Role
permission
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
54
NIOS 6.2
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

Field Name
Data Type
Required
(Yes/No)
Header-IPv6FixedAdd
ress
String
Yes
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

ADDRESS or BOTH.
Example: 2000::5
_new_ip_address
IP address
No
ipv6_prefix
IPv6 address
prefix
No
_new_ipv6_prefix
IPv6 address
prefix
No
ipv6_prefix_bits
Integer
No
network_view
String
No
name
String
comment
disabled
NIOS 6.2
Associated GUI
Field
Associated PAPI
Object

Example: IPv6FixedAddress
Add this field to overwrite the ip_address

merge option.
Prefix Delegated
ipv6prefix

PREFIX or BOTH.
Example: 2000:1111::
Add this field to overwrite the ipv6_prefix
merge option.
ipv6prefix_bits

PREFIX or BOTH.
Example: 32
Network View
network_view

No
Name
name
Example: IPv6FixedAddr
String
No
Comment
comment
Boolean
No
Disabled
disable
Example: FALSE
55
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
match_option
String
No
duid
String
No
DUID
domain_name
FQDN
No
Domain Name
Example: ns1.corp100.com
domain_name_
servers
IPv6 address
list
No
Name Servers
Example: 2000::10,3000::10
valid_lifetime
Unsigned
integer
No
Valid Lifetime
valid_lifename
Example: 43200
preferred_lifetime
Unsigned
integer
No
Preferred Lifename
preferred_lifetime
Example: 604800
OPTION-7
Integer
No
Custom DHCP
Options
override_
options

on page 8.
Example: 12 name implies option space
= DHCPv6, option code/number 7
OPTION-XXXX-200
Option
information
No
Custom DHCP
Options
override_
options

on page 8.
match_client
Only DUID is allowed.

Example: DUID
duid
Example: 0001
code/number 200
EA-Site
String
No
Site
extensible_
attributes

on page 8.
EA-Users
String
No
Users
extensible_
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.
ADMGRP-JoeSmith
String
No
Permissions Admin
Group/Role
permission
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
56
NIOS 6.2
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

Field Name
Data Type
Required
(Yes/No)
Header-DhcpMacFilter
String
Yes
name
String
Yes
_new_name
String
No
never_expires
Boolean
No
Never Expires
expiration_interval
Integer
No
Automatically expires
in
default_mac_address
_expiration
Example: 3624
enforce_expiration_time
Boolean
No
Enforce Expiration
Times
enforce_expiration_
times
Example: FALSE
comment
String
No
Comment
comment
EA-Site
String
No
Site

extensible attribute. You can add
other predefined attributes to the
data file. For information about data
EA-Users
String
No
Users

user defined attributes to the data
file. For information about data
ADMGRP-JoeSmith
String
No
Permissions Admin
Group/Role
permission
ADMGRP-JoeSmith is an example of
an admin permission of a specific
admin group. For information about
data format and examples, see Data
NIOS 6.2
Associated PAPI
Object

Example: DhcpMacFilter
Name
name
Example: MAC filter 1

Add this field to overwrite the name
merge option.
Example: TRUE
57
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

Field Name
Data Type
Required
(Yes/No)
Header-MacFilterAddress
String
Yes
parent
String
Yes
MAC Address
Filter
filter_name
Example: MAC filter 1
mac_address
MAC address
Yes
MAC Address
mac_address
Example: aa:bb:cc:dd:ee:ff
_new_mac_address
MAC address
No
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:
First Name
Example: John
guest_middle_name
String
No
Register as Guest:
Middle Name
Example: Doe
guest_last_name
String
No
Register as Guest:
Last Name
Example: Doe
guest_email
Email address
No
Register as Guest:
Email Address
Example: jdoe@infoblox.com
guest_phone
String
No
Register as Guest:
Phone Number
Example: 408-111-1111
guest_custom_field1
String
No
Register as Guest:
Custom Field 1
58
Associated GUI
Field
Associated PAPI
Method

Example: MacFilterAddress

mac_address field when you select the
NIOS 6.2
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Method
guest_custom_field2
String
No
Register as Guest:
Custom Field 2
guest_custom_field3
String
No
Register as Guest:
Custom Field 3
guest_custom_field4
String
No
Register as Guest:
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
comment
String
No
Comment
comment
EA-Site
String
No
Extensible
Attribute Site
extensible_
attributes

on page 8.
EA-Users
String
No
Extensible
Attribute Users
extensible_
attributes

ADMGRP-JoeSmith
String
No
Permissions
Admin
Group/Role
permission
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
NIOS 6.2
59
Option Filter
Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Method
Header-OptionFilter
String
Yes
name
String
Yes
_new_name
String
No
comment
String
No
Comment
comment
boot_file
String
No
Boot File
boot_file
Example: bootfile1
boot_server
String
No
Boot Server
boot_server
lease_time
Integer
No
Lease Time
lease_time
Example: 7200
pxe_lease_time
Unsigned
integer
No
PXE Lease Time
pxe_lease_time
Example: 1100
next_server
String
No
Next Server
next_server
option_space
String
No
Option Space
option_space
Example: Infoblox_DHCP
OPTION-2
Integer
No
Custom DHCP
Options
option_list

on page 8.
Example: 50
OPTION-1
String
No
Custom DHCP
Options
options_list

on page 8.
OPTION-XXXX-200
Option
information
Np
Extensible
Attribute Site
options_list

on page 8.

Example: OptionFilter
Name
name
Example: Option Filter 1

option.
code/number 200
EA-Site
String
No
Extensible
Attribute Site
extensible_
attributes

page 8.
EA-Users
String
No
Extensible
Attribute Users
extensible_
attributes

60
NIOS 6.2
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

Field Name
Data Type
Required
(Yes/No)
Header-OptionFileterMatchRule
String
Yes
parent
Option filter
Yes
Option Filter
Name
filter
The name of the parent option

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
comment
String
No
Comment
comment
is_substring
Boolean
No
Value is a
substring
is_substring
Example: FALSE
substring_offset
Integer
No
Substring Offset
substring_offset
Example: 2
substring_length
Unsigned
integer
No
Substring Length
substring_length
Example: Doe
NIOS 6.2
Associated GUI
Field
Associated PAPI
Object

Example: OptionFilterMatchRule

match_value field when you select
61
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
62
NIOS 6.2
Relay Agent Filter

Field Name
Data Type
Required
(Yes/No)
Header-RelayAgentFilter
String
Yes
name
String
Yes
_new_name
String
No
comment
String
No
Comment
comment
circuit_id_rule
String
No
Circuit ID: Match

Value
is_circuit_id
circuit_id
String
No
Circuit ID
circuit_id_name
remote_id_rule
String
No
Remote ID: Match

Value
is_remote_id
Example: MATCHES_VALUE
remote_id
Integer
No
Remote ID
remote_id_name
Example: 50
EA-Site
String
No
Site
extensible_
attributes

predefined attributes to the data file.
on page 8.
EA-Users
String
No
Users
extensible_
attributes

user defined attributes to the data file.
on page 8.
Associated PAPI
Object

Example: RelayAgentFilter
Name
name
Example: Relay Agent Filter 1

merge option.
Example: MATCHES_VALUE
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
NIOS 6.2
63
NAC Filter
Field Name
Data Type
Required
(Yes/No)
Header-NACFilter
String
Yes
name
String
Yes
_new_name
String
No
comment
String
No
Comment
comment
expression
Option list
No
Match the following

rule
expression
To include the option list in the Matching

the following rules table in Grid Manager,
you must enclose the expression in
brackets.
Example:
(Sophos.ComplianceState="Compliant"
AND RADIUS.ServerError="TRUE")
EA-Site
String
No
Site

on page 8.
EA-Users
String
No
Users

Associated PAPI
Object

Example: NACFilter
Name
name
Example: NAC Filter

option.
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
64
NIOS 6.2
IPv4 Option Space

Field Name
Data Type
Required
(Yes/No)
Header-OptionSpace
String
Yes
name
String
Yes
_new_name
String
No
comment
String
No
Associated PAPI
Object

Example: OptionSpace
Name
name
Example: ABC-co options

merge option.
Comment
comment
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.
NIOS 6.2
65
IPv6 Option Space

Field Name
Data Type
Required
(Yes/No)
Header-IPv6OptionS
pace
String
Yes
name
String
Yes
_new_name
String
No
comment
String
No
Comment
ipv6_enterprise_
number
String
No
Enterprise Number
Associated PAPI
Object

Example: IPv6OptionSpace
Name
name
Example: MySpace
merge option.
comment
Example: Custom option space

This is the vendors enterprise number
that is registered with IANA.
Example: 7779

Field Name
Data Type
Required
(Yes/No)
Associated GUI
Field
Associated PAPI
Object
Header-OptionDefinition
String
Yes
space
String
Yes
_new_space
String
No
name
String
Yes
_new_name
String
No
code
String
Yes
Options: Code
code
type
String
Yes
Options: Type
type

Example: OptionDefinition
Option Space
space
Example: ABC-co options

Add this field to overwrite the space field
option.
Name
name
Example: Option one

when you use the overwrite or merge
option.
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
66
NIOS 6.2
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

Field Name
Data Type
Required
(Yes/No)
Header-IPv6OptionDefin
ition
String
Yes
space
String
Yes
_new_space
String
No
name
String
Yes
_new_name
String
No
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
NIOS 6.2
Associated GUI
Field
Associated PAPI
Object

Example: IPv6OptionDefinition
Option Space
space
Example: MySpace
Add this field to overwrite the space field
option.
Name
name
Example: MyOption1
when you use the overwrite or merge
option.
67
68
NIOS 6.2

NIOS CSV Ref 6.2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NIOS CSV Ref 6.2

Uploaded by

Copyright:

Available Formats

Infoblox CSV Import Reference

Document Overview on page 4

CSV Import Reference (Rev. A)

Indicates examples of the field names.

Signifies the data in a CSV file.

Infoblox CLI Guide

CSV Import Reference (Rev. A)

CSV Import Reference (Rev. A)

CSV Import Reference (Rev. A)

Chapter 1 CSV Import Reference

Guidelines for CSV Import on page 7

Guidelines for CSV Import

Do not include blank lines in the data file

CSV Import Reference (Rev. A)

CSV Import Reference

Data Specific Guidelines

EA-IB is a user defined URL type. It can have a value of www.infoblox.com.

CSV Import Reference (Rev. A)

CSV File Format

CSV File Format

Table 1.1 CSV File Example 1

Table 1.2 CSV File Example 2

CSV Import Reference (Rev. A)

CSV Import Reference

Table 1.3 CSV File Example 3

CSV Import Reference (Rev. A)

Supported Object Types

Supported Object Types

Table 1.4 Supported DNS Object Types

Required Fields & Syntax

Authoritative DNS Zone on page 12.

AAAA Record on page 17

CNAME Record on page 18

DNAME Record on page 19

NAPTR Record on page 22

PTR Record on page 25

SRV Record on page 27

TXT Record on page 26

Host Record on page 29

IPv4 Host Address

IPv4 Host Address on page 31

IPv6 Host Address

IPv6 Host Address on page 33

NXDOMAIN and Blacklist Rulesets on page 35

NXDOMAIN Rule on page 36

Blacklist Rule on page 36

DNS64 Synthesis Group

DNS64 Synthesis Group on page 37

Table 1.5 Supported DHCP Object Types

Required Fields & Syntax

IPv4 Network on page 38

IPv6 Network on page 41

IPv4 Shared Network

IPv4 Shared Network on page 43

IPv6 Shared Network

IPv6 Shared Network on page 45

IPv4 DHCP Range

IPv4 DHCP Range on page 47

CSV Import Reference (Rev. A)

CSV Import Reference

DHCP Object Type

Required Fields & Syntax

IPv6 DHCP Range