# DNS > Configure and use the OneFuse DNS module with VMware vRealize Automation 7.6 --- Site [llms.txt](/llms.txt) --- To learn more about this OneFuse module, refer to [DNS](/docs/onefuse/configure/modules/dns/). ## Prerequisites 1. Configure OneFuse [Property Set(s)](/docs/onefuse/templating/property-sets/) and OneFuse Module Policies. 1. Run [OneFuse Configuration](/docs/onefuse/consume/vmware-aria-automation/vrealize-automation-76/installation-and-setup/#run-the-onefuse-configuration-workflow) per vRA Tenant. 1. Review the [OneFuse Modules](/docs/onefuse/consume/vmware-aria-automation/vrealize-automation-76/modules/) overview for vRealize Automation 7.6. 1. Create a new **vRA Blueprint** (if none exist) or determine which existing Blueprint(s) will utilize this OneFuse Module. - Resource: [Designing Machine Blueprints](https://docs.vmware.com/en/vRealize-Automation/7.6/com.vmware.vra.prepare.use.doc/GUID-62A92480-A122-4C89-A4E3-F8F6EC26C19E.html#GUID-62A92480-A122-4C89-A4E3-F8F6EC26C19E) ## Configure the Blueprint 1. **Know the name of the OneFuse Endpoint** created via [OneFuse Configuration](/docs/onefuse/consume/vmware-aria-automation/vrealize-automation-76/installation-and-setup/#run-the-onefuse-configuration-workflow). 1. **Determine _which_ OneFuse DNS Policies to run** for this Blueprint. 1. **Update the Blueprint** to add in the necessary vRA Properties to invoke a OneFuse DNS Policy. 1. **Deploy the Blueprint** to provision a vRA Deployment and register DNS Record(s). 1. **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** 1. Select the **Design** tab from the top menu bar 1. Select the **Blueprints** tab from the left menu 1. **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:** | Property name format | Property value format | | --- | --- | | `OneFuse_DnsPolicy_Nic<#>` | `::` | - Replace `<#>` with a number from `0` to `9`, one for each NIC. Default is `0`. ```yaml # Execute OneFuse DNS Policy # -- Property Value # is onefuse # 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. | Property name format | Property value format | | --- | --- | | `OneFuse_DnsPolicy_AdditionalTrigger` | `true` | | `OneFuse_DnsPolicy_Additional_` | `::` | - `OneFuse_DnsPolicy_AdditionalTrigger` is the required trigger property to enable DNS for additional NICs. - Replace `` 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 `` 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. | Property name format | Property value format | | --- | --- | | `OneFuse_IP_Additional_` | `` | - Match the `` here with the value set for `` in `OneFuse_DnsPolicy_Additional_`. - Templatable. Additional IP Address to register into DNS. **Example vRA Custom Properties** (in `key: value` pair format) ```yaml # -- Property Name # is xyz # -- Property Value # is onefuse # is prod # 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.** | Property | Value format | | --- | --- | | `OneFuse_Tracking_Id` | A GUID (globally unique identifier) that links OneFuse Policy Executions and the resulting Managed Objects together for a given resource on a deployment. The first OneFuse Module Policy execution will populate this vRA property and it will be passed into other OneFuse Modules automatically. Learn more about OneFuse [Tracking ID](/docs/onefuse/concepts/tracking-id/). | **Purpose: Reference a specific NIC's values to get hostname, IP address, etc.** | Property format | Example | | --- | --- | | `OneFuse_VmNic<#>.` | See examples below | Replace `<#>` with a number from `0` to `9`, one for each NIC. Replace `` 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: | Method | Description | | --- | --- | | Basic | Add a Custom Property to the vSphere machine on the blueprint canvas, or to the blueprint layer itself. | | Advanced 1 | Add a Custom Property to an existing or new vRA [Property Group](https://docs.vmware.com/en/vRealize-Automation/7.6/com.vmware.vra.prepare.use.doc/GUID-73D5DB94-3B5D-410A-8E9C-CF42D4ADF6F0.html). | | Advanced 2 | Add a Custom Property to a more global level - such as vCenter Endpoint (to run on all deployments) and/or a Reservation (to run on all deployments using that reservation), etc. | Learn more: [Understanding Custom Properties Precedence](https://docs.vmware.com/en/vRealize-Automation/7.6/com.vmware.vra.prepare.use.doc/GUID-F45F332E-1003-45BC-BC05-0EA2FDE1B31F.html) ### Compiled example vRA custom properties Review example below of vRA Custom Properties (in `key: value` pair format) for this OneFuse Module. ```yaml # Execute OneFuse DNS Policy # -- Property Value # is onefuse # 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. | Property name | Property value | | --- | --- | | `OneFuse_DNS_Nic<#>` | _JSON string of OneFuse DNS Managed Object_ | | `OneFuse_DNS_Additional` | _JSON string of OneFuse DNS Managed Object_ | - `<#>` is a number `0`-`9`. - `` 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 | EBS Execution | Subscription State | EBS Priority | EBS Name | | --- | --- | --- | --- | | **Provision** | | | | | BuildingPre | Early | 1300 | OneFuse_Provision_DNS | | **Deprovision** | | | | | MachineDisposingPost | - | 1300 | OneFuse_De-Provision_DNS | ## Troubleshooting Troubleshoot in vRealize Orchestrator. 1. Log in to **vRealize Orchestrator**. 1. Turn on [Verbose Logging](/docs/onefuse/consume/vmware-aria-automation/vrealize-automation-76/modules/#troubleshooting-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 1. Optionally, [configure timeouts for EBS](/docs/onefuse/consume/vmware-aria-automation/vrealize-automation-76/modules/event-broker-subscriptions/#configure-ebs-timeouts) and/or [Configure timeouts for OneFuse modules](/docs/onefuse/consume/vmware-aria-automation/vrealize-automation-76/installation-and-setup/#configure-timeouts-for-onefuse-modules). ### Troubleshooting common errors - **Error:** `message": "Policy action job '' 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](#add-in-necessary-vra-property) section for an example on the expected format. **Additional resources:** - Review [Troubleshooting in OneFuse](/docs/onefuse/getting-started/troubleshooting/) - Review [VMware troubleshooting resources](/docs/onefuse/consume/vmware-aria-automation/vrealize-automation-76/getting-started/#troubleshooting)