Pulse Secure Client - Registering DNS

[KAS]

• FQDN Split tunneling does not work at all.  Endpoints are left in a broken state where internal corporate DNS Servers are set statically on an endpoint.  Users can no longer use their computer until it's brought into the office to have DNS Servers set back to automatic.  (TAC admits this, and suggest that it not even be used)
• Disabling DNS registration at the adapter level isn't really valid either, regardless of GPOs to attempt to disable the setting.  This just 'fixes' the issue when a machine is remote on VPN, but now when back in the office would not register its DNS entries correctly (or at all).

[NetworkBod]

Hi Everyone, same issues here since enabling Split-tunneling using FQDN a few weeks ago. Is it best just to not use FQDN at all? Did anyone find a solution to this issue or have any confirmation from Pulse that they are investigating further? Regards.

[zanyterp]

using FQDN has difficulty, yes; if it is not needed for business continuity and ease, IP is preferred. if FQDN is needed for continuity and ensuring access, it should be used.
there have been difficulties with it, yes, and we are working on solutions. please open a case with support as-needed for further discussion

[Pulse-60bpm]

Hey KAS,

You seemed to put a lot of effort into this, did you come up with a solution?  Really curious as this is affecting us in a bad way.  We use FortinetSSO and the multiple entries in DNS are causing havoc withour staff.

THanks