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

/etc/resolv.conf is wrong when using VPN #1986

Closed
ayanamist opened this Issue Apr 23, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@ayanamist
Copy link

ayanamist commented Apr 23, 2017

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    Microsoft Windows [Version 10.0.15063]

  • What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
    Using a WiFi to connect to internet, then use a VPN (like AnyConnect) to dial into company private net.
    Then use nslookup to see effective DNS server:
    image
    However, /etc/resolv.conf shows that this dns server is not the first one.
    image
    So some queries which only 10.20.0.98 can answer is failed.

  • What's wrong / what should be happening instead:
    WSL use the same dns order like windows

@legigor

This comment has been minimized.

Copy link

legigor commented Apr 25, 2017

Same here #1881

@sunilmut

This comment has been minimized.

Copy link
Member

sunilmut commented Jul 25, 2017

If you are connected to a VPN and lose connectivity within bash, please try the workaround posted here. It should work for Creators Update and above. Post Fall Creators Update, we will be looking at a better support for other VPN solutions.

Thanks to @bradley101, who first pointed out the workaround. Also, marking this duplicate of #1350

@sunilmut sunilmut marked this as a duplicate of #1350 Jul 25, 2017

@ayanamist ayanamist closed this Nov 10, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment