-
Notifications
You must be signed in to change notification settings - Fork 152
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
OpenVPN3 doesn't set back previous DNS after disconnect using systemd-resolved in stub mode #246
Comments
Can you please run this command as
If the output here doesn't look too concerning to you, you can add the I expect this command to detect Before starting a new VPN session, please ensure that |
Please retest with the latest |
Unforturnately I have exactly the same problem: in stub mode after disconnecting from VPN I still have corporate DNS and domains set which leads to internet basically not working. Version:
|
In foreign mode corporate network works, but OpenVPN3 sets only one DNS server (but we are using two), leaves for some reason my home DNS server, overall I would say it behaves the same:
I need to admit that this is completely new PC which I setup from scratch using |
I am using the latest Arch Linux with systemd-resolved. I am dealing with rather two problems, but the most annoying is the case in stub resolve.conf mode.
So in foreign mode (with usual
/etc/resolv.conf
mode) OpenVPN3 just adds VPN's DNS server to the list, but it doesn't make it primary even if I am overriding withdns-scope: global
:192.168.88.1
is my home network cache server. In that case corporate services with domain other than from DNS Domain list resolves to external IP (dns-scope: global
was here to fix it or I missed something?). The reason for this problem probably missing~.
in domains.But in stub mode situation is even more weird. So OpenVPN finally detects stub mode and sets only one DNS:
Finally even corporate resources with domain other than from Domain list resolving, but after proper disconnecting it leaves the corporate DNS installed for systemd-resolved:
So basically network breaks and until I will manually do
systemctl restart systemd-resolved.service
it won't recover. For me it looks at least strange and probably broken.The text was updated successfully, but these errors were encountered: