Local private IP is registering to Domain DNS over VPN

[Larry]

We need some help to solve the following issue.

When connecting the Pulse Secure Client (9.1.8.3143), both VPN IP adress (10.x.x.x) and local private IP (192.168.1.x) are registering to domain DNS. 

Result: the computer could not be reach using it's hostname because NSLOOK is returning both private and VPN IP.

We also notice that the local network adapter (let say the Wireless) is updating they DNS server settings to the domain one after the Pulse Secure connection is establish. 

[kita]

This will depend on the configuration pushed by the administrator.  The admin can enforce either full tunnel or split tunnel.

If you are trying to reach a local subnet and it is going through the tunnel, it is likely enforced by the administrator to not allow access to the local subnet.

To confirm this scenario, you can run a "route print" and see where the 192.168.1.x route is pointed to.  If it is not mentioned, then it will fall under 0.0.0.0 which is likely pointed to the tunnel interface.  If local subnet is required, then discussion with the admin would be needed to see if an exception can be made.