-
Notifications
You must be signed in to change notification settings - Fork 837
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
dns stopped working #12423
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
|
it will not let me upload my log file |
Windows Version
10.0.26100.2605
WSL Version
2.3.26.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.167.4-1
Distro Version
ubuntu 24.04.1
Other Software
Repro Steps
run wsl
ping -c 5 google.com
PING google.com (142.250.190.110) 56(84) bytes of data.
From 10.99.214.91 icmp_seq=1 Destination Host Unreachable
From 10.99.214.91 icmp_seq=2 Destination Host Unreachable
From 10.99.214.91 icmp_seq=3 Destination Host Unreachable
From 10.99.214.91 icmp_seq=4 Destination Host Unreachable
From 10.99.214.91 icmp_seq=5 Destination Host Unreachable
--- google.com ping statistics ---
5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 14124ms
this was working a couple days agoa and it just quit working for some reason
pipe 4
Expected Behavior
dns working
Actual Behavior
dns not working
Diagnostic Logs
The text was updated successfully, but these errors were encountered: