PROTONVPN UBUNTU FULL
PROTONVPN UBUNTU SOFTWARE
PROTONVPN UBUNTU CODE

(I don't know, I don't use them) They may want you to use *their* DNS servers and you are attempting to override that. Proton VPN could possibly be trying to block DNS that isn't their own.(though my home desktop has a lot of non-standard modifications I've made to it) My work VPN (OpenVPN) does this on my home desktop, though not on my work laptop. VPNs are known to jack-up local DNS from time to time to the point that rebooting becomes necessary.If they are and they set your DNS to ::1, then the local VPN client might be trying to act as your DNS server. Unless your ProtonVPN is forcing you to use IPv6, I doubt this is your problem. I really don't have much experience with IPv6, but I believe you meant ::1 (1 not 6) This is 'localhost' for IPv6. The VPNs they use are network devices powered site-to-site VPNs. How this affects VPNs I heard can be a positive for desktops, but my servers do not have VPNs installed on them. They tend to like the click-to nature of NetworkManager. That said, from Linux Desktop users I know. Second, it sometimes seems to have a mind on its own that breaks what I'm trying to do. As I'm not a Linux Desktop user, I immediately disable NetworkManager on my server. So, let's wade into some of the possible issues here. It also helps because in your case, you're looking to cover your tracks it appears and you definitely do not want to be using your local DNS which would 'leak' your DNS requests and tell people on the local network exactly what sites you are attempting to get to.

PROTONVPN UBUNTU SOFTWARE

(check the VPN software for a DNS setting) This occurs because you are connecting to a secondary network that may have its own internal DNS. VPN software will usually configure their own (preconfigured) DNS servers. pinging the intranet and google both work fine without the vpn connected.

PROTONVPN UBUNTU CODE

this isn't a bug in protonvpn's code because the error is displayed while attempting to connect to expressvpn also. the nf file seems to be nuked by protonvpn-cli due to the addition of '::6' to the /etc/nf file but oddly enough, subsequent attempts to reconnect to the VPN appear to 'fail for an unknown reason'. I can go into /etc/nf and add 'nameserver 1.1.1.1' to the end of the file but that seems to point back to the current location of the computer, without the VPN even seeming to notice.

PROTONVPN UBUNTU FULL

protonvpn-cli can connect(albeit after about a full thirty seconds of attempts) but no internet connection in a web browser or from the arch repositories seems to be able to be connected to. There has to be something that saved the DNS configuration for NetworkManager between restarts, although I haven't really been forced to confront the issue head on because any sensitive information has been communicated over tor. Now, when the VPN is connecting, /etc/nf is reset and provides a nameserver that is either the router or '::6' or something. only dhcpcd and NetworkManager are installed as network services under systemctl, as this is a fresh install, so there shouldn't be any reason afaik that would cause such an issue.) This is honestly it's own issue that probably is a simple fix, and while help would be greatly appreciated with that issue, that's not really the reason this thread was made(although seriously, if you do know why this is, it would be much appreciated. It seems that when this happens a restart of some sort of network service is restarted which resets the DNS server used in nf

Protonvpn ubuntu