Unexpected Behavior in DNS Suffix with Infoblox Integration.

Products

• VMware Aria Suite

Issue/Introduction

• In this Knowledge Base (KB) article, we will delve into a situation where the desired DNS suffix is requested in the action run log, but the resulting suffix differs from expectations. We will examine the evidence presented in the action run log to shed light on this issue.

Symptoms:

• The issue at hand pertains to a discrepancy between the DNS suffix requested and the DNS suffix received during an action run. While the action run log indicates a specific desired DNS suffix, the final result provides a different suffix.

 

We can observe the below in the action run :
"Infoblox.IPAM.Network.dnssuffix": "abcd.abc.com"

hostname.abcd.abc.com is the desired FQDN. hostname.abc.com is what we get.

Cause

• The property 'Infoblox.IPAM.Network.dnsSuffix' provides the functionality to replace the existing domain DHCP option within an Infoblox network with a new value. This capability proves particularly useful in cases where the Infoblox network lacks a configured domain DHCP option or when there is a need to overwrite the existing domain DHCP option. The default value for this property is 'null' (an empty string)."

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

 

Example :

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

 

We must ensure that the characters in the cloud template precisely match the casing as specified either in the document or as outlined above, specifically referring to 'Infoblox.IPAM.Network.dnsSuffix"

 

Resolution

• Rectifying the property in the cloud template should serve as a solution to address the problem, resulting in the acquisition of the desired DNS suffix.

For instance, please ensure that 'Infoblox.IPAM.Network.dnssuffix' is appropriately matched with 'Infoblox.IPAM.Network.dnsSuffix' to achieve the intended configuration.

 

 

 

Additional Information

https://docs.vmware.com/en/vRealize-Automation/8.11/Using-and-Managing-Cloud-Assembly/GUID-6BF1F830-FB58-40B7-BBE8-06658C3D33FC.html