# Infoblox

> Connect an Infoblox server to Cloud Management Platform (CMP) to manage addresses for your networks

---

Site [llms.txt](/llms.txt)

---

The setup workflow is common to all IPAM integrations: connect, import the networks, map them to your resource handler networks, and then enable orchestration. See [IP address management (IPAM)](/docs/cmp/configure/infrastructure/networks/ipam/) for those steps. This page covers what is specific to Infoblox.

## Connection details

In **Admin** > **IP Management**, select **Add**, then choose **Infoblox**.

| Field | Description |
| --- | --- |
| **Name** | A name for this connection. |
| **IP address** | The address or hostname of the Infoblox server. |
| **Port** | Defaults to 443. |
| **Account username** | An account authorized to run commands on the Infoblox server. |
| **Password** | The password for that account. It is stored securely. If the password vault feature is enabled, this field offers **Locally Stored** or **Vault Managed**. Select **Vault Managed** to read the secret from a configured vault provider. See [Use password vaults](/docs/cmp/configure/access-and-security/security/use-password-vaults/). |

## Network result limit

CMP imports every network from Infoblox, however many there are, by requesting them in pages through Infoblox WAPI v2.0.

If your Infoblox does not support WAPI v2.0, CMP requests all networks at once instead, up to **Maximum # of Network Results**, which defaults to 5,000. If importing fails with "Result set too large", raise the limit:

1. On the Infoblox connection's **Overview** tab, select the pencil icon next to **Maximum # of Network Results**.
1. Enter a number higher than the total number of networks in your Infoblox instance.
1. Select **Save**.

## Orchestration

The Infoblox sample hook validates a hostname, allocates an IP address to it, sets up DHCP for the host, restarts the Infoblox DHCP service, and then deletes the host to release the IP address. Enable it on the **Orchestration** tab, and edit it if required.

## A server will not get an address

CMP must have a domain name when it deploys a server to an Infoblox-managed network, and that domain must be one Infoblox knows. The domain can come from a parameter on the order or from the **DNS Domain** value on the CMP network. If the two do not agree, Infoblox refuses to register the host, which is the first step in IP allocation, and provisioning fails.

For the same reason, the CMP network also needs a gateway and a netmask defined.

## Legacy plugin actions

Before the network mapping described above existed, Infoblox was driven by a set of sample plugin actions, still available under **Admin** > **Orchestration Actions**, named **Infoblox 00** through **Infoblox 04**. They pre-allocate an address, register DNS and DHCP entries, reconcile the server record, and delete the host record on decommission.

<div class="alert alert-warning" role="alert">


If you map networks to an IPAM as described above, you do not need these actions and should leave them disabled. Use them only to keep an older configuration working.
</div>


They depend on two parameters you would have to create yourself at **Admin** > **Parameters**: `host_fqdn`, the fully qualified domain name registered in Infoblox DNS, and `infoblox_ip`, the address Infoblox assigned to the host record.

## Related

- [IP address management (IPAM)](/docs/cmp/configure/infrastructure/networks/ipam/): The setup workflow shared by every IPAM integration.
- [Import and manage existing networks](/docs/cmp/configure/infrastructure/networks/import-existing/): Set a network's DNS Domain, gateway, and netmask.
- [Orchestration actions](/docs/cmp/use/orchestration/actions/orchestration-actions/): Where the legacy Infoblox actions live.