Actions182
- Address Block Actions
- Audit Log Actions
- Auth Profile: LDAP Actions
- Auth Profile: OIDC Actions
- Auth Profile: SAML Actions
- CDC Application Actions
- CDC Destination: HTTP Actions
- CDC Destination: Splunk Actions
- CDC Destination: Syslog Actions
- CDC Host Actions
- Custom API Request Actions
- DFP Service Actions
- DHCP Fingerprint Actions
- DHCP Lease Actions
- DNS Event Actions
- DNS Record Actions
- DNS Zone Actions
- Endpoint Device Group Actions
- Endpoint Roaming Device Actions
- Endpoint VPN Profile Actions
- Fixed Address Actions
- Global Search Actions
- Identity: Compartment Actions
- Identity: Group Actions
- Identity: User Actions
- Infrastructure Host Actions
- Infrastructure Service Actions
- IP Address Actions
- IP Space Actions
- IPAM Range Actions
- Location Actions
- Lookalike Domain Actions
- Lookalike Target Actions
- NIOS Custom API Request Actions
- NIOS WAPI Object Actions
- NTP Service Config Actions
- Redirect: Custom Redirect Actions
- Service Log Actions
- SOC Insight Actions
- Subnet Actions
- TD Access Code Actions
- TD Application Filter Actions
- TD Category Filter Actions
- TD Internal Domain List Actions
- TD Named List Actions
- TD Scheduled Report Actions
- TIDE Batch Actions
- TIDE Dossier Lookup Actions
- TIDE Threat Actions
DNS Zone → Update
AI-generatedSummary
Updates an existing Infoblox Universal DDI authoritative DNS zone by ID, sending a PATCH to /api/ddi/v1/dns/auth_zone/{id} with the fields you supply.
Inputs
- resourceId (required) — ID of the DNS zone to update. It is URL-encoded and appended to the auth_zone endpoint.
- dataFields (required) — Resource mapper for the zone fields to change. Columns are loaded from the Infoblox DnsConfig API schema, and read-only fields, id and _ref are skipped. Auto-map from input data is supported.
- jsonBody — Extra request body as JSON. It is merged over the mapped fields, so its keys win on conflict. Use it for fields missing from the schema. Defaults to {}.
- queryParameters — Extra name/value query-string parameters added to the request, for example _fields.
Output shape
One output item per input item, containing the JSON response from the Infoblox API. This is normally the updated zone object.
A non-object response is wrapped as { result: value }. If Continue On Fail is enabled, a failed item returns { error: message } instead of stopping the run. Requires Infoblox CSP API credentials.
Examples
Example 1: Change the comment on an existing zone
Resource: DNS Zone, Operation: Update, Resource ID: the zone ID (for example dns/auth_zone/abc123), JSON Body: {"comment":"Managed by n8n"}
Example 2: Update zone fields from upstream data
Resource ID set by expression from a previous node's id. Fields mapped through the resource mapper, for example the comment field and other writable zone fields.