DNS and a VPN often appear together in connection settings, but they do different jobs. DNS helps an application find information associated with a domain name. A VPN changes the route taken by the traffic it covers. Changing a DNS resolver is not the same as turning on a VPN.
DNS answers questions about names
When an application needs an address for a hostname, it can ask a DNS resolver. An A record contains an IPv4 address, while an AAAA record contains an IPv6 address. Other record types serve different purposes: MX records identify mail servers and NS records identify nameservers.
Try the DNS lookup tool with a public domain. It asks the selected public resolver for records and shows the response. The result describes that domain; it does not describe the path every application on your phone uses to reach it.
A VPN changes the route
A VPN routes covered traffic through a VPN server. DNS requests may travel through that connection too, depending on the VPN, device and application configuration. An app or browser with its own resolver settings can add another layer to investigate.
Using an encrypted DNS service protects the DNS exchange along that service’s supported path. It does not, by itself, route your web browsing through a VPN or change the public IP websites see. These are separate properties to check.
Why answers can differ
Two DNS resolvers can return different answers because of caching or how a service directs users to its infrastructure. After a record changes, a resolver may continue serving a cached value until its lifetime expires. One response is not necessarily wrong just because it differs from another.
For a domain you manage, use the DNS propagation checker to compare actual responses from available probes. Use DNS trace to investigate delegation. These checks help answer questions about the domain’s DNS, rather than your VPN’s privacy behavior.
Why this DNS lookup is not a leak test
VVPN’s record tool deliberately contacts the provider you select, using DNS over HTTPS. It does not discover your browser’s usual resolver or monitor DNS requests from other apps. A successful response means the chosen lookup worked; it cannot establish that all your DNS traffic stays inside a VPN.
The authenticated-data flag shown in a DNS response is also narrower than a safety score. Google’s API documentation describes it as the resolver’s indication that the response data was validated. It does not certify that a website is trustworthy or that a VPN is configured correctly.
Pick the check that matches your question
- What address does this website see? Use the IP checker.
- Where does this domain point? Use DNS lookup and select the relevant record type.
- Have different locations picked up my DNS change? Use DNS propagation checks, noting the reported locations and failures.
- Who is the domain’s registrar? Use WHOIS/RDAP lookup. Registration data is separate from traffic routing.
To start using VVPN itself, follow the Android or iPhone guide. Keep connection checks and domain troubleshooting separate so each result answers a clear question.
