-
Notifications
You must be signed in to change notification settings - Fork 817
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
Ability to configure domain name from wsl.conf #11688
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 scipt will output the path of the log file once done. 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:
|
/feature |
Diagnostic information
|
Windows Version
Microsoft Windows [version 10.0.22621.3593]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
If
generateResolvConf
is false, I can configure the company's domain manually in/etc/resolv.conf
.However, with such a configuration, it is more difficult to retrieve the WSL gateway IP address, ex
NEW_IP=$(grep -m 1 nameserver /etc/resolv.conf | awk '{print $2}')
.As a workaround, one can use:
netstat -rn | grep "^0.0.0.0" | awk '{print $2}'
Expected Behavior
Actual Behavior
When
generateResolvConf
is true, WSL ignores my company's domain, thus I cannot ping servers of my network without specifying the domain (ex:ping mygitserver.MY.COMPANY
).Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: