So I’ve tried manually setting the DNS servers from surfshark website but they keep getting deleted or switched off after reboots. I’ve tracked it down to the wireguard protocol setting. It always leaks in wireguard now but not in OpenVPN (TCP) protocol. Which is slower.
I’ve turned off secure DNS servers in the browsers so I know they’re not causing the problem. This is happened recently and I thought I had fixed it by manually setting the DNS servers for surfshark(suggested via Chat Help from Surfshark). But they just switch back to assigned by ISP after reboot. Is this a windows 11 issue maybe? I’ve only noticed this since installing 5.7.4. I would rather go back to 5.7.1 when this wasn’t an issue. Can i get the older install back?
Also, havent had any issues with my debian surfshark app dealing with DNS leaks.
Hey. While we typically recommend using the latest version for improved security and features, we understand your concern. For now, you can not download an older version of Surfshark like that. However, you could also try the OpenVPN (UDP) protocol. It should provide faster speeds than TCP. Additionally, a simple reinstall of the app could also help as something may have gone wrong during the update process resulting in such issues.
Strangely enough Wireguard is now working properly without an update. Worries me because it means there was a problem at the backend of the system not from the computer.
FYI, exactly the same issue since 5.8.xx
Rolled back to 5.7.1 and it now works again.
Will use udp until it gets sorted. I’ve also tested it on a fresh windows 10 install and get the same results after rebooting. The wireguard protocol just does not work in any of my windows versions. Hopefully, will be fixed in next update. They do seem to update the windows version often.
So it works fine when first installed but after reboot it always fails the leak test.
Got back home from Atlanta and wireguard doesn’t work again. Can ISPs do something to alter wireguard from working properly?