DNS error in Linux when trying to reach client.wvd.microsoft.com

ataboo 25 Reputation points
2023-05-18T16:28:20.41+00:00

When I try to navigate to client.wvd.microsoft.com in both Firefox and Chrome on Ubuntu, I get an NS_ERROR_UNKNOWN_HOST error and it shows the error page as if I don't have an internet connection.

In-browser AVD worked fine with the same setup until this week.  It's not intermittent, it's consistent.  When I boot the same machine to Windows, it works fine in Firefox.

Is anyone else running into this?

The only thing I can think is if an Ubuntu update broke something on the OS that's blocking this now.  Or Microsoft changed something that is blocking me on Linux.

Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,362 questions
0 comments
Accepted answer
  1. Stephan Fischer 85 Reputation points
    2023-05-24T06:58:39.01+00:00

    Hi, I had the same problem on LinuxMint. The reason is the "systemd-resolved". If he looks for "client.wvd.microsoft.com" he get more than 9 CNAMES and this throws an error on linux.

    The workaround is to add the IP and Name to your /etc/hosts until the problem is solved on linux site.

    2 people found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sedat SALMAN 13,080 Reputation points
    2023-05-19T07:00:12.5833333+00:00

    The error NS_ERROR_UNKNOWN_HOST = the domain you are trying to reach cannot be resolved by the DNS server your system is using

    • You can test the DNS lookup from your Ubuntu system to see what's happening. Use the dig command like this: dig client.wvd.microsoft.com. If the domain cannot be resolved, it might indicate a problem with the DNS server you are using.
    • The issue might be related to a corrupted DNS cache. On Ubuntu, DNS cache is not enabled by default, but if you have a caching service like dnsmasq or systemd-resolved, you can try clearing it. For systemd-resolved, you can use the command sudo systemd-resolve --flush-caches.
    • You could try changing the DNS server on your Ubuntu system to a different one, such as Google's DNS servers (8.8.8.8 and 8.8.4.4) or Cloudflare's (1.1.1.1 and 1.0.0.1). To do this, edit your /etc/resolv.conf file or set the DNS servers in your Network Manager settings.
    • Check if any firewall rules might be blocking the connection. Use sudo ufw status to check the firewall status and rules.
    0 comments