Comment 5 for bug 1952131

Revision history for this message
Dr Philip J Naylor (p-j-naylor) wrote :

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 guess I'll need to raise this with Microsoft instead.