Hi guys, We're facing a weird issue. Scenario: VPN tunneling enabled, split tunneling enabled, Route Precedence set as Tunnel routes, Route Monitor disabled. My testing profile's Resource policies for VPN tunneling: access control set to allow any (*.*), connection profile DNS set to 'Search the device's DNS servers first, then client', split-tunneling networks: 10.10.10.0/24. When I connect from Pulse Client on my laptop, I get the IP e.g. 10.50.50.50. Run route print and see that a new entry has been injected, route to 10.10.10.0/24, interface 10.50.50.50, which is totally fine. Then I ping a host of the remote network, e.g. 10.10.10.10, and get reply. If I run nslookup of that host, e.g. mail.contoso.local, I get the right IP, 10.10.10.10. But if I then ping the FQDN mail.contoso.local, it won't get a reply, and then when I check again the laptop routing table, I see that the route to that specific IP has been changed, now there is an entry towards 10.10.10.10 that drives the traffic to my laptop physical WiFi interface IP, instead of keeping the tunnel one. Any idea? Thanks
... View more