-
Notifications
You must be signed in to change notification settings - Fork 822
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 resolution for Internal Sites doesn't work when using Global Secure Access Client #11745
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:
|
Diagnostic information
|
Thank you for reporting this @karthiktumu. This issue should be resolved with DNS tunelling. Unfortunately this feature is only supported on Windows 11 and higher so you'll need to upgrade your Windows build to get it. |
Windows Version
Microsoft Windows [Version 10.0.19045.4412]
WSL Version
2.2.4
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
Ubuntu 22.04
Other Software
Global Secure Access Client 1.7.669.0
Repro Steps
Expected Behavior
DNS resolution for internal sites should work from inside WSL2 distro.
Actual Behavior
DNS lookup fails finding internal sites.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: