Infoblox DNS record creation fails when network range source is set to Assembler in VMware Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When deploying a virtual machine (VM) in VMware Aria Automation using the Infoblox IPAM plugin, you experience the following:

• The VM deploys successfully and receives an IP address.
• The Infoblox portal does not update with the assigned IP or domain name.
• DNS entries are not automatically created in Infoblox.
• Stale DNS entries remain in the Infoblox UI after a VM is deleted from Aria Automation.
• nslookup on the VM domain name or IP address fails to resolve.

Environment

• VMware Aria Automation 8.x
• VMware Cloud Foundation (VCF) Automation 9.x
• Infoblox IPAM Plugin

Cause

This issue occurs when the Network Range source in the network profile is set to Assembler instead of External. The "Assembler" setting causes Aria Automation to manage the IP assignment internally, which bypasses the lifecycle hooks required by the Infoblox plugin to trigger DNS registration and cleanup actions.

Resolution

To resolve this issue, revert the network range configuration to use the external IPAM source:

1. Log in to VMware Aria Automation Assembler.
2. Navigate to Infrastructure > Resources > Networks.
3. Click on IP Ranges.
4. Locate and select the affected IP range.
5. Change the Source setting from Assembler to External.
6. Select the appropriate IPAM integration (Infoblox) from the dropdown menu.
7. Save the configuration.
8. Verify the fix by deploying a test VM and confirming the record appears in the Infoblox Grid Manager.

Additional Information

• If you continue to experience issues after verifying the range source, ensure that the Infoblox plugin is updated to the latest version. See Download Broadcom Products.
• For further assistance, refer to Contact Broadcom Support.
• Subscribe to this article to be updated on any future changes or fix status by following the steps in KB 275360.