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.

Sign up for GitHub

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

Jump to bottom

DNS in WSL2 stops working after Wifi change in mirrored mode #12246

Open
1 of 2 tasks
OscBacon opened this issue Nov 7, 2024 · 2 comments
Open
1 of 2 tasks

DNS in WSL2 stops working after Wifi change in mirrored mode #12246

OscBacon opened this issue Nov 7, 2024 · 2 comments

Comments

@OscBacon
Copy link

OscBacon commented Nov 7, 2024

Windows Version

Microsoft Windows [Version 10.0.22631.4317]

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

curl google.com
# Connect to another wifi network
curl google.com

Expected Behavior

Getting the same response on both curl requests:

<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">                                                                              <TITLE>301 Moved</TITLE></HEAD><BODY>                                                                                                                       <H1>301 Moved</H1>                                                                                                                                          The document has moved                                                                                                                                      <A HREF="http://www.google.com/">here</A>.                                                                                                                  </BODY></HTML>

Actual Behavior

On the second curl:

curl: (6) Could not resolve host: google.com

With the verbose flag:

* Could not resolve host: google.com
* shutting down connection #0
curl: (6) Could not resolve host: google.com

Diagnostic Logs

I also tested dig:

dig google.com
;; communications error to 8.8.8.8#53: timed out
;; communications error to 8.8.8.8#53: timed out
;; communications error to 8.8.8.8#53: timed out

; <<>> DiG 9.18.28-0ubuntu0.22.04.1-Ubuntu <<>> google.com
;; global options: +cmd
;; no servers could be reached

Note that my /etc/resolve.conf looks like this:

nameserver 8.8.8.8
@github-actions GitHub Actions
Copy link

github-actions bot commented Nov 7, 2024

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

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
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please 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:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@OscBacon
Copy link
Author

OscBacon commented Nov 7, 2024 •
edited
Loading

The networking logs fail to upload directly, so I'll make it a Google Drive link:
https://drive.google.com/file/d/1SaQzbulEGGppzAjU5qm8r9PzLBtpoXPs/view?usp=sharing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@OscBacon