<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Resolving the balancer DNS name on Access point if it is the same for internal and external connections in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Resolving-the-balancer-DNS-name-on-Access-point-if-it-is-the/m-p/2273339#M60812</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, my configuration is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;F5 External vdi.mycomp.com 234.000.14.23 NAT to 192.168.1.3&lt;/P&gt;&lt;P&gt;AP1 ap1.mycomp.com 234.000.14.24 NAT to 192.168.1.4&lt;/P&gt;&lt;P&gt;AP2 ap2.mycomp.com 234.000.14.25 NAT to 192.168.1.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;F5 Internal vdi.mycomp.com as CNAME for vdi.dom.mycomp.com 172.20.12.3&lt;/P&gt;&lt;P&gt;CON1 con01.dom.mycomp.com 172.20.12.4&lt;/P&gt;&lt;P&gt;CON2 con02.dom.mycomp.com 172.20.12.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you can see, for our users it is enough to put the only one server name (vdi.mycomp.com) in their client and whatever they locate they can connect.&lt;/P&gt;&lt;P&gt;But, the question is - which IP address should be resolved on AP by using "nslookup vdi.mycomp.com" (172.20.12.3 or 192.168.1.3 or 234.000.14.23)?&lt;/P&gt;&lt;P&gt;Now, our DNS is always answers the IP 172.20.12.3 for vdi.mycomp.com if we put it on AP or on CON.&lt;/P&gt;&lt;P&gt;Everything seems works normal, but I don't think it is correct configurations. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help with it&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Apr 2017 20:33:09 GMT</pubDate>
    <dc:creator>ALEX_TSM</dc:creator>
    <dc:date>2017-04-11T20:33:09Z</dc:date>
    <item>
      <title>Resolving the balancer DNS name on Access point if it is the same for internal and external connections</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Resolving-the-balancer-DNS-name-on-Access-point-if-it-is-the/m-p/2273339#M60812</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, my configuration is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;F5 External vdi.mycomp.com 234.000.14.23 NAT to 192.168.1.3&lt;/P&gt;&lt;P&gt;AP1 ap1.mycomp.com 234.000.14.24 NAT to 192.168.1.4&lt;/P&gt;&lt;P&gt;AP2 ap2.mycomp.com 234.000.14.25 NAT to 192.168.1.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;F5 Internal vdi.mycomp.com as CNAME for vdi.dom.mycomp.com 172.20.12.3&lt;/P&gt;&lt;P&gt;CON1 con01.dom.mycomp.com 172.20.12.4&lt;/P&gt;&lt;P&gt;CON2 con02.dom.mycomp.com 172.20.12.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you can see, for our users it is enough to put the only one server name (vdi.mycomp.com) in their client and whatever they locate they can connect.&lt;/P&gt;&lt;P&gt;But, the question is - which IP address should be resolved on AP by using "nslookup vdi.mycomp.com" (172.20.12.3 or 192.168.1.3 or 234.000.14.23)?&lt;/P&gt;&lt;P&gt;Now, our DNS is always answers the IP 172.20.12.3 for vdi.mycomp.com if we put it on AP or on CON.&lt;/P&gt;&lt;P&gt;Everything seems works normal, but I don't think it is correct configurations. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help with it&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Apr 2017 20:33:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Resolving-the-balancer-DNS-name-on-Access-point-if-it-is-the/m-p/2273339#M60812</guid>
      <dc:creator>ALEX_TSM</dc:creator>
      <dc:date>2017-04-11T20:33:09Z</dc:date>
    </item>
    <item>
      <title>Re: Resolving the balancer DNS name on Access point if it is the same for internal and external connections</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Resolving-the-balancer-DNS-name-on-Access-point-if-it-is-the/m-p/2273340#M60813</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are 2 options here. UAG (AP) normally uses an internal DNS server to resolve names. You specify the DNS server with the "dns" keyword in the UAG PowerShell .ini file. See&lt;A href="https://communities.vmware.com/docs/DOC-30835"&gt;Using PowerShell to Deploy VMware Unified Access Gateway (formerly known as Access Point)&lt;/A&gt;​.&amp;nbsp; You would expect UAG to resolve the names of your Connection Server hostnames to the 172 addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If UAG doesn't have access to DNS you can either add hosts file entries (also in the .ini file) or configure proxyDestinationUrl in the [Horizon] section to reference an IP address (e.g. &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;172.20.12.3 instead of &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;vdi.mycomp.com&lt;/SPAN&gt;). Either way, proxyDestinationUrl is used on UAG to establish a connection to Connection Server(s).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;The "split DNS" you've set up is good because internal users can connect to Connection Server(s) and external users can connect to UAG(s) with the same URL hostnames.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Apr 2017 21:23:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Resolving-the-balancer-DNS-name-on-Access-point-if-it-is-the/m-p/2273340#M60813</guid>
      <dc:creator>markbenson</dc:creator>
      <dc:date>2017-04-11T21:23:15Z</dc:date>
    </item>
  </channel>
</rss>

