-
Notifications
You must be signed in to change notification settings - Fork 832
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
Set DNS resolver options in autogenerated resolver configuration #11385
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! Closed similar issues:
|
/feature |
Diagnostic information
|
@olliefr |
Yes, I do 😈
I'll fire it and get a better one, then! 😉 |
Is your feature request related to a problem? Please describe.
I would like to configure the
timeout
and the retryattempts
for a DNS resolver which is using autogenerated/etc/resolver.conf
.Describe the solution you'd like
I suppose that an extra parameter for
wsl.conf
sectionnetwork
would solve this.It could be named
resolvConfOptions
and its type would bestring
.The value would be added to the autogenerated
/etc/resolv.conf
asoptions ...
Example
wsl.conf
:This would produce the following example
/etc/resolv.conf
:Describe alternatives you've considered
To the best of my knowledge, the only alternative at the moment is to turn off auto-generation and manage
/etc/resolv.conf
manually. This does not sound appealing as network settings and DNS server addresses do change.The text was updated successfully, but these errors were encountered: