A DNS leak happens when your queries go to your ISP resolver instead of your VPN resolver. Even if your visible IP changes, leaked DNS can still expose provider and location patterns. This page is a written walkthrough: it explains what a leak is, points you to the tools that run the actual checks, and shows how to interpret the result.
A DNS leak in a VPN means the website lookup part of your traffic is not following the same protected path as your public IP. The VPN may hide your IP address, but your resolver can still reveal your ISP, network region, or a third-party DNS provider you did not intend to use.
This is why a DNS leak test belongs next to an IP check. The IP result answers "what address do websites see?" The DNS result answers "who resolves the domains I visit?"
After changes, run the same before/after checks again. You want consistent VPN indicators across IP, ASN, and DNS context.
Most DNS leaks fall into one of four categories. Understanding which one applies helps you fix it faster instead of guessing at settings.
After running a before/after comparison, you will see one of these patterns. Each one tells you something different about your setup.
If ISP resolvers still appear after connecting your VPN, the tunnel is not capturing DNS traffic. Reconnect, disable browser DoH if needed, and use a provider with built-in DNS leak protection.