CloudConnexa: DNS Server Use Cases When Network Connector is Deployed

Description 1: The customer who is connected as a VPN user is unable to reach the server via hostname(FILE)


Cause: If you encounter this, It's possible that you are not using Default DNS Suffix from CloudConnexa Portal, check If there's any value set in DNS Suffix from your CloudConnexa Portal > Settings > DNS > DNS Servers > Advanced Configuration > Default DNS Suffix 

Resolution: First, set the DNS Server IP Address from your CloudConnexa Portal > Settings > DNS > DNS Servers > Edit > Choose: Custom > Input the DNS IPv4 Address > Update
CloudConnexa - Change DNS Servers from Default to Custom

Second, set the domain name in Default DNS Suffix to resolve hostname to FDQN names, from your CloudConnexa Portal > Settings > DNS > DNS Servers > Advanced Configuration > Edit > Default DNS Suffix > Input the Domain Name > Update

Once It's set in CloudConnexa, test from your connected VPN user by doing the PING from the command prompt the hostname(FILE) and It should resolve the hostname to FQDN names.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Description 2: The customer would like to use multiple DNS Zone

Resolution: Set the DNS Zone from your CloudConnexa Portal > Settings > DNS > DNS Servers > Advanced Configuration > Edit > DNS Zone> Add the DNS Zone > Update

Once It's set in CloudConnexa, test from your connected VPN user by doing the PING from the command prompt the hostname with added DNS Zone.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Description 3: The customer would like to use local DNS for internet traffic and for company local DOMAIN(nino.local) traffic goes to DNS server provided by VPN

Resolution: First, Disable the DNS Proxy from your CloudConnexa Portal > Settings > DNS > DNS Servers > Advanced Configuration > Edit > DNS Proxy> Disable > Update
NOTE: When DNS Proxy is disabled the following features are not available:

• DNS Servers
• Domain for Networks and Hosts
• Domain filtering on Shield
• DNS Records
• DNS Zones

Second, set the OpenVPN Client Options from your CloudConnexa Portal > Settings >VPN > Advanced Configuration > Edit > OpenVPN Client Options > Add the below > Update
dhcp-option DOMAIN nino.local
dhcp-option DNS 172.31.10.219

Once It's set in CloudConnexa, test from your connected VPN user by doing the PING from the command prompt the local DOMAIN.