Firewall Support Center

GlobalProtect Split Tunnel vs Full Tunnel: Routing and DNS Explained

Compare GlobalProtect full and split tunnels with practical routing, DNS, application, and endpoint validation checks.

Full tunnelCorporate and internet traffic use the VPN under the configured policy
Split tunnelSelected traffic uses the VPN and selected traffic exits locally
DNS decisionVerify resolver selection separately for each test name
Illustrative troubleshooting view · Firewall Support Center

Choose the model around the traffic policy

Full tunneling sends the configured user traffic through the VPN gateway. Split tunneling divides traffic between the VPN and local connectivity using supported inclusion or exclusion controls. The choice affects inspection coverage, bandwidth, application behavior, and endpoint access. Define those requirements before building the client configuration.

Keep routing and DNS observable

A client can select the expected route while resolving an internal name incorrectly. It can also obtain the right DNS answer and then send packets down the wrong route. GlobalProtect includes controls for access routes, DNS servers, and supported domain or application behavior. Feature availability varies with client operating system, app release, and licensing. Verify the compatibility matrix for the deployed combination.

Build a simple test matrix

Test destinationExpected observation
Internal application by FQDNInternal DNS answer and VPN path
Internal application by IPVPN route and server connectivity
Public websiteLocal or VPN exit according to the design
Local printerAccess outcome consistent with local-network policy
IPv6 destinationExplicitly verified IPv6 routing and policy behavior

Inspect the Windows endpoint

ipconfig /all
route print -4
route print -6
Resolve-DnsName app.example.com
Test-NetConnection app.example.com -Port 443 -InformationLevel Detailed

Use controlled names and addresses

Replace app.example.com with a test application under your control. Record the DNS answer, selected source address, route, and result. Repeat before connecting, after connecting, and after disconnecting. Compare with a known-good endpoint using the same client configuration. A cached DNS answer can complicate comparisons, so record cache behavior as part of the test.

Common causes of unexpected behavior

An overlapping home subnet can conflict with a corporate route. A user can receive a different gateway client configuration than intended. An application may contact additional domains after its initial login. IPv4 tests can succeed while an IPv6 path fails. Check the configuration actually delivered to the client and the destinations actually used by the application.

Verify the gateway policy too

For VPN-carried traffic, confirm the relevant zones, security rule, destination route, and NAT behavior. For locally excluded traffic, verify the endpoint protections and controls required by the organization. Endpoint traffic enforcement and local-network options can alter expected access, so include those settings in the design review.

Deploy with measurable acceptance criteria

Pilot the configuration with representative operating systems and networks. Test authentication, internal applications, public internet access, video calls, DNS, and reconnect behavior. Preserve the previous client configuration and define a rollback. Document both intended inspection coverage and the measured user experience before expanding the deployment.

Official references

GlobalProtect client settings

GlobalProtect supported features

Endpoint traffic policy enforcement