Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wsl2 DNS failure #8474

Closed
1 of 2 tasks
snowgato opened this issue Jun 5, 2022 · 2 comments
Closed
1 of 2 tasks

wsl2 DNS failure #8474

snowgato opened this issue Jun 5, 2022 · 2 comments

Comments

@snowgato
Copy link

snowgato commented Jun 5, 2022

Version

windows 10.0.22621.1

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.10.102.1

Distro Version

Ubuntu-20.04

Other Software

No response

Repro Steps

Hello, I have today a wsl2 dns failure
$ ping google.com
ping: google.com: Temporary failure in name resolution

ping works in windows,
Lately I had the same dns problem within wsl2 that got resolved from manually editing /etc/resolv.conf and /etc/wsl.conf to prevent wsl2 from overwriting it at boot.

Nevertheless, today, after having some python installation trouble, solved following this page: https://askubuntu.com/questions/1402456/unmet-dependencies-for-python-3-10, and I have been able to install python3.10 . Then did apt full-upgrade and wanted to install some software to mount usb devices in wsl2 following this page: https://devblogs.microsoft.com/commandline/connecting-usb-devices-to-wsl/ . I had installed in windows usbipd-win usbipd-Win](url). Then I could not get anymore internet connection from wsl2 , I could not execute successfully this command:
sudo apt install linux-tools-5.4.0-77-generic hwdata

I have tried to restore /etc/wsl.conf to enable automatic generation, but that doesn't solve the bug neither. Neither does the action of disabling fully windows firewall.
Would greatly appreciate some help,
Thanks a lot !

Expected Behavior

ping google.com would succeed

Actual Behavior

it doesn't

Diagnostic Logs

No response

@benhillis
Copy link
Member

/dupe #8365

@ghost
Copy link

ghost commented Jun 7, 2022

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants