-
Notifications
You must be signed in to change notification settings - Fork 814
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
Querying ${hostname}.local
takes forever due to DNS server that is built into WSL
#12080
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:
|
Diagnostic information
|
Windows Version
Microsoft Windows [Version 10.0.22631.4169]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
Linux version 5.15.153.1-microsoft-standard-WSL2
Distro Version
Any, I guess. The bug reproduces on Ubuntu 23.04 and on openSUSE Tumbleweed 20240923
Other Software
on my openSUSE Tumbleweed machine:
avahi-daemon 0.8
libnss-mdns 0.15.1-1.5
systemd 256.5-1.1
Repro Steps
However, if I change my DNS server in
/etc/resolv.conf
, then everything is super fast:Expected Behavior
I get the results in 10 seconds
Actual Behavior
I get the results in 0.00001 seconds
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: