We need some help to solve the following issue. When connecting the Pulse Secure Client (18.104.22.16843), 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.
... View more