Thanks for the follow-up. As this doesn't seem to be a bug in Ubuntu,
and that I doubt that a (sane) workaround can be implemented on the
Ubuntu side, I'm marking this bug report as Invalid. Should you not
agree please do not hesitate to change the bug status back to New and
share your reasoning, w
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 subscr
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 gue
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 addr
Also: what's the output if you explicitly specify the DNS server to
query? E.g.
root@paride-f:~# host ubuntu.com 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
ubuntu.com has address 91.189.88.181
ubuntu.com has address 185.125.190.20
ubuntu.com has address 185.125.190.2
Hello and thanks for this bug report. I'm not aware of any change in the
the 'host' command output, and indeed it seems to be the usual one to
me:
root@paride-f:~# host ubuntu.com
ubuntu.com has address 91.189.88.181
ubuntu.com has address 185.125.190.29
ubuntu.com has address 185.125.190.21
ubunt
