How to disable WSL DNS mechanism? #9699
Unanswered
Tabiskabis
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
Does overwriting |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In windows, I use a few search domains and NRPT rules to direct the according lookups at their right server.
When I do DNS queries in WSL, they bypass the NRPT rules and any DNS query goes to every first nameserver of each network interface.
So I thought I'd use a local DNS resolver/cache as a service in windows and implement the NRPT rules as conditional forwardings instead. This works somewhat, but only if 127.0.0.1 is the only nameserver windows knows about. So basically no more DHCP for me, or WSL starts spewing and leaking queries again.
Can this be mitigated somehow? Ideally by forcing WSL to respect NRPT or make its queries otherwise behave like windows, or force it to use only my local dns service.
I also thought about using unbound as resolver on both windows and linux, so i could include a shared conffile on both. But apparently, services on WSL are not exactly stable?
Edit: Also just realised, wtf why is resolv.conf shared across wsl distributions?
Beta Was this translation helpful? Give feedback.
All reactions