Fix DNS Issues

Troubleshooting help

Summary

Websites will not load even though the VPN says connected? It is usually DNS. Reconnect, flush the DNS cache, re-import your config, and test for leaks.

On this page
  1. How to recognize a DNS problem
  2. Quick fixes
  3. Check for a DNS leak
  4. Conflicting software

How to recognize a DNS problem

The VPN shows connected, but websites time out or your browser says the address cannot be found. Apps that use raw IP addresses may still work. That pattern almost always means DNS requests are failing or going to the wrong place.

Quick fixes

  1. Reconnect the tunnel. Turn the VPN off and on. This re-applies the DNS settings from your config.
  2. Flush the DNS cache. On Windows run ipconfig /flushdns in a command prompt. On macOS run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. On phones, toggling airplane mode does the job.
  3. Re-import your config. The config sets your VPN DNS server. Download a fresh copy from the devices page and import it again.

Check for a DNS leak

A DNS leak is the opposite problem: pages load fine, but your DNS requests bypass the VPN and go to your internet provider. That weakens your privacy without any visible error.

Run a leak test while connected and confirm the listed DNS servers belong to the VPN, not your provider. Our DNS leak guide explains how to test and what the results mean.

Conflicting software

Custom DNS tools, ad blockers with their own DNS, and "secure DNS" browser settings can fight with the VPN's DNS. Try disabling them temporarily. If the problem disappears, re-enable them one at a time to find the conflict.

Need help reading your leak test results? Contact support and paste them into the message.

Was this helpful?

Yes, back to the Help Center  ·  No, I still need help