This is currently a limitation of the PCS device. Take this into consideration, if you are deploying the PCS SSL VPN in a Linux environment.
For example, on a Ubuntu 9.10 machine, the following behavior is observed when split tunnel mode is enabled (irrespective of the DNS search order configured under the NC Profile on the PCS ):
Before launching NC, the resolve.conf has the following entries:
Implying that all DNS requests would first be sent to server 220.127.116.11 and would fall back to server 18.104.22.168 in the case where server 22.214.171.124 is unreachable for name resolution.
If the PCS DNS setting under NC profile is:
Primary DNS: 10.10.10.10
Secondary DNS: 126.96.36.199
After launching NC, the resolve.conf would be modified as shown below:
Implying that all DNS requests would first be sent to the server 10.10.10.10 and would fall back to 188.8.131.52 in the case when the 10.10.10.10 server is unreachable for name resolution.
After disconnecting NC, resolve.conf is restored with the old entries as shown below: