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 Record → Update
AI-generatedSummary
Update a DNS record in Infoblox Universal DDI using its resource ID and supplied field values. Mapped fields and the optional JSON body are combined, with JSON body values taking precedence, then sent in a PATCH request.
Inputs
- Resource ID (required) — Infoblox ID of the DNS record to update.
- Fields (required) — Set fields through the mapper, or use its supported automatic mapping from incoming data.
- JSON Body — Optional JSON object merged over mapped fields. Use it for extra fields or when no API schema is available; duplicate keys override mapped values.
- Query Parameters — Optional additional query parameters for the request.
Output shape
A single record, or a list of records if the API response is an array.
The operation sends a PATCH request to the DNS record endpoint. Object responses are returned as one n8n item; array responses become multiple items. With Continue On Fail enabled, errors are returned as an item containing an error message.