DNS queries leak around the VPN, internal hostnames do not resolve.
A DNS leak means the client asks the internet resolver for internal names, or private hostnames reach your ISP. On Windows the gotcha lives in DNS Client policy and how interfaces are merged.
Try this first
- 1Check via dnsleaktest.com or an internal page which resolver answers which zone.
- 2Push split DNS via the VPN profile: corp.lan goes to the internal resolver, the rest to public.
- 3On Windows 11 set Force Tunneling and a Trusted DNS suffix, otherwise the client picks the Wi-Fi resolver.
- 4On macOS run scutil --dns to verify which resolver answers each search list, that shows real behaviour.
When to bring us in
You use Azure or AWS private endpoints: without correct split DNS those never work, plan an agreed internal resolver with conditional forwarders.
See also
- VPN will not connect or keeps droppingTwo main causes: your home internet or the VPN server. One quick test separates them.
- VPN connects but corporate folders are unreachableConnection says "green" but your network drives will not open. Almost always a DNS or routing issue.
- Home PC slow on VPN, fast at the officeThree suspects: home internet, VPN server limits, or routing that takes a long detour.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.