Search results

ah, hahaha, what a goof, the attempt to use ipv6 would, at the moment, appear to be the issue because I had disabled ipv6 for the interface. also, you were right, that it is "::1". not "::6". where I went wrong is in the assumption that the linux kernel wouldn't have it's own method of handling...

thanks for the reply, much appreciated. I'm decently sure that the issue isn't with protonvpn because expressvpn is seemingly having the same issue.

It seems that when this happens a restart of some sort of network service is restarted which resets the DNS server used in resolv.conf 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...