DNS Settings and DNS Leaks: What to Check
DNS turns a name such as example.com into an IP address. A browser can have a working connection while DNS requests take a route you did not expect, so “the page opens” and “DNS is configured the way I intended” are not the same test.
Where DNS may be handled
Depending on the operating system and client, DNS can be handled by the system resolver, an encrypted resolver such as DoH/DoT, the proxy core, or a DNS rule inside a TUN setup. The exact path varies by app; do not assume every client treats DNS the same way.
What people mean by a DNS leak
A leak generally means DNS requests go to a resolver outside the path or policy you expected. The implications depend on the setup and resolver. It does not automatically mean the whole connection is unencrypted, but it can reveal the domains being looked up to that resolver.
Troubleshooting without making things worse
First note the current DNS settings. Test several domains, compare proxy and direct mode, and change one option at a time. If a new custom resolver causes failures, return to the previous setting before experimenting further. Avoid copying random DNS addresses from untrusted posts.
If only one domain fails, check whether the site itself or its DNS records are having trouble. If many domains fail but direct IP access works, DNS becomes a stronger suspect.
Related: DNS troubleshooting and IPv4 vs IPv6.