<?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 Re: DNS issues with internationalized domain names in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/DNS-issues-with-internationalized-domain-names/m-p/2900503#M174785</link>
    <description>&lt;P&gt;When I used Bridged networking, the ping from a Windows 10 VM works.&lt;/P&gt;&lt;P&gt;C:\&amp;gt;ping coronaprøver.dk&lt;/P&gt;&lt;P&gt;Pinging xn--coronaprver-ngb.dk [185.127.96.91] with 32 bytes of data:&lt;BR /&gt;Reply from 185.127.96.91: bytes=32 time=259ms TTL=234&lt;BR /&gt;Reply from 185.127.96.91: bytes=32 time=207ms TTL=234&lt;BR /&gt;Reply from 185.127.96.91: bytes=32 time=271ms TTL=234&lt;BR /&gt;Reply from 185.127.96.91: bytes=32 time=264ms TTL=234&lt;/P&gt;&lt;P&gt;But when I switch to NAT, it fails as well.&lt;/P&gt;&lt;P&gt;So try switching to Bridged networking as it won't be using the software-based NAT but uses whatever hardware router/switch that you have connected with the host machine.&lt;/P&gt;</description>
    <pubDate>Thu, 24 Mar 2022 23:10:48 GMT</pubDate>
    <dc:creator>bluefirestorm</dc:creator>
    <dc:date>2022-03-24T23:10:48Z</dc:date>
    <item>
      <title>DNS issues with internationalized domain names</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/DNS-issues-with-internationalized-domain-names/m-p/2900447#M174779</link>
      <description>&lt;P&gt;I am experiencing an issue where my VM (Windows 10 Pro) fails to resolve international domain names (with special characters).&lt;/P&gt;&lt;P&gt;It simply fails to resolve the host.&lt;/P&gt;&lt;P&gt;I have created a new, clean VM for testing this, and it fails the same way as my regular VM. Furthermore, I created a VirtualBox VM from the exact same ISO, and that works perfectly.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="vmware1.png" style="width: 999px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/94384i81A56BA39218741E/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="vmware1.png" alt="vmware1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As you can see, the VM in VirtualBox correctly translates the domain name to the puny-code version. The VMWare VM, however, fails to do this.&lt;/P&gt;&lt;P&gt;I have also tried on a Windows PC as well as Windows Server, and they both produce the same output as you see in VirtualBox.&lt;/P&gt;&lt;P&gt;Why does this happen? And what can I do to fix it?&lt;/P&gt;</description>
      <pubDate>Thu, 24 Mar 2022 17:33:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/DNS-issues-with-internationalized-domain-names/m-p/2900447#M174779</guid>
      <dc:creator>eso1</dc:creator>
      <dc:date>2022-03-24T17:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: DNS issues with internationalized domain names</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/DNS-issues-with-internationalized-domain-names/m-p/2900503#M174785</link>
      <description>&lt;P&gt;When I used Bridged networking, the ping from a Windows 10 VM works.&lt;/P&gt;&lt;P&gt;C:\&amp;gt;ping coronaprøver.dk&lt;/P&gt;&lt;P&gt;Pinging xn--coronaprver-ngb.dk [185.127.96.91] with 32 bytes of data:&lt;BR /&gt;Reply from 185.127.96.91: bytes=32 time=259ms TTL=234&lt;BR /&gt;Reply from 185.127.96.91: bytes=32 time=207ms TTL=234&lt;BR /&gt;Reply from 185.127.96.91: bytes=32 time=271ms TTL=234&lt;BR /&gt;Reply from 185.127.96.91: bytes=32 time=264ms TTL=234&lt;/P&gt;&lt;P&gt;But when I switch to NAT, it fails as well.&lt;/P&gt;&lt;P&gt;So try switching to Bridged networking as it won't be using the software-based NAT but uses whatever hardware router/switch that you have connected with the host machine.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Mar 2022 23:10:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/DNS-issues-with-internationalized-domain-names/m-p/2900503#M174785</guid>
      <dc:creator>bluefirestorm</dc:creator>
      <dc:date>2022-03-24T23:10:48Z</dc:date>
    </item>
  </channel>
</rss>

