In addition to allowing network communication to those DNS addresses, the DNS configuration on your VNet must resolve the names as described in this article. The purpose of each DNS address is stated in the following tables. For the pod deployer to work, you must configure your firewalls to allow the network access to those addresses. Horizon Cloud pod requires network access to specific DNS addresses over your Microsoft Azure VNets.

Some Overarching Key Points About these required DNS names At times, this page uses the phrases DNS name and host name interchangeably. The pod deployment process requires that the deployed instances have network communication over the deployment's selected VNet to the host names (DNS names) described in this page.Īfter the pod is successfully deployed in your subscription, various day-to-day service operations require network access to specific host names, as does the pod update process for updating the pod's software when new software is made available. As described in the software networking industry, systems use Domain Name System (DNS) to resolve host names to their IP addresses for communication purposes.

The reason why this page includes the phrase DNS name along with the phrase host name is because DNS is a networking standard for resolving host names for communication between those host names to occur.Ī host name is a unique name assigned to a machine instance on a given network. Brief Points about Host Names, DNS Host Names, and Relationship to the Horizon Cloud on Microsoft Azure Deployment For successful end-to-end use of the service's features, you must ensure the host names described in this documentation page are resolvable and reachable from the management and tenant subnets using the specific ports and protocols identified in this page.

Vmware horizon infrastructure