· 3 min read · By BSafe Group
DNS leaks explained: why your VPN might still reveal the sites you visit
What DNS is, how a DNS leak happens even with a VPN switched on, how to test for one, and how DNS-over-HTTPS closes the gap.
DNS · Privacy · Technology
You switch on your VPN, the icon turns green, and you assume your browsing is private. But there is one step of almost every connection that can slip around the tunnel: the DNS lookup. When it does, it is called a DNS leak.
A quick refresher on DNS
Computers connect to IP addresses, not names. Before your browser can open example.com, it asks a DNS resolver to translate the name into an address. Normally that resolver is run by your internet provider, or by whoever runs the Wi-Fi network you are on.
That means the resolver sees every name you look up, with a timestamp, and knows your IP address. Even if the pages themselves are encrypted, the list of names is a detailed record of your browsing.
Classic DNS is also sent unencrypted, so anyone on the network path can read it, and on a hostile network can change the answers.
What a DNS leak is
A VPN is supposed to send your DNS lookups through the tunnel to a resolver it controls. A DNS leak happens when lookups go to your provider's resolver instead, outside the tunnel. Your traffic is protected, but the list of sites you visit is not.
Common causes:
- Operating system behaviour. Some systems send queries to every configured resolver at once and use whichever answers first, including the one outside the tunnel.
- IPv6. If a VPN only handles IPv4, lookups and connections over IPv6 can bypass it entirely.
- Network-assigned resolvers. Wi-Fi networks hand out their own DNS servers, and some apps use them directly.
- The seconds after a reconnect. When a connection drops and comes back, queries can escape before the tunnel is restored.
- Browser features. Some browsers have their own DNS settings that ignore the system's.
How to test for a leak
Connect your VPN and visit a DNS leak test site, then look at the list of resolvers it shows. If you see servers belonging to your internet provider, or to the café or hotel network, you have a leak. If you only see the resolvers of your VPN provider, you are fine. Repeat the test after switching networks, because leaks often show up only in specific situations.
How BSVPN prevents DNS leaks
BSVPN treats DNS as part of the tunnel, not as an afterthought:
- DNS-over-HTTPS inside the tunnel. Lookups are sent encrypted, over HTTPS (RFC 8484), through the VPN connection. Nobody on the local network sees them, and they cannot be tampered with.
- No DNS logs. Nothing on BSVPN servers records the names you look up. We do not keep a list of your queries, not even temporarily. See the security and no-logs policy.
- Kill switch. If the tunnel drops, traffic is blocked until it is back, so lookups cannot fall back to the network's resolver.
- Routing rules that respect DNS. When smart routing sends a local site outside the tunnel, the decision is made by the app, not by whichever resolver answers first.
What you can do yourself
- Run a leak test after installing any VPN, and again on a new network.
- In your browser, check whether "secure DNS" is set to a provider of its own. With BSVPN connected, you can leave it on the system default.
- Keep the kill switch enabled.
- Be wary of VPNs that mention DNS nowhere in their documentation.
Summary
Encryption protects what you send. DNS reveals where you send it. A VPN that does not protect DNS hides the letter but leaves the address on the envelope. Make sure yours does both.
Updated . Questions or corrections? Write to benelux@bsafegroup.be.