First, Distinguish Exit IPs from DNS Lookups
Before a browser visits a site, it usually looks up the domain name to find its network address. Website traffic may go through a proxy while DNS lookups are still handled by your local network. What to expect depends on your client’s DNS mode, routing rules, and the browser’s own Secure DNS settings.
- Before connecting, note the DNS settings used by your system, browser, and client. Don’t rely only on the resolver’s name or location to decide whether a leak is occurring.
- After connecting, check your client’s DNS interception settings and lookup route. If your client provides diagnostic logs, check which resolver handled the domain lookups and whether they followed the expected route through the proxy.
- Check whether your browser’s Secure DNS settings override the system configuration. Coordinate these settings using your client’s instructions. Avoid changing several settings at once, so you can identify what caused any difference.
- For further verification, use a DNS testing tool that clearly identifies its resolvers and testing method. Compare results before and after connecting, and consider your routing rules. This page does not automatically send requests to third-party testing services.
A local network resolver appearing in the results is a clue to investigate, not a definitive conclusion. Organization networks, independent browser lookups, and intentional direct-routing rules can all affect the results. If you’re unsure, use the support ticket portal to share your operating system, connection method, and the issue you’re seeing. Don’t include passwords or full subscription links.