Unexpected Behavior in DNS Suffix with Infoblox Integration in Aria Automation 8.x

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

This article addresses an issue where the requested DNS suffix (e.g., subdomain.example.com) does not match the final applied suffix (e.g., example.com) in VMware Aria Automation 8.x when using Infoblox integration.

Symptoms

• The action run log shows a desired suffix, such as hostname.subdomain.example.com.
• The resulting suffix is different, e.g., hostname.example.com.

Environment

Aria Automation 8.x

Cause

• The property Infoblox.IPAM.Network.dnsSuffix replaces or specifies the DHCP option domain in an Infoblox network.
• By default, this property is null (empty string).
• It only applies if Infoblox.IPAM.Network.enableDns is set to True.
• Proper case matching is required (use dnsSuffix, not dnssuffix).

Infoblox.IPAM.Network.dnsSuffix is only applicable if Infoblox.IPAM.Network.enableDns is set to True.

 

Example Cloud Template:

formatVersion: 1

inputs: {}

resources:

Cloud_Machine_1:

type: Cloud.Machine

properties:

Infoblox.IPAM.Network.dnsSuffix: test.local

Infoblox.IPAM.Network0.hostnameNicSuffix: -nic1

Infoblox.IPAM.Network1.hostnameNicSuffix: -nic2

image: ubuntu

flavor: small

networks:

- network: '${resource.Cloud_Network_1.id}'

deviceIndex: 0

- network: '${resource.Cloud_Network_2.id}'

deviceIndex: 1

Cloud_Network_1:

type: Cloud.Network

properties:

networkType: existing

Cloud_Network_2:

type: Cloud.Network

properties:

networkType: existing

 

Note: Ensure the property name exactly matches Infoblox.IPAM.Network.dnsSuffix.

 

 

Resolution

Correct the property in the cloud template to match the desired DNS suffix. For example, if you intended to set Infoblox.IPAM.Network.dnssuffix, change it to Infoblox.IPAM.Network.dnsSuffix to achieve the intended configuration.

Additional Information

For more details, refer to the Using and Managing Cloud Assembly documentation.