
InfoBlox DDI
Network Management- Overview
- Setup
- Data & mappings
- Operations & API
- Changelog
The Infoblox DDI Connector integrates with the Infoblox NIOS DDI (DNS, DHCP, IPAM) platform through its WAPI (Web API) interface. It discovers and synchronizes IP address management data — specifically host records and networks — into Brinqa, modeling them as assets. In addition to the two first-class models (Host and Network), the connector dynamically discovers every other WAPI object type exposed by the server schema and can sync it as a generic object, including any user-defined extensible attributes.
The connector negotiates the WAPI version at runtime by reading the server's supported versions and using the highest available (falling back to 2.2). Extensible attributes are only synced when the negotiated version is 2.2 or higher.
Data retrieved from Infoblox DDI
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Host | Yes | Host |
| Network | Yes | Ip Range |
| Dynamic Objects | Yes | Dynamic Objects |
Model relationships
For detailed steps on how to view the data retrieved from Infoblox DDI in the Brinqa Platform, see How to view your data.
Connection settings
When setting up a data integration, select Infoblox DDI from the Connector dropdown and provide the following:
| Setting | Required | Default | Description |
|---|---|---|---|
| Infoblox server | No | — | Infoblox server base URL |
| Username | No | — | Infoblox username |
| Password | No | — | Infoblox password |
| SSL / TLS | No | — | Skip certificate verification |
Authentication
The connector authenticates to the Infoblox NIOS WAPI using HTTP Basic authentication. The Infoblox server URL, username, and password are supplied as configuration. The username and password are encoded into the Authorization: Basic header on every request; there is no separate token-exchange step.
A connection test is performed against the schema root endpoint.
Endpoint
| Method | URL |
|---|---|
| GET | {Infoblox server}/wapi/v{version}/?_schema |
Request Headers
| Header | Value |
|---|---|
Authorization | Basic base64(username:password) |
Accept | application/json |
Sample Request
GET /wapi/v2.2/?_schema HTTP/1.1
Host: infoblox.example.com
Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=
Accept: application/json
Sample Response
{
"requested_version": "2.2",
"supported_objects": [
"network",
"record:host",
"range",
"ipv6network"
],
"supported_versions": [
"1.0",
"1.1",
"2.2"
]
}
Response Fields
| Field | Description |
|---|---|
requested_version | The WAPI version that served the request. |
supported_objects | List of WAPI object types exposed by the server schema. The connector iterates these (excluding ignored utility objects) to build dynamic object classes. |
supported_versions | List of WAPI versions the appliance supports. The connector selects the highest version. |
The same Basic Authorization header is sent on every subsequent schema, extensible-attribute, and search request.
How to obtain Infoblox DDI credentials
InfoBlox DDI permissions
For the InfoBlox DDI connector to access the InfoBlox API and retrieve data, the account used in the integration configuration must have the appropriate permissions and API access.
To create the necessary role and user group with the required permissions, follow these steps:
-
Log in to your organization's InfoBlox DDI portal as an administrator.
-
Navigate to Administration > Administrators > Roles and click + to create a new role.
-
Enter a Name for the new role and click Next.
-
On the Extensible Attributes page, click Next, then click Save & Add Permissions.
-
On the Permissions page, click + and add the following
Read-Onlypermissions to the new role:All HostsAll IPv4 Host AddressesAll IPv4 NetworksAll IPv6 Host AddressesAll IPv6 NetworksAll Network ViewsPort Control
-
Click Save & Close.
-
Navigate to Administration > Administrators > Groups and click + to create a new group.
-
Enter a Name for the new group and click Next.
-
Under Allowed Interfaces, select API, then click +.
-
Click Custom Roles, select the custom role you created in the earlier steps, and then click Save & Close.
-
Navigate to Administration > Administrators > Users.
-
Select the user you want to add to the group, and then click Edit.
This should be the user whose credentials are entered in the integration configuration.
-
In the Available User Groups table, select the group you created in the earlier steps.
-
Click Save & Close.
Note: If you do not have permissions to create a new role and group, contact your InfoBlox DDI administrator. For additional information, see the InfoBlox DDI documentation on Creating Roles, Creating User Groups, and Editing Users.
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes:
Host
| Source Field Name | SDM Attribute |
|---|---|
(constant) | CATEGORIES |
record:host._ref | UID |
record:host.dns_name | DNS_NAMES |
record:host.dns_name | PUBLIC_DNS_NAMES |
record:host.dns_name | PRIVATE_DNS_NAMES |
record:host.extattrs.* | *{ext attr} |
record:host.name | NAME |
Network
| Source Field Name | SDM Attribute |
|---|---|
(constant) | CATEGORIES |
network._ref | UID |
network.comment | DESCRIPTION |
network.email_list | EMAILS |
network.extattrs.* | *{ext attr} |
network.network | NAME |
Dynamic Objects
| Source Field Name | SDM Attribute |
|---|---|
{object}._ref | UID |
{object}.extattrs.* | *{ext attr} |
{object}.{field} | {field} |
Operations & API
Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).
Host
Operation options
| Option | Type | Default | Description |
|---|---|---|---|
QUERY | Optional WAPI filter expression, e.g. host_name:~=localdomain&platform=VNIOS. Each field=value pair is sent as a search query parameter. | — |
Delta sync
The connector README does not document sync behavior for this object.
API
- Type: REST endpoint · Endpoint:
GET /wapi/v{version}/record:host?_paging=1&_return_as_object=1&_max_results=1000
Network
Operation options
| Option | Type | Default | Description |
|---|---|---|---|
QUERY | Optional WAPI filter expression, e.g. network:~=localdomain&platform=VNIOS. Each field=value pair is sent as a search query parameter. | — | |
ATTRS_TO_GET | Subset of fields/extensible attributes to retrieve, e.g. network,comment,email_list,*Country,disable,netmask,*network,*First Found. | — |
Delta sync
The connector README does not document sync behavior for this object.
API
- Type: REST endpoint · Endpoint:
GET /wapi/v{version}/network?_paging=1&_return_as_object=1&_max_results=1000
Dynamic Objects
Operation options
This object does not support any operation options.
Delta sync
The connector README does not document sync behavior for this object.
API
- Type: REST endpoint · Endpoint:
GET /wapi/v{version}/{object}?_paging=1&_return_as_object=1&_max_results=1000
Changelog
The Infoblox DDI connector has undergone the following changes:
| Version | Description | Migration Steps |
|---|---|---|
| 3.0.0 | Overview The Infoblox DDI connector integrates with Infoblox NIOS (DNS, DHCP, and IP Address Management) to synchronize network infrastructure assets such as host records and IP networks. It dynamically discovers the objects exposed by the Infoblox WAPI schema, so the available models reflect the object types supported by the connected appliance, and it incorporates any extensible attributes defined on those objects. Category: Network Management Models | N/A |