automation-suite
2022.4
false
UiPath logo, featuring letters U and I in white

Automation Suite installation guide

Last updated Mar 17, 2025

Step 4: Configuring the DNS

Tip:

The previous step is Step 3: Configuring Azure SQL.

For production deployments: Configuring the DNS

For production deployments, DNS configuration is required. Follow the steps in Configuring the DNS to configure DNS using the provider specific to your environment.

For test or evaluation purposes, Creating a Private DNS zone in Azure can be used as a workaround. See the following section for detailed steps.

For test or evaluation deployments: Creating a private DNS zone

This is a workaround for testing purposes. For production, please follow the DNS configuration guide specific to your environment.

Make sure to configure the host entries in the client machine after the DNS zone is created. This is a requirement for any type of deployment.

Creating a private DNS zone

  1. Search for Private DNS Zone in the search bar.


  2. Select Create.


  3. Create a private DNS zone in same Resource Group:
    • For single-node evaluation: the name of the Private DNS Zone should be the DNS name of the VM:

    • For multi-node HA-ready production: the name of the Private DNS Zone should be the DNS name of the Load Balancer.



  4. Select Review and Create.
  5. Then select Create.
  6. Once the Private DNS Zone is created, select Go to resource.


Adding a record set for all subdomains

  1. Select Record Set.


  2. Enter * in the Name field.
  3. The IP address of the record set should be the VM’s IP address (in the case of single-node evaluation) or the load balancer’s IP address (in the case of multi-node HA-ready production).


  4. Then select OK.

Adding a record set for the root domain

  1. Add a A Record for @ , which will include root, and redirect the traffic to the cluster.
  2. Go to Record Set.
  3. Set the IP address to be the VM’s IP address (in the case of single-node evaluation) or the load balancer’s IP address (in the case of multi-node HA-ready production).


  4. All the VMs should already be under one Virtual Network.

Adding a virtual network link to the private DNS zone

  1. Go to Virtual network Links under settings.


  2. Select Add.


  3. Create a new link name, and specify the Virtual network that the VMs are under.


  4. To find the virtual network link, see the following under the VM homepage:


  5. Wait until the link is created and appears as follows:


Configuring a client machine to access the cluster

Once you configure the DNS, you need to add the host entries to the client machines.

Note:

This is mandatory to perform for all deployments, both evaluation/test and production.

Adding the /etc/hosts host entry is only needed in the client machines, not the cluster node.
Windows
  1. Run the following commands from the Elevated PowerShell (Run as Administrator), to add a host entry in the \etc\hosts file.
    Tip:
    • Replace 10.10.10.10 with the IP Address of the VM (in the case of single-node evaluation) or the IP Address of the Load Balancer (in the case of multi-node HA-ready production).
    • Replace dns-123.eastus.cloudapp.azure.com with the FQDN of the cluster (DNS name of the VM for single-node evaluation and the FQDN of the Load Balancer for multi-node HA-ready production).
    • There should be a `n (backtick n) before the IP address.
    Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    dns-123.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    alm.dns-123.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    objectstore.dns-123.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    registry.dns-123.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    monitoring.dns-123.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    insights.dns-123.eastus.cloudapp.azure.com" -ForceAdd-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    dns-123.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    alm.dns-123.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    objectstore.dns-123.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    registry.dns-123.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    monitoring.dns-123.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windir\System32\drivers\etc\hosts -Value "`n10.10.10.10    insights.dns-123.eastus.cloudapp.azure.com" -Force
  2. Verify that the entries are added at the bottom of the \etc\hosts file.
    Get-Content -Path $env:windir\System32\drivers\etc\hostsGet-Content -Path $env:windir\System32\drivers\etc\hosts
MacOS or Linux
  1. Run the following commands from terminal. This is to add a host entry in the /etc/hosts file.
    Tip:
    • Replace 10.10.10.10 with the IP Address of the VM (in the case single-node evaluation) or the IP Address of the Load Balancer (in the case of multi-node HA-ready production).
    • Replace dns-123.eastus.cloudapp.azure.com with the FQDN of the cluster (DNS name of the VM for single-node evaluation and the FQDN of the Load Balancer for multi-node HA-ready production). 
    sudo bash -c "echo \"10.10.10.10    dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
sudo bash -c "echo \"10.10.10.10    alm.dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
sudo bash -c "echo \"10.10.10.10    objectstore.dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
sudo bash -c "echo \"10.10.10.10    registry.dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
sudo bash -c "echo \"10.10.10.10    monitoring.dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
sudo bash -c "echo \"10.10.10.10    insights.dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"sudo bash -c "echo \"10.10.10.10    dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
sudo bash -c "echo \"10.10.10.10    alm.dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
sudo bash -c "echo \"10.10.10.10    objectstore.dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
sudo bash -c "echo \"10.10.10.10    registry.dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
sudo bash -c "echo \"10.10.10.10    monitoring.dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
sudo bash -c "echo \"10.10.10.10    insights.dns-123.eastus.cloudapp.azure.com\" >> /etc/hosts"
  2. Verify that the entries are added at the bottom of the /etc/hosts file.
    cat /etc/hostscat /etc/hosts

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.