{"id":47556,"date":"2021-02-16T09:00:27","date_gmt":"2021-02-16T08:00:27","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=47556"},"modified":"2021-02-16T09:18:23","modified_gmt":"2021-02-16T08:18:23","slug":"vmware-uag-dns-resolution-issue","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vmware-uag-dns-resolution-issue\/","title":{"rendered":"VMware UAG DNS resolution issue"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-47595 size-large\" title=\"vmware-uag-dns-resolution-issue-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2021\/02\/vmware-uag-dns-resolution-issue-01-600x201.jpg\" alt=\"vmware-uag-dns-resolution-issue-01\" width=\"600\" height=\"201\" \/><\/p>\n<p>Once the <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-horizon-7-deploy-unified-access-gateway\/\">Unified Access Gateway<\/a> (UAG) has been deployed and configured, the VMware UAG DNS is <strong>not able to name resolve<\/strong> the Connection Servers if the <strong>FQDN includes the .local<\/strong> domain.<\/p>\n<p>Despite the <strong>correct DNS and Search suffix<\/strong> settings configured, once the appliance is rebooted after the deployment the <strong>Horizon Destination Server<\/strong> (Connection Server) is unreacheable from the <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-uag-two-factor-authentication-configuration\/\">UAG appliance<\/a>. This problem occurs when the FQDN of your Connetion Server is a <strong>.local domain<\/strong>\u00a0(for example <em>w16-cs01.nolabnoparty.local<\/em>).<!--more--><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-47597 size-large\" title=\"vmware-uag-dns-resolution-issue-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2021\/02\/vmware-uag-dns-resolution-issue-02-600x401.jpg\" alt=\"vmware-uag-dns-resolution-issue-02\" width=\"600\" height=\"401\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>VMware UAG DNS fix<\/h2>\n<p>To fix this issue, there two possible workaround:<\/p>\n<ul>\n<li>the use of the <strong>IP Address<\/strong> instead of FQDN<\/li>\n<li>modify an entry in the <strong>resolved.conf<\/strong> file in the UAG appliance<\/li>\n<\/ul>\n<h4>Use the IP Address<\/h4>\n<p>An easy solution to allow the <a href=\"https:\/\/docs.vmware.com\/en\/Unified-Access-Gateway\/index.html\" target=\"_blank\" rel=\"noopener noreferrer\">Unified Access Gateway<\/a> appliance to reach the Connection Servers can be achieved by entering the <strong>IP Address instead of the FQDN<\/strong> in the <strong>Connection Server URL<\/strong> field.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-47599 size-full\" title=\"vmware-uag-dns-resolution-issue-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2021\/02\/vmware-uag-dns-resolution-issue-03.jpg\" alt=\"vmware-uag-dns-resolution-issue-03\" width=\"600\" height=\"383\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Edit the \/etc\/systemd\/resolved.conf file<\/h4>\n<p>If you want to use the FQDN instead, you have to edit the <em>\/etc\/systemd\/resolved.conf<\/em> file in the UAG appliance.<\/p>\n<p>Using a tool like PuTTY, SSH the UAG by entering the <strong>root credentials<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-47601 size-large\" title=\"vmware-uag-dns-resolution-issue-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2021\/02\/vmware-uag-dns-resolution-issue-04-600x133.jpg\" alt=\"vmware-uag-dns-resolution-issue-04\" width=\"600\" height=\"133\" \/><\/p>\n<p>Edit the file <em>\/etc\/systemd\/resolved.conf<\/em> with the <strong>vi command<\/strong>.<\/p>\n<p><span style=\"color: #0000ff;\"># vi \/etc\/systemd\/resolved.conf<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-47603 size-large\" title=\"vmware-uag-dns-resolution-issue-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2021\/02\/vmware-uag-dns-resolution-issue-05-600x140.jpg\" alt=\"vmware-uag-dns-resolution-issue-05\" width=\"600\" height=\"140\" \/><\/p>\n<p>Uncomment (remove the <strong>#<\/strong>) the <strong>Domains<\/strong> line and specify your <strong>DNS Search Domain<\/strong> (in the example <em>nolabnoparty.local<\/em>). When done save the file with the <strong>:wq command<\/strong>.<\/p>\n<p><span style=\"color: #0000ff;\">Domains=nolabnoparty.local<\/span><br \/>\n<span style=\"color: #0000ff;\">:wq<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-47605 size-large\" title=\"vmware-uag-dns-resolution-issue-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2021\/02\/vmware-uag-dns-resolution-issue-06-600x355.jpg\" alt=\"vmware-uag-dns-resolution-issue-06\" width=\"600\" height=\"355\" \/><\/p>\n<p>Now <strong>Reboot<\/strong> the appliance to apply the changes.<\/p>\n<p><span style=\"color: #0000ff;\"># reboot<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-47607 size-large\" title=\"vmware-uag-dns-resolution-issue-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2021\/02\/vmware-uag-dns-resolution-issue-07-600x145.jpg\" alt=\"vmware-uag-dns-resolution-issue-07\" width=\"600\" height=\"145\" \/><\/p>\n<p>When the appliance has booted, login to the UAG appliance and check the <strong>Connection Server connectivity<\/strong>. This time the Connection Server is reachable since the DNS name is resolved with no issues and all <strong>components are marked as green<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-47609 size-large\" title=\"vmware-uag-dns-resolution-issue-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2021\/02\/vmware-uag-dns-resolution-issue-08-600x400.jpg\" alt=\"vmware-uag-dns-resolution-issue-08\" width=\"600\" height=\"400\" \/><\/p>\n<p>Once the Connetion Server is reacheable from the Unified Access Gateway, remote users can connect the corporate <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-horizon-2006-upgrade-from-version-7-x\/\">Horizon infrastructure<\/a>.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Once the Unified Access Gateway (UAG) has been deployed and configured, the VMware UAG DNS is not able to name resolve the Connection Servers if the FQDN includes the .local domain. Despite the correct DNS and Search suffix settings configured, once the appliance is rebooted after the deployment the Horizon Destination Server (Connection Server) is unreacheable from the UAG appliance. This problem occurs when the FQDN of your Connetion Server is a .local domain\u00a0(for example w16-cs01.nolabnoparty.local).<\/p>\n","protected":false},"author":3,"featured_media":47595,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[1025,903],"tags":[617,2293,2294,2250],"class_list":["post-47556","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-horizon-en","category-vmware-en","tag-dns-en","tag-domain-en","tag-fqdn-en","tag-uag","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/47556","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=47556"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/47556\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/47595"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=47556"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=47556"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=47556"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}