CloudConnexa: Allow DNS Resolution to Local Resources

Overview

When a user device or Connector is connected to CloudConnexa, DNS queries are routed through the CloudConnexa DNS Proxy. As a result, DNS requests intended for local network resources may fail to resolve if those resources can only be resolved by a local DNS server.

To allow DNS resolution of local resources, you can use one of the following options.

Option 1: Disable CloudConnexa DNS Proxy Globally

You can disable the CloudConnexa DNS Proxy for the entire WPC.

1. Sign in to the CloudConnexa administration portal for your CloudID.

2. Navigate to Settings → DNS. 

3. Expand Advanced Configuration.

   • DNS Proxy displays as enabled. 

4. Select Edit DNS Server Details.

5. Disable the DNS Proxy toggle and confirm your changes.

6. Select Update to confirm your changes.

Warning

This is a global setting that affects all connected users and Connectors. When DNS Proxy is disabled, the following features become unavailable:

• DNS Servers

• Applications for Networks and Hosts

• Cyber Shield Domain Filtering

• DNS Records

• DNS Zones

• AppHub Applications

Consider the impact on your environment before disabling DNS Proxy globally.

Option 2: Disable DNS Proxy for a Specific Device or Connector

If you need local DNS resolution for only a specific device or Connector, OpenVPN Support can disable DNS Proxy on a per-device basis.

Submit a support ticket and include the following:

• Cloud ID

• User or Connector name

• Connector type (Host or Network)

• Tunnel IP address

After the ticket is submitted, the OpenVPN Support team will apply the change on the backend and confirm once completed.

Notes

• This change only affects the specified device or Connector.

• All other users and Connectors continue using the CloudConnexa DNS Proxy and retain DNS-related features.

• We recommend this approach when only a small number of devices require local DNS resolution.