Your own VPN server · WireGuard, Outline, AmneziaWG · 6 cities · Pay in BTC, USDT, USDC, ETH, SOL, LTC, XMR
Language: English
Get a VPN server

Guide · DNS and IPv6 leaks on a personal VPN

How do I check a VPN for DNS leaks?

Where name lookups go when the tunnel is on, how the client file controls it, and what a leak test can and cannot prove.

Last updated: · 4 min read

Quick answer

How do I check a VPN for DNS leaks?

Here is how to check a VPN for DNS leaks: turn the tunnel on, open a DNS leak test page, and confirm that only the resolver from your config appears, not your internet provider. On a TunnelVPS WireGuard server, set DNS = in each client file and include ::/0 in AllowedIPs. Run 3 checks: IP, DNS, IPv6.

In brief
  • Cause: the device keeps asking the home or café resolver while the tunnel is up.
  • Fix: a DNS = line in the client's [Interface] section.
  • IPv6: without ::/0 in AllowedIPs, IPv6 traffic can bypass the tunnel.
  • Limit: a clean test shows the tunnel works, not that you are hidden from the sites you visit.

What are the steps for a DNS leak check?

DNS leak check for a WireGuard tunnel to a TunnelVPS server, 5 steps
StepWhereWhat to do
1Client fileSet DNS = to the resolver you trust, in the [Interface] section.
2Client fileSet AllowedIPs = 0.0.0.0/0, ::/0 for a full tunnel.
3DeviceTurn the tunnel on and open a page that shows your public IP.
4DeviceRun a DNS leak test page and read the resolver list.
5DeviceTurn the tunnel off and repeat, to see the difference.

What is a DNS leak on a personal VPN?

A DNS leak is a name lookup that goes to the local network's resolver instead of through the tunnel. The pages themselves travel through the VPN, but the list of names you visit reaches the café or internet provider anyway.

It usually happens when the client file has no DNS = line. The device then keeps the resolver it got from the Wi-Fi. That is why learning how to check a VPN for DNS leaks belongs in every new setup.

How does the client file control DNS?

The DNS = line in [Interface] tells the client which resolver to use while the tunnel is up. On Linux, wg-quick applies it through resolvconf when the interface comes up and removes it when it goes down, per its manual. The phone and desktop apps apply the same line.

Pick a resolver you trust and reach it through the tunnel. Placeholders below stand in for real values.

Client file with a DNS line and a full tunnel (dummy values)
[Interface]
PrivateKey = <LAPTOP_PRIVATE_KEY>
Address = 10.8.0.3/32
DNS = <DNS_RESOLVER_IP>

[Peer]
PublicKey = <SERVER_PUBLIC_KEY>
Endpoint = 203.0.113.10:51820
AllowedIPs = 0.0.0.0/0, ::/0

Why does IPv6 matter for leaks?

Because a device with IPv6 at home sends IPv6 traffic outside the tunnel if AllowedIPs covers only IPv4. Adding ::/0 sends it into the tunnel too. Each TunnelVPS server has an IPv6 /64, so the server can carry that traffic.

The WireGuard IPv6 guide sets up the server side. Without it, ::/0 in the client still blocks the IPv6 leak, but IPv6 sites will not load through the tunnel.

How do you run the check on a device?

Compare what a test page shows with the tunnel on and off. With the tunnel on, the public IPv4 should be the server's address from the dashboard. A DNS leak test page lists the resolvers that answered its lookups. Only your chosen resolver should appear, not your internet provider's.

On Linux, cat /etc/resolv.conf with the tunnel up shows which resolver is in use. Repeat the check after any app or system update. Anyone asking how to check a VPN for DNS leaks on a phone can use the same test page in its browser.

What does a clean leak test not prove?

It shows the tunnel carries lookups and traffic; it does not make you hidden from the sites you visit. A personal VPN hides traffic from the local network and the internet provider, not from the sites visited: every connection leaves through one IP address rented by one account, so it is a private tunnel, not anonymity. Cookies and accounts identify a browser through any tunnel.

The privacy limits page sets this out. For traffic that must never leave outside the tunnel, use the client's blocking option, explained in the kill switch page. TunnelVPS read the wg-quick manual on 16 November 2026: its example blocks unencrypted packets with iptables rules.

DNS leak questions

What is the best way to check a VPN for DNS leaks in 2026?

A test page with the tunnel on and off, plus a look at the DNS = and AllowedIPs lines of each client file.

Does a split tunnel leak DNS?

It can. If the resolver's address is outside AllowedIPs, lookups go around the tunnel. Keep the resolver inside the routed ranges.

Can I run my own resolver on the server?

Yes. A resolver or DNS filter on the server, reached at its tunnel address, keeps lookups inside the tunnel. Home is sized for that.

Why does my test still show my provider's resolver?

The client file has no DNS = line, the app ignores it, or the browser uses its own secure DNS setting. Check each in turn.

Do I need to repeat the check?

Yes, after changing the client file, the app or the operating system.

Verdict
  • DNS = plus ::/0 closes the usual DNS and IPv6 leaks on WireGuard.
  • A clean test proves the tunnel works, not that you are hidden from the sites you visit.
Sources (3)
  1. wg-quick(8) manual page (DNS, kill switch example) — man7.org (read 2026-11-16)
  2. WireGuard: Quick Start — WireGuard (read 2026-11-16)
  3. IPv6 Address Prefix Reserved for Documentation (RFC 3849) — IETF (July 2004)

A server with IPv4 and IPv6

Every plan has one IPv4 and an IPv6 /64. Home costs $6.37 a month on 12 months.

From $2.25/mo on 12 months · no KYC

Get a server