Plain VPN

How to Check a VPN DNS Leak Against the Expected Resolver

简体中文

A DNS test can show a provider name, but first establish which resolver should handle the lookup. Your VPN profile, browser settings, and work policies can all matter. Use that expectation when you interpret the result.

About 2 min read

How to run and read a VPN DNS leak test

Use the same trusted test page, device and browser to record the DNS resolvers before and after connecting. If you see an unexpected resolver, check the VPN client’s expected DNS behavior and the browser’s secure DNS settings. Repeat after switching VPN servers. Treat a resolver name as a clue and compare the result with your public IP test.

Related guide: How to Check Your Public IP Before and After Connecting to a VPN

Write down the expected DNS path

SetupWhat can choose the resolver
Device-wide VPNThe VPN client or operating system
Browser encrypted DNSBrowser policy and fallback behaviour
An internal work domainDomain-specific enterprise rules
An app outside the tunnelThe app and underlying network

One resolver service can use several addresses. DNS over HTTPS describes how a query is transported to a resolver. The provider's identity and the network route are separate observations. Check the product documentation or ask IT what to expect.

Compare on a trusted network

  1. Choose a trusted public test and a known browser profile.
  2. Use the permitted baseline and record the displayed resolver, time, and browser.
  3. Connect the VPN and repeat. Note whether browser encrypted DNS is enabled.
  4. Compare the observations with the documented policy and repeat with another trusted source if useful.

Keep internal names out of third-party test pages. The test provider receives your request, so use public content. Caches and browser profiles can change results. Vary one condition at a time.

Interpret an unexpected resolver

If the resolver has another provider's name, check whether the browser chose it or the VPN provider documents that service. If it matches your baseline ISP, check whether the browser is covered and what the VPN promises. Work profiles can apply different rules to internal domains. Let the administrator verify those domains with approved tools.

Capture the difference for support

Give the operating system, client and browser versions, expected resolver, and observed result. Say which app you used to test. Leave internal names, keys, and unrelated records out of the report. Ask the provider which browser and client configuration it supports.

Frequently asked questions

Does encrypted DNS always travel through the VPN?

The encryption and routing choices are separate. Check the browser, operating system, and VPN policies.

Can a public IP test verify DNS?

It measures the exit of that request. Use a separate DNS check to verify the resolver.

Sources