TamemJ

IT Support Portal

ServiceNow-style demo portal

Affiliate Disclosure

Some recommendations may include affiliate links. If you purchase through these links, the site may earn a commission at no additional cost to you. Recommendations are still selected for fit, safety, and support relevance.

VPN Split-Tunnel DNS Mismatch (Internal Names Fail)

Estimated time

10-20 min

Severity: HighAdmin RequiredEnv: BothNetworking • Corporate VPN

Author & Verification

Tamem J

IT Solutions Engineer

Last verified: March 3, 2026

Runbooks and troubleshooting guides are reviewed for enterprise-safe usage and avoid security bypass patterns.

Tested on Windows 11 23H2Tested on macOS Sequoia 15

Trust Signals

No ratings yet

0 total helpfulness votes

  • • Enterprise Microsoft 365 Administration
  • • Endpoint Management (Intune, Jamf, Kandji)
  • • Identity & Access (Entra ID, Okta)

Symptoms of vpn connected but no internet

  • VPN is connected but internal hostnames do not resolve.
  • Internal resources work by IP but fail by DNS name.
  • Issue varies after reconnect or network changes.

Likely Causes of vpn connected but no internet

  • DNS servers/search suffixes not applied correctly via tunnel.
  • Local DNS overrides enterprise resolution path.
  • Split-tunnel route policy and DNS scope mismatch.

Interactive Decision Tree

ITIL-style triage path powered by state machine logic.

How to Fix: vpn connected but no internet

Accordion runbook sections

  1. 1

    Confirm scope, user impact, and reproduction

    Info
    v

    Document whether the issue affects one user, multiple users, or multiple devices. Confirm exact error messages, recent changes (password reset, update, network change), and whether the same issue reproduces in web vs desktop workflows where applicable.

  2. 2

    Validate prerequisites and application/session state

    Info
    v

    Confirm the user is signed in with the correct corporate account, system time is accurate, network/VPN connectivity is stable, and the application is not running in offline or limited mode.

  3. 3

    Run safe diagnostics from the Commands section

    Command
    v

    Use the command snippets below to collect non-destructive diagnostics. Capture output in the ticket when escalation may be required. Avoid deleting profiles, cached credentials, or managed app data unless the runbook or admin approval explicitly allows it.

  4. 4

    Apply safe remediation steps

    Info
    v
    • Capture DNS server/search suffix state while VPN is active.
    • Test internal resources by hostname and IP for comparison.
    • Reconnect VPN and compare route/DNS outputs.
    • Escalate for profile-level DNS/split-tunnel policy correction.
  5. 5

    Escalate when access, policy, or security controls are involved

    WarningAdmin required
    v
    • Multiple users on same VPN profile are affected.
    • Issue started after VPN profile or client updates.
    • Requested workaround bypasses managed security controls.

Commands

Copyable diagnostic or remediation commands (1 snippet).

Split-tunnel DNS diagnostics

CLI

# Windows
ipconfig /all
Resolve-DnsName intranet.company.local
route print

# macOS
scutil --dns
nslookup intranet.company.local
netstat -rn

When to Contact IT / Security

  • Multiple users on same VPN profile are affected.
  • Issue started after VPN profile or client updates.
  • Requested workaround bypasses managed security controls.

Recommended Partners for This Topic

Selected from your affiliate registry based on this article's category, product family, and tags.

Disclosure: Active partner links may generate commission with no additional user cost.

Related Exact-Match Queries

Internal fix guides aligned to high-intent search phrases.

Was this helpful?

Your response is stored locally in this browser for demo analytics.

Related Articles