eso1
Contributor
Contributor
‎03-24-2022 10:32 AM

DNS issues with internationalized domain names

I am experiencing an issue where my VM (Windows 10 Pro) fails to resolve international domain names (with special characters).

It simply fails to resolve the host.

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.

vmware1.png

 

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.

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.

Why does this happen? And what can I do to fix it?

Labels (2)
Labels
Reply
0 Kudos
bluefirestorm
Champion
Champion
‎03-24-2022 04:10 PM

When I used Bridged networking, the ping from a Windows 10 VM works.

C:\>ping coronaprøver.dk

Pinging xn--coronaprver-ngb.dk [185.127.96.91] with 32 bytes of data:
Reply from 185.127.96.91: bytes=32 time=259ms TTL=234
Reply from 185.127.96.91: bytes=32 time=207ms TTL=234
Reply from 185.127.96.91: bytes=32 time=271ms TTL=234
Reply from 185.127.96.91: bytes=32 time=264ms TTL=234

But when I switch to NAT, it fails as well.

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.

Reply
0 Kudos