Skip to content
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

DNS resolve does not work properly with vpn #5120

Closed
sifear opened this issue Apr 22, 2020 · 2 comments
Closed

DNS resolve does not work properly with vpn #5120

sifear opened this issue Apr 22, 2020 · 2 comments

Comments

@sifear
Copy link

sifear commented Apr 22, 2020

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

  • What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

  1. Start Cisco AnyConnect vpn and wait until its connected
  2. Start Ubuntu from Start menu
  3. Ping a public website: success
  4. Ping any company url: ping: <my-company-url.com>: Name or service not known
  5. Ping company url in windows: success
  • What's wrong / what should be happening instead:
    I feel i should be able to ping both url's. I need them both for an internal application we develop which uses services from public and private network (internet and intranet)

Resolv.conf has my ISP's dsn ip as first and second line, then vpn dns ip as third then a line with content: search company domain.com
If i move the vpn dns ip to top then i can ping my company url and not the public one. Error in this case ping: index.hu: Name or service not known

I need to be able to ping both.
If i run Ubuntu in Hyper-v its working. But its laggish to work in so i thought i might try WSL + VCode combo.

@therealkenc
Copy link
Collaborator

/dupe #4277 #2529

@ghost
Copy link

ghost commented Apr 23, 2020

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

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

No branches or pull requests

2 participants