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

Weird DNS server after successfull connection (131.234.137.23, net1.uni-paderborn.de) #3

Closed
GoogleCodeExporter opened this issue Mar 19, 2015 · 3 comments
Labels

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Connect to the VPN
2. Try to resolve internal systems

What is the expected output? What do you see instead?

Since internal DNS names cannot be resolved over an external DNS server, only 
IP-based access seems to be possible right now

What version of the product are you using? On what operating system?

Latest Version (16.04.2012)




Original issue reported on code.google.com by [email protected] on 20 Apr 2012 at 5:11

@GoogleCodeExporter
Copy link
Author

I just checked the source - the DNS is hardcoded right now - an option field 
would be great!

Original comment by [email protected] on 20 Apr 2012 at 5:13

@GoogleCodeExporter
Copy link
Author

Yes that is the DNS of the University of Paderborn. Next version will honour 
the DNS Server pushed from the Server and allow to set your own Server too.

Original comment by [email protected] on 22 Apr 2012 at 10:13

  • Changed state: Started
  • Added labels: Priority-High
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

This issue was closed by revision 19b391e658f0.

Original comment by [email protected] on 29 Apr 2012 at 1:25

  • Changed state: Fixed

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

No branches or pull requests

1 participant