![pulse secure client proxy dns pulse secure client proxy dns](https://www.pulsesecure.net/base/images/kb-images/library/CUSTOMERSERVICE/BK18241/bk18241.jpg)
![pulse secure client proxy dns pulse secure client proxy dns](https://i2.wp.com/thevpn.guru/wp-content/uploads/2014/03/Transparent-Proxy-VPN1.png)
The PCS DNS servers resolve the PCS hostname to an internal IP address after the VPN tunnel is launched and the PCS’s internal gateway router does not have a route to the PCS's internal IP address or if the PCS's DNS servers cannot resolve the PCS hostname at all. PCS hostname does not resolve or there is no route.Roaming Session can be enabled\disabled by going to Role > Session Options: This will add an unnecessary load to the PCS device. However, all traffic will now go through the VPN tunnel instead of the external interface of PCS's web server. If "Roaming Session" is Enabled - The later connection to the browser from the VPN IP to PCS's internal interface will not cause the session to be terminated. Since the roaming session is disabled, the source IP change will result in a disconnect. The connection will come from the VPN IP 192.168.36.2 is configured to go through the VPN tunnel. If "Roaming Session” is Disabled - When the VPN tunnel made a connection to the browser to PCS's Internal interface (for example 192.168.36.2), after the tunnel has been started, the PCS will register a source IP change as the connection is now coming from the VPN Tunnel IP instead of the WAN IP. If the PCS DNS servers resolve the PCS hostname to an internal IP address after the VPN tunnel is launched, then the following may occur depending on what Roaming Option you have configured: