The virtual network that you use for Horizon Cloud pod must have the ability to resolve both internal machine names and external names. During the pod deployment process, the deployer securely downloads the pod software into your Microsoft Azure environment from external addresses in the Horizon Cloud control plane. The ability to resolve internal virtual machine (VM) names is needed for the pod's Horizon Cloud Active Directory domain-join operations with the VMs that get deployed in your Microsoft Azure environment.
In a Microsoft Azure subscription, internal network connectivity is not set up by default. For production environments, you would typically configure the virtual network's DNS settings to point at a valid DNS server that can resolve external names as well as work in Microsoft Azure for your corporate machines. For example, you might want to deploy a Microsoft Windows Server 2016 virtual machine in that virtual network to act as the DNS server, and configure the virtual network's DNS setting to point to the IP address of that deployed DNS server.
For proof-of-concept environments, if your organization's privacy and security policies allow, you can configure the internal DNS to delegate to an external public DNS for external name resolution. Some organizations and ISPs provide public recursive name servers to use for such purposes, such as OpenDNS at 126.96.36.199 or Google Public DNS at 188.8.131.52. For a sample list of public recursive name servers, see the Wikipedia article Public recursive name server.
Ensure your Microsoft Azure region has the virtual network that you plan to use for your pod. See Configure the Required Virtual Network in Microsoft Azure.
Ensure that the DNS server you specify in these steps can reach and resolve the specific external names required for a successful pod deployment. For details, see DNS, Ports, Protocols Requirements for a Horizon Cloud Pod in Microsoft Azure.
- From the Microsoft Azure portal's left navigation bar, click (Virtual networks) and then click the virtual network that you are going to use for your pod.
- Display the virtual network's DNS server settings by clicking DNS servers.
- Using the Custom option, add the address of the DNS server you want to use for name resolution and click Save.
What to do next
Ensure the pod deployer's access requirements for DNS, ports, and protocols are met. See DNS, Ports, Protocols Requirements for a Horizon Cloud Pod in Microsoft Azure.