DNS

To learn more about this OneFuse module, refer to DNS.

Prerequisites

1. Configure OneFuse Property Set(s) and OneFuse Module Policies.
2. Run OneFuse Configuration per vRA Tenant.
3. Review the OneFuse Modules overview for vRealize Automation 7.6.
4. Create a new vRA Blueprint (if none exist) or determine which existing Blueprint(s) will utilize this OneFuse Module.
   • Resource: Designing Machine Blueprints

Configure the Blueprint

1. Know the name of the OneFuse Endpoint created via OneFuse Configuration.
2. Determine which OneFuse DNS Policies to run for this Blueprint.
3. Update the Blueprint to add in the necessary vRA Properties to invoke a OneFuse DNS Policy.
4. Deploy the Blueprint to provision a vRA Deployment and register DNS Record(s).
5. Destroy the vRA Deployment to remove the DNS Record(s) for the destroyed resource(s).

Update the Blueprint

1. Log in to the vRA Tenant
2. Select the Design tab from the top menu bar
3. Select the Blueprints tab from the left menu
4. Edit the Blueprint and perform the below:

Add in necessary vRA Property

The following vRA Property needs to be added Blueprint’s Properties > Custom Properties section under the Resource(s) of interest.

Call a DNS Policy for a specific NIC:

• Replace <#> with a number from 0 to 9, one for each NIC. Default is 0.

# Execute OneFuse DNS Policy

# -- Property Value
# <OneFuse Endpoint Name>  is onefuse
# <DNS Policy Name> is prod

OneFuse_DnsPolicy_Nic0: onefuse:prod

Optional. DNS registration for additional IPs:

Support for registering in DNS for multiple IP Addresses on a single interface. The DNS Records are reserved and stored in both OneFuse and vRA Machine Properties for future reference in vRA lifecycles.

• OneFuse_DnsPolicy_AdditionalTrigger is the required trigger property to enable DNS for additional NICs.
• Replace <niclabel> with a value that is appended to the hostname.
• When listing multiple DNS Suffixes, comma separate the values without any spaces.

Name behavior:

• Without additional Naming Property: Default behavior of the <niclabel> is to get appended to the hostname after a hyphen (-). To override this behavior, modify the field Hostname Override on the OneFuse DNS Policy.
• With additional Naming Property: If an Additional Naming Policy is defined that matches this value, the name generated from the Naming Policy will be used.

Optional. IP address not using OneFuse IPAM module.

Use the following optional vRA Property that will be used in the event IP addresses are getting obtained not using OneFuse IPAM and the user wants to register those IP addresses in DNS.

• Match the <niclabel> here with the value set for <niclabel> in OneFuse_DnsPolicy_Additional_.
• Templatable. Additional IP Address to register into DNS.

Example vRA Custom Properties (in key: value pair format)

# -- Property Name
# <niclabel> is xyz

# -- Property Value
# <OneFuse Endpoint Name>  is onefuse
# <OneFuse DNS Policy Name> is prod
# <DNS Suffix(es)> is example.com,example2.com

# Example
OneFuse_DnsPolicy_AdditionalTrigger: true
OneFuse_DnsPolicy_Additional_xyz: onefuse:prod:example.com

# Example not using OneFuse IPAM for registering additional IP
OneFuse_IP_Additional_xyz: 10.11.11.11

# Example Output assuming the hostname is 'server12'
# > server12-xyz.example.com

Additional helpful vRA properties

Purpose: Relate OneFuse Policy executions from different OneFuse Modules together with a Tracking ID.

Purpose: Reference a specific NIC’s values to get hostname, IP address, etc.

Replace <#> with a number from 0 to 9, one for each NIC.

Replace <value> with an appropriate key: dnsSuffix, fqdn, gateway, hostname, ipAddress, macAddress, netmask, network, subnet, target

Examples:

• OneFuse_VmNic0.dnsSuffix
• OneFuse_VmNic0.fqdn
• OneFuse_VmNic0.hostname
• OneFuse_VmNic0.ipAddress
• OneFuse_VmNic0.target: when DNS Suffix is provided, will be the FQDN; otherwise, will be the hostname (without domain).

Custom property placement methods

Influence Custom Properties for Resources using different methods:

Learn more: Understanding Custom Properties Precedence

Compiled example vRA custom properties

Review example below of vRA Custom Properties (in key: value pair format) for this OneFuse Module.

# Execute OneFuse DNS Policy

# -- Property Value
# <OneFuse Endpoint Name>  is onefuse
# <DNS Policy Name> is prod

OneFuse_DnsPolicy_Nic0: onefuse:prod

Provision

Deploy a Blueprint with OneFuse DNS Policies configured. DNS Record(s) will register in the desired DNS Provider.

Outputs

The following vRA Properties will exist on the Deployment.

• <#> is a number 0-9.
• <niclabel> is the user-specified value (if configured to register additional IPs).

Deprovision

Destroy an existing deployment with OneFuse DNS Policies configured. The DNS Record(s) will be removed from the desired DNS Provider.

vRA EBS

Troubleshooting

Troubleshoot in vRealize Orchestrator.

1. Log in to vRealize Orchestrator.
2. Turn on Verbose Logging and try again to see additional log messages in vRO Workflows:
   • Select Library > Workflows from the left menu
   • Go to: OneFuse > DNS > vRA7 to find corresponding workflow runs and view logs
   • Optionally, run the workflows in the Manual folder to manually test
3. Optionally, configure timeouts for EBS and/or Configure timeouts for OneFuse modules.

Troubleshooting common errors

• Error: message": "Policy action job '<GUID>' failed: 'NoneType' object has no attribute 'has_failures'; details: None"
  • The most likely cause for this error is when DNS Suffix(es) were not provided for the vRA Property Value.
  • Refer to the Add in necessary vRA Property section for an example on the expected format.

Additional resources:

• Review Troubleshooting in OneFuse
• Review VMware troubleshooting resources