DNS troubleshooting
A DNS leak happens when your DNS queries still go to your normal resolver instead of the VPN path. Public OpenVPN profiles may not push reliable DNS settings, so always test DNS after connecting.
Use this guide after importing a public .ovpn profile and before relying on the connection for browsing tests.
Run DNS checks only after the VPN client reports connected.
Compare resolver behavior with visible IP results.
Windows, Android and Linux handle DNS differently.
Public profiles may not push usable DNS settings.
A DNS leak means domain lookups are visible to a resolver outside the expected VPN path, even if some traffic uses the tunnel.
Public .ovpn files vary widely. Some push DNS options, some leave DNS unchanged, and some use stale settings.
Check adapter DNS state after connecting and reconnect if Windows keeps the old resolver.
Re-run the test after approving VPN permission and avoid stale imported profiles.
Use resolvectl status, NetworkManager details or distro network settings to compare resolver state.
The DNS leak test gives a practical browser-side check and links back to safer profile selection.
If DNS remains outside the VPN path after reconnecting and switching protocol, use another fresh checked profile.
A clean DNS result still does not verify the VPN operator or logging policy.