GhostMesh
DownloadServersConnection checkSRSPFAQPricingBlog
Login
GhostMesh

© 2026 SRS Conglomerate. All rights reserved.

Service StatusDocumentationSecurityTerms & ConditionsTransparency reportPrivacy policy
Home/Guides/DNS leaks: check, understand, fix
WindowsAndroidBrowser

DNS leaks: check, understand, fix

DNS translates domain names into addresses. A DNS leak means those lookups go outside the VPN path and reveal browsing intent to a network you did not expect.

Updated
May 20, 2026
Published
Apr 6, 2026
Reviewed by
GhostMesh Network Team
intermediate
10 min read
DNS leaks: check, understand, fix — GhostMesh

Quick answer

Connect the VPN, run a DNS leak test, compare resolver ownership with your selected route, then repeat with browser secure DNS, Android Private DNS, and third-party DNS tools disabled if results are confusing.

Download for WindowsDownload from Google PlayView pricing

Start with the scope

Decide whether the problem affects one site, one browser, one app, one network, or all traffic. Scope is the fastest way to avoid changing the wrong setting.

Record the direct result before connecting the VPN, then repeat the same test after connecting GhostMesh.

Run controlled checks

Change one variable at a time: DNS, server location, browser secure DNS, Private DNS on Android, or split tunneling rules.

If a result changes only in one browser or one network, the VPN may not be the root cause.

Checklist

  • ✓Record baseline
  • ✓Connect GhostMesh
  • ✓Run the same test again
  • ✓Change one setting at a time

Read the symptoms

A DNS-only failure means IP endpoints may still work while domains fail. A route or firewall failure usually affects all apps.

Connection resets can point to browser state, MTU, network filtering, or a route that only affects one destination.

SymptomWhere to look
Domains fail, IP worksDNS
All apps failRoute, firewall, kill switch, captive portal
One site resetsSite policy, CDN path, DPI, MTU
Only Android differsPrivate DNS or battery policy

When to contact support

Send platform, app version, selected server, network type, and screenshots of the test results. Avoid passwords, tokens, or private page content.

A timestamp plus direct-vs-VPN comparison usually gives support enough context to start.

FAQ

Should I reinstall first?

No. Reinstalling rarely identifies DNS, route, or network scope. Run the small checks first.

What is the most useful support detail?

Platform, app version, server, network type, and the exact test result before and after VPN.

Contents

  1. Start with the scope
  2. Run controlled checks
  3. Read the symptoms
  4. When to contact support

Read next

Related guides

  • 10 minHow to check DNS, IPv6, and WebRTC leaksRun three tests: DNS resolvers, IPv6 exposure, and WebRTC local/public IP exposure. Compare results before and after connecting the VPN, then change only one browser or OS setting at a time.Open
  • 9 minPrivate DNS on Android and VPN: what can go wrongHow Private DNS affects VPN routing, DNS leak tests, captive portals, and Android diagnostics.Open
  • 7 minKill switch: what happens when the VPN dropsWhen to use Kill Switch, what it blocks, and how to test that traffic does not bypass the VPN.Open
  • 8 minVPN for Windows 10 and 11: safe setup and checksInstaller checks, SHA256 verification, SmartScreen, DNS, and first Windows troubleshooting steps.Open