-
Notifications
You must be signed in to change notification settings - Fork 1.3k
DNS is not working on WSL #10068
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
Comments
TL;DR define your own DNS servers in resolv.conf and disable automatic generation. However, this begs the question: to what extent will this effect local and/or docker/podman name resolution? |
Related #10111. @dragoncommits can you confirm if you updated to KB5026361? |
I am on the latest windows version that windows allows me to be on. I am not sure how to check if I am on KB5026361 or not. |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Windows Version
Microsoft Windows [Version 10.0.22621.1635]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
Ubunto 22.04
Other Software
No response
Repro Steps
run ping google.com inside ubuntu
Expected Behavior
ping to google.com
Actual Behavior
root@pc:~# ping google.com
ping: google.com: Temporary failure in name resolution
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: