As an administrator, after you deploy your Horizon Edge Gateway and Unified Access Gateway instances, you can then create DNS records that match the FQDNs on the Unified Access Gateway instances.
Note: Perform this task after you deploy the Horizon Edge Gateway and Unified Access Gateway instances. For related information, see Add and Deploy a Microsoft Azure Edge and Add and Deploy an Amazon Workspaces Core Edge.
If you have more than one Unified Access Gateway cluster, configure the DNS server for all non-peered VNets.
Configuring the DNS server for all non-peered VNets also applies when you create additional pool groups and are required to specify a subnet.
Considerations for Administrators and End Users
The DNS address that you configure for the UAGs per these instructions is used during brokering, but is not used by the end user. The end user connection flow in Horizon Cloud does not use this UAG URL except in background. Configuring this UAG URL is required for the solution to work, but an end user will never enter this URL into a client. For the end user to connect, they need to use either the common connect URL (cloud.omnissahorizon.com) or you can configure a custom client URL for them (custom subdomain or a fully customized URL). Note that the certificate for a custom client URL would need to be a different certificate than the one used for the UAG.
To learn more about how end users connect, see topics at Configuring the Remote Experience for Users.
To learn more about configuring a custom connection URL, see the Configure Custom Client Access URLs in the Horizon Universal Console section of Configuring Client Settings.
Prerequisites
Obtain the following IP addresses and FQDNs using the Horizon Universal Console. For example, select Capacity, click the name of the Horizon Edge Gateway instance you want to configure, and note the corresponding IP addresses and FQDNs as follows.
In the Unified Access Gateway section, obtain the load balancer IP addresses and the FQDN associated with the Unified Access Gateway instance. The list includes labels for the load balancer type or types you configured when you deployed the Horizon Edge Gateway instance. If you configured both an internal and external load balancer, the corresponding load-balancer related labels appear in the Unified Access Gateway section.
| Label | Description |
|---|---|
| Load Balancer IP | Public (external) load balancer IP address |
| Private Load Balancer IP | Internal load balancer IP address |
| FQDN | This FQDN label appears only if you solely configure internal access or solely configure external access, but not both. Moreover, this FQDN can be used for either internal or external load balancer IP addresses. |
| Internal FQDN | This Internal FQDN label only appears if you configure both internal and external access. This FQDN can only be used with a private load balancer address. |
| External FQDN | This External FQDN label only appears if you configure both internal and external access. This FQDN can only be used with a public load balancer address. |
Procedure
-
For Unified Access Gateway, perform the appropriate step that follows, depending on your load-balancer configuration:
-
If you selected External access over the internet
Create a DNS record and use the FQDN to point to the public IP address of the external load balancer in the Unified Access Gateway configuration.
-
If you selected Internal and external access
In your internal DNS, map the Unified Access Gateway Internal FQDN to the private IP address of the internal load balancer.
Also, in your external DNS, map the Unified Access Gateway External FQDN to the public IP address of the external load balancer.
-
-
Verify any updates that you make.
Questa pagina è stata utile?