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

nameserver got 10.255.255.254 #12101

Closed
1 of 2 tasks
rickywu opened this issue Sep 29, 2024 · 5 comments
Closed
1 of 2 tasks

nameserver got 10.255.255.254 #12101

rickywu opened this issue Sep 29, 2024 · 5 comments

Comments

@rickywu
Copy link

rickywu commented Sep 29, 2024

Windows Version

Windows 11 home edition

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

cat /etc/resolv.conf got wrong server
how should I got correct one if edit manullay

Expected Behavior

# generateResolvConf = false
nameserver 172.x.x.x
search lan

Actual Behavior

generateResolvConf = false
nameserver 10.255.255.254
search lan

Diagnostic Logs

WslLogs-2024-09-29_23-49-07.zip

Copy link

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.

Copy link

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
Issue was edited and new log file was found: https://github.com/user-attachments/files/17179825/WslLogs-2024-09-29_23-46-31.zip
.wslconfig found
Detected appx version: 2.2.4.0
Found no WSL traces in the logs

Copy link

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
Issue was edited and new log file was found: https://github.com/user-attachments/files/17179833/WslLogs-2024-09-29_23-49-07.zip
.wslconfig found
Detected appx version: 2.2.4.0
Found no WSL traces in the logs

@elsaco
Copy link

elsaco commented Sep 30, 2024

Disable dnsTunneling. It's enabled by default. Add dnsTunneling=false to your $HOME\.wslconfig

@rickywu rickywu closed this as completed Sep 30, 2024
@zerzerzerz
Copy link

Create or edit the .wslconfig file in the directory %UserProfile% in Windows host, following this url.

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

3 participants