# BlueCat

> Connect a BlueCat 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 BlueCat.

## Connection details

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

| Field | Description |
| --- | --- |
| **Name** | A name for this connection. |
| **IP address** | The address or hostname of the BlueCat server. |
| **Port** | Defaults to 443. |
| **Account username** | An account authorized to run commands on the BlueCat 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/). |

## A server will not get an address

The domain comes from the **DNS Domain** value on the CMP network. When it is set, CMP registers the host as `<hostname>.<domain>` in BlueCat, so the domain must be one BlueCat knows. If the two do not agree, BlueCat refuses to register the host against the IP, and provisioning fails. If the network has no **DNS Domain**, CMP reserves the IP address without creating a 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 the DNS Domain on a CMP network.