icon-zapp.svg
Client Connector

Resolving Zscaler Client Connector Linux 1.2 DNS Configuration Issues for VPNs

Zscaler Client Connector for Linux 1.2 requires changes to the DNS configuration for older third-party VPNs, like Pulse Secure and Cisco AnyConnect, in order for it to work for ZIA only mode. These changes are not required if you are using both ZIA and ZPA or if you are using modern VPN clients like Openconnect.

Complete the following to resolve the issue:

  1. Run command resolvectl or systemd-resolve --status to identify the physical network interface's DNS search domains. This information will be required later.

You must complete this step prior to connecting to the VPN server.

  1. Connect to the VPN server and log in.
  2. Run the ifconfig command to identify the VPN network interface name (e.g., tun0 for Pulse Secure).
  3. Run command cat /etc/resolv.conf to gather the VPN name server and search domain information.
    1. Find the IP addresses for the VPN name server in the nameserver lines. Ignore the 127.0.0.53 IP address in the nameserver line.
    2. Find the domains in the search line for the VPN domain names. Ignore the physical network interface’s search domains identified in step 1.

In the following example, the VPN nameserver IPs are 10.11.12.13 and 10.11.12.14, and the domain is corp.testco.com. They are highlighted in green.

$ cat /etc/resolv.conf 
search corp.testco.com localdomain 
nameserver 10.11.12.13 
nameserver 10.11.12.14 
nameserver 127.0.0.53
  1. Run the /opt/zscaler/scripts/config_vpn_dns.sh script with root permission using the information gathered in steps 3 and 4. Use the command format: sudo ./vpn_dns_config.sh <vpn_interface_name> <vpn_name_server> <vpn_search_domain>.

If either <vpn_name_server> or <vpn_search_domain> have multiple entries, they should be separated by a space with quotation marks on either side of all the entries.

For example:

sudo ./config_vpn_dns.sh tun0 "10.11.12.13 10.11.12.14" corp.testco.com
Related Articles
AppArmor Causes Auto-Upgrade to Zscaler Client Connector version 3.7.1 for Linux to FailZscaler Client Connector Errors Zscaler Client Connector: Windows Registry KeysZscaler Client Connector: Connection Status ErrorsZscaler Client Connector: ZPA Authentication ErrorsCaptive Portal Sign-In Fails for Chromebook UsersZscaler Client Connector Displays Blank PageFirewall Posture Check Failure on macOS SequoiaMicrosoft Outlook and Microsoft Teams Not AccessibleLogin Failure in Zscaler Client Connector for Android on ChromeOS version 1.12 Browser-Based Authentication Fails When Using Certain Browsers to Launch Zscaler Client Connector for Linux and WindowsDNS Request Failure in Zscaler Client Connector version 4.1.0.89DNS Resolution Failure in Zscaler Client Connector for Android on ChromeOS version 1.12Upgrading to Zscaler Client Connector 3.7 for WindowsMissing Zscaler Client Connector GNOME Tray icon for LinuxUpgrading to Windows 10, Version 2004Supporting M1 ProcessorsUpgrading to macOS Big SurUpgrading to macOS CatalinaUpgrading to Android 10Using Zscaler Client Connector with Cisco AnyConnect on macOS CatalinaUsing the Unauthorized Modification Device Posture ProfileResolving Update Issues to Zscaler Client Connector 1.4.3Login Failures with Zscaler Client Connector Using Active DirectoryDowngrading Zscaler Client Connector to an Earlier VersionResolving Zscaler Client Connector Linux 1.2 DNS Configuration Issues for VPNsResolving Auto-Update Issues for Zscaler Client Connector Linux 1.2Upgrading to Zscaler Client Connector version 1.9 for Android