Allow WSL DNS Proxy when using NetworkMode=VirtioProxy
@benhillis is already working on this.
Since Feb 10, 2026.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
**Is your feature request related to a problem? Please describe.**
When WSL2 `NetworkMode` is set to `VirtioProxy`, WSL cannot use the built-in DNS Proxy and instead relies on an auto-generated `/mnt/wsl/resolv.conf`.
This file lists DNS servers from multiple Windows network interfaces (e.g. physical NICs and VPN adapters). In VPN scenarios, DNS queries are first sent to physical NIC DNS servers, fail or time out, and only then reach the VPN DNS server, causing noticeable delays and unreliable name resolution.
**Describe the solution you'd like**
Please support using the WSL DNS Proxy when `NetworkMode=VirtioProxy`.
DNS behavior should be consistent with the default WSL2 networking mode and correctly integrate with Windows DNS resolution, including VPN and split-DNS scenarios, without relying on sequential queries to unrelated NIC DNS servers.
**Describe alternatives you've considered**
- Manually managing `/etc/resolv.conf`, which is fragile and breaks on network or VPN changes.
- Avoiding `VirtioProxy`, which is undesirable for my use case.
**Additional context**
- WSL version: 2.6.3.0
- Kernel: 6.6.87.2-1
- Windows version: 10.0.26100.7628
- Current behavior: `/etc/resolv.conf` → symlink to `/mnt/wsl/resolv.conf`, generated from Windows NIC DNS settings, leading to delayed DNS resolution when VPN is active.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.