Infoblox NIOS
Manage DNS-01 records on an Infoblox NIOS Grid through its WAPI REST API.
Prerequisites
- The Grid Manager reachable from CertAutoPilot over HTTPS (port 443).
- The zones you issue certificates for are authoritative zones on the Grid in the view you configure.
- An admin account for CertAutoPilot (below). Its password must not expire unattended: an expired password stops issuance.
Create a least-privilege API user
In Grid Manager (Administration → Administrators):
- Admin group — create one (for example
certautopilot) and set its access method to API only. It needs no superuser rights. - Permissions — on each zone CertAutoPilot writes to, give the group Read/Write for the TXT resource record type. Nothing else is needed for issuance: no zone-wide, view or Grid permission. The optional record check of Test on the credential page also writes and removes a CNAME; grant Read/Write for CNAME too if you use it.
- Admin — create the user in that group.
The same through the WAPI, as a superuser (replace the host, the zone and the password):
GM=https://gm.example.com/wapi/v2.7
# 1. API-only admin group
curl -u admin -X POST "$GM/admingroup" -H 'Content-Type: application/json' \
-d '{"name":"certautopilot","access_method":["API"]}'
# 2. Write permission for TXT records on the zone (repeat per zone; use the
# zone's own view if it is not "default")
ZONE=$(curl -s -u admin "$GM/zone_auth?fqdn=example.com&view=default" | jq -r '.[0]._ref')
curl -u admin -X POST "$GM/permission" -H 'Content-Type: application/json' \
-d "{\"group\":\"certautopilot\",\"object\":\"$ZONE\",\"permission\":\"WRITE\",\"resource_type\":\"TXT\"}"
# 3. The user
curl -u admin -X POST "$GM/adminuser" -H 'Content-Type: application/json' \
-d '{"name":"certautopilot-api","password":"<strong password>","admin_groups":["certautopilot"]}'
Two Grid settings affect this user:
- Approval workflows. If changes made by the user's group need approval, Infoblox parks every change as a pending task and nothing is written. CertAutoPilot detects this, withdraws the pending task and fails with "the change is waiting for approval in Infoblox". Exempt the CertAutoPilot group from the approval workflow.
- Account lockout. CertAutoPilot never retries a refused login within a call, but an issuance with a wrong password still makes several refused logins: the challenge attempt, the issuance job's own retries, and the follow-up cleanup job's retries. Fix a changed password promptly (the credential Test shows it at once) so these do not add up to the Grid's lockout threshold. A locked account is refused exactly like a wrong password; the error says so.
Add the credential
- Settings → DNS Credentials → New → Infoblox NIOS.
- Grid Manager URL:
https://gm.example.com(no path — CertAutoPilot adds/wapi/v<version>/). - Username + Password of the API user.
- DNS View — the view the zones live in; empty means
default. - CA Certificate — the CA that issued the Grid Manager's HTTPS certificate. A Grid Manager often serves a self-signed certificate: paste that certificate itself.
- Test → Save. Without a domain, Test signs in and checks the view; with a domain it also creates and deletes a temporary TXT record.
The URL, WAPI version and CA certificate are checked when you save; a mistake is refused right away instead of failing at the next issuance.
Config fields
| Field | Required | Purpose |
|---|---|---|
url | yes | Grid Manager address, https://host[:port], no path. |
username | yes | The API user. |
password | yes | Its password. Never shown again after saving. |
view | no | DNS view every record is written to and searched in. Default default. |
wapi_version | no | API only — the form does not ask. Empty (the default) = automatic: CertAutoPilot asks the Grid which WAPI versions it serves and uses 2.7 when listed, otherwise the highest listed. Set it only to pin a version. |
ca_cert | no | PEM of the CA (or the self-signed certificate) of the Grid Manager. |
tls_skip_verify | no | Accept any certificate. Anyone on the network path could then read the API password — use ca_cert instead. |
Editing the credential
Fields left empty on the edit form keep their stored value. To move back to the default view, type default; a stored CA Certificate can be replaced but not removed — to stop pinning one, create a new credential. The same holds for a wapi_version set through the API: it can be changed, not cleared back to automatic.
How records are written
- One view only. Every write, search and delete names the configured view, so a record with the same name in another view (split-horizon) is never touched. Use a separate credential per view.
- DNS-01: the challenge
TXTis added next to any other value at the same name (an apex and its wildcard share one name), with a 60-second TTL and the commentcertautopilot, and is deleted by name and value afterwards — also when the cleanup runs as a separate job. - Changes are served by the Grid at once; no service restart is involved.
Propagation
The record is published by the Grid members serving the zone. For a zone that exists only in an internal view, public resolvers cannot see it: set DNS Resolvers (Settings → General) to servers that answer from that view, or allow partial propagation. Public certificate authorities can only validate names resolvable on the internet.
Troubleshooting
Authentication refused
Wrong username or password, a locked account, or an expired password — Infoblox answers all three the same way. Check the user under Administration → Administrators (status and password expiry).
"The API user lacks permission"
The group has no Write permission for TXT in that zone. Add it on the zone.
"The name is not in any zone of view …"
The domain is not under an authoritative zone of the configured view — wrong view, or the zone lives in another view.
"View … does not exist"
The configured view name is wrong (names are case-sensitive). Leave it empty for default.
"The change is waiting for approval in Infoblox"
An approval workflow covers the API user's group. Exempt the group; CertAutoPilot has already withdrawn the pending task.
Certificate errors
The Grid Manager's certificate is not trusted: paste its CA (or the self-signed certificate) into CA Certificate.
See also
Video tutorial
Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →