DNS resolution for Internal Sites doesn't work when using Global Secure Access Client

[karthiktumu]

Windows Version

Microsoft Windows [Version 10.0.19045.4412]

WSL Version

2.2.4

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

Ubuntu 22.04

Other Software

Global Secure Access Client 1.7.669.0

Repro Steps

1. Connect to company VPN using Global Secure Access Client Tool
2. Do nslookup for internal sites from inside wsl distro.

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

[github-actions]

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 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
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com 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:

• Cisco Anyconnect blocks DNS access from WSL2 (#11075), similarity score: 0.76

Closed similar issues:

• WSL Name resolution failure when connected to company VPN (#7224), similarity score: 0.75
• Mcafee Endpoint Security and WSL2 DNS (#8370), similarity score: 0.73
• DNS resolve does not work properly with vpn (#5120), similarity score: 0.73
• No name resolution in WSL2 even with custom resolv.conf (#6219), similarity score: 0.73

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

[karthiktumu]

WslLogs-2024-07-03_15-34-34.zip

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.2.4.0

[OneBlue]

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.