Skip to content

Privacy & security

DNS leaks explained

What a DNS leak exposes, how to test for one and how to fix it.

Updated · First published · 8 sources

The short answer

A DNS leak happens when your device looks up website names outside the VPN tunnel, usually through your internet provider, even though the VPN is connected. Whoever answers those lookups can see every domain you visit. Run an extended test at a site such as dnsleaktest.com, and fix a leak by turning on your VPN’s DNS leak protection and dealing with IPv6 and browser DNS settings.

What is a DNS leak?

Before your browser can load a site, your device asks a DNS server for the site’s IP address. Traditional DNS lookups are unencrypted, which Mozilla says makes it “easy for third-parties to see what website you’re about to access”.

With a VPN on, those lookups should travel inside the encrypted tunnel to a DNS server run by the VPN provider. A leak is any lookup that goes another way, most often to the DNS server your internet provider or router hands out.

What does a DNS leak reveal?

A leaked lookup shows the domain name you asked for, such as a news site or a streaming service, and the IP address it came from. It doesn’t show the pages you read or what you type on a site that uses HTTPS.

That is still a browsing history. It goes to whoever runs the DNS server, and Mozilla notes that unencrypted lookups are also visible to your internet provider and anyone else on your local network, such as someone on the same public Wi-Fi.

What causes DNS leaks?

  • The operating system keeps using its default DNS servers for some lookups instead of the VPN’s.
  • Your internet provider intercepts ordinary DNS traffic and answers it with its own servers, a “transparent DNS proxy”.
  • IPv6 traffic bypasses a VPN that only handles IPv4. An IETF report on VPN leakage in dual-stack networks describes how this sends traffic, including DNS, out in the clear.
  • Your browser uses its own encrypted DNS provider, so lookups go to that provider instead of the VPN’s servers.
  • The VPN drops briefly and the device falls back to your normal connection. A kill switch prevents this.

How do you test for a DNS leak?

  1. Connect to your VPN.
  2. Open dnsleaktest.com and run the extended test. It sends 36 lookups instead of the standard test’s 6, so it’s more likely to find every DNS server handling your requests.
  3. Read the list of DNS servers. Each should belong to your VPN provider or its hosting company, near the VPN server you chose.
  4. If any server belongs to your internet provider, or sits in your real location, you have a leak.
  5. Repeat the check on ipleak.net or BrowserLeaks, and on each device you use.

A server from your browser’s encrypted DNS provider, such as Cloudflare or Google, isn’t your internet provider. It still means a company other than your VPN sees your lookups.

For a full check that also covers IP, WebRTC and IPv6 leaks, see how to test your VPN.

How do you fix a DNS leak?

  1. Turn on DNS leak protection in your VPN app if it has a separate switch, and leave the app to set DNS rather than entering servers by hand.
  2. Turn on the app’s IPv6 leak protection. If your VPN doesn’t support IPv6, the IETF report recommends disabling IPv6 while the tunnel is in use, as a temporary workaround.
  3. Check your browser’s secure DNS setting (see below).
  4. Turn on the kill switch so drops don’t fall back to your normal connection.
  5. Update the VPN app, reconnect and test again. If it still leaks, contact the provider’s support.

Every provider in our [rankings](/) offers DNS leak protection, and our methodology counts it under security features.

How does DNS over HTTPS work with a VPN?

DNS over HTTPS (DoH), defined by the IETF in RFC 8484, sends DNS lookups as ordinary encrypted HTTPS traffic, usually on port 443. Without a VPN, it hides your lookups from your internet provider and anyone on your local network.

With a VPN, DoH traffic travels through the tunnel like any other HTTPS connection, so your internet provider still can’t see it. But the DoH provider, not your VPN, answers the lookups and learns which domains you visit. That’s why a leak test can list a DoH provider’s servers.

Firefox handles this on its Default Protection setting, which turns DoH off when a VPN is active. Mozilla describes Increased and Max Protection as always using your chosen provider, and doesn’t list a VPN exception for them. You’ll find the setting under Settings, Privacy & Security, DNS over HTTPS.

Using your VPN’s own DNS keeps lookups with one company. Keeping DoH on while the VPN runs adds a second company that sees your lookups.

Common questions

Can my ISP see my browsing if my VPN leaks DNS?

It can see the domain names you look up, but not the pages you read or what you send to HTTPS sites. That’s enough to build a list of the sites you use.

Is a DNS leak dangerous?

It’s a privacy problem rather than a security hole. It undoes much of the privacy a VPN gives you, because your internet provider or another DNS operator gets a list of the domains you visit.

Should I use DNS over HTTPS with a VPN?

Usually not. Your VPN already encrypts DNS inside the tunnel, and DoH adds another company that sees your lookups. Use DoH when you aren’t on the VPN.

Does disabling IPv6 stop DNS leaks?

It stops IPv6 leaks when your VPN doesn’t support IPv6, but the IETF calls it a temporary workaround. A VPN that routes IPv6 through the tunnel is the proper fix.

Sources

We checked this guide against these pages on October 22, 2026.

  1. Firefox DNS over HTTPS · Mozilla Support
  2. Configure DNS over HTTPS protection levels in Firefox · Mozilla Support
  3. RFC 8484: DNS Queries over HTTPS (DoH) · IETF
  4. RFC 7359: Layer 3 Virtual Private Network (VPN) Tunnel Traffic Leakages in Dual-Stack Hosts/Networks · IETF
  5. What is a DNS leak? · DNS leak test
  6. Standard vs extended test: what’s the difference? · DNS leak test
  7. IPleak.net · IPleak.net
  8. DNS leak test · BrowserLeaks