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.
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"
https://docs.vmware.com/en/vRealize-Automation/8.11/Using-and-Managing-Cloud-Assembly/GUID-6BF1F830-FB58-40B7-BBE8-06658C3D33FC.html