Confirm Your Expected Route
DNS translates domain names into network addresses. If you expect both traffic to a website and its DNS lookups to use a specific route, check your client's routing rules, system DNS settings, and browser's secure DNS settings. Some traffic may intentionally use your local network under the rules, so a DNS resolver in a different region doesn't by itself indicate a leak.
- Review your client's DNS settings. Make sure the DNS mode matches your current connection mode, and check where local resolution, remote resolution, and rule-based routing apply. Save your existing settings before making changes so you can restore them if needed.
- Check your browser and system. Browser-based encrypted DNS, custom system resolvers, and other network tools can change the DNS route. Check for settings that override your client's configuration; you don't need to disable encrypted DNS just to test.
- Compare DNS results with the target app. If you use a reputable DNS testing tool separately, check which resolver handled the request and compare it with your selected DNS setup. Distributed DNS networks may show a location different from your public IP, so interpret the result alongside your configuration.
- Verify again after making changes. Follow your operating system or client's instructions to clear the DNS cache, reopen the target app, then check your public IP and DNS route again. Refreshing this page alone won't clear every app's DNS cache.
A public IP location that matches your expectations confirms only that this lookup used the expected route. Check web traffic, DNS resolution, and other app connections separately.
For setup and connection steps, see our Guides. If you're having connection issues, see Frequently Asked Questions. When contacting support, describe your network environment, client mode, and the issue. Don't send your password or full subscription link.