Looks like this is already logged as issue #7657 -
https://github.com/microsoft/WSL/issues/7658
** Bug watch added: github.com/microsoft/WSL/issues #7658
https://github.com/microsoft/WSL/issues/7658
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Further investigation indicates that this looks to be something weird about the
WSL2 resolver implementation.
Replacing the out of the box /etc/resolv.conf (which uses the host computer as
a name server) with one
using an external name server (e.g. 8.8.8.8) restores the expected behaviour.
I
Extra command results as requested (this is indeed on WSL2):
pjn:~$ host ubuntu.com
ubuntu.com has address 91.189.88.180
ubuntu.com has address 91.189.88.181
ubuntu.com has address 185.125.190.20
ubuntu.com has address 185.125.190.29
ubuntu.com has address 185.125.190.21
ns1.canonical.com has
Public bug reported:
Coincident with the host command now outputing the names and IP addresses of
the DNS servers, as well
as the host information requested, ssh seems to be getting the same
(multi-line) response which it then
treats as a round-robin response. As a result, if the host is down,
Public bug reported:
Since some time on 16/06/2016 Puppet manifests that use the "pip"
provider to manage Python packages are failing with a 403 error, on (at
least) Ubuntu 14.04.4 LTS, when processed using "puppet apply...".
puppet version is 3.4.3-1ubuntu1.1
python-pip version is
Public bug reported:
Binary package hint: at
Description:Ubuntu 9.10
Release:9.10
at:
Installed: 3.1.11-1ubuntu4
Candidate: 3.1.11-1ubuntu4
Version table:
*** 3.1.11-1ubuntu4 0
500 http://gb.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status
