Axonius Documentation
  1. Enforcement Action Library
  2. Enrich Asset Data

Infoblox - Update Device with DNS Records

The Infoblox - Update Device with DNS Records enforcement enriches devices with DNS records that resolve to their IP addresses for:

  • Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

When accessing an enforcement action using the API, you must use the backend form of field names.

Use the Syntax Helper to find the correct name. In the enforcement action, enable Configure Dynamic Values and select Syntax Helper.

📘

Note

Required Fields

These fields must be configured to run the Enforcement Action.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values (optional) - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
  • Use stored credentials from the Infoblox DDI adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.

    • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

📘

Note

This enforcement action enriches devices with Infoblox DNS records (A Records and Host Records) that resolve to the device's IP addresses. The DNS records are written to the device's Infoblox adapter record as "Linked DNS Records" and can be queried using the field specific_data.data.dns_records.

Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Additional Fields

These fields are optional.

💡

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

  • Infoblox Domain - The domain or IP address of your Infoblox server.
  • API version - The WAPI version to use. Supported versions: 2.2, 2.5, 2.10.3, 2.10.5, 2.12, 2.13.
  • User Name - Username for authentication with Infoblox WAPI.
  • Password - Password for authentication with Infoblox WAPI.

  • Verify SSL (Optional) (default: enabled) - Selects whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings. This setting is enabled by default on all new adapter settings. If you need to disable SSL verification, make sure you disable this setting.)

  • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

  • HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

  • HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.

  • Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses the Infoblox WAPI (Web API). The action queries the Domains & URLs collection for Infoblox DNS records and writes the matched records to the device's Infoblox adapter data.

Note: The official WAPI documentation is available on your Infoblox server at https://<grid_IP>/wapidoc.

Required Ports

Axonius must be able to communicate via the following ports:

  • TCP port 443 (HTTPS)

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

The user account must have permissions to:

  • Read DNS records - Query A Records and Host Records from Infoblox
  • Read device information - Access device IP address information

Note: The exact permission names should be confirmed with your Infoblox administrator, as the publicly available API documentation does not include detailed permission information.

To learn more about Enforcement Actions, see Enforcement Actions.

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

VersionSupportedNotes
WAPI 2.2Yes
WAPI 2.5Yes
WAPI 2.10.3Yes
WAPI 2.10.5Yes
WAPI 2.12Yes
WAPI 2.13Yes

For more details about other enforcement actions available, see Action Library.

Updated about 1 hour ago

Did this page help you?