Exium allows you to use your own private DNS server that you can configure in the Exium admin console. This way, remote users who need to access the private applications can access these apps using private/ local domains rather than entering IP addresses.
Exium achieves this by relaying/ proxying the DNS traffic via our DNS server in the Cloud Cybermesh. This way, you get the best of both Worlds:
The DNS traffic flow is shown in the figure below. Your devices always see Exium DNS servers, 172.18.8.100
and 172.19.53.1
in the example below. These DNS servers forward any DNS queries for your internal domains to your DNS servers, 10.10.37.43
and 192.168.21.78
, for example, running on-prem. The devices securely get back response to their DNS queries for both public and private domains.
To change the DNS providers to your private DNS servers, you can edit the settings at the workspace level. Here are the steps:
Step 1: Log into the partner admin console and navigate to the company workspace
Step 2: Click on the workspace profile in the bottom left of the screen.
Step 3: This will bring up the profile info for the workspace as shown in the Figure below. The fourth field on the right is the DNS field. You can add up to two DNS server IP addresses into this field, one after the other, press space tab on the keyboard before entering the second DNS server.
Step4 : After updating DNS servers, Click on Save.
Your DNS traffic is now fully secured while resolving both public and private domains.
The DNS suffix identifies the domain name (for example, "exium.net") that is appended to an unqualified host name to obtain a fully qualified domain name (FQDN) suitable for a DNS name query. For example, if DNS Suffix is set as exium.net and end users connected to CyberMesh can do ssh or ping to service.exium.net, just by typing service like ssh service or ping service.
To change the DNS providers to your private DNS servers, you can edit the settings at the workspace level. Here are the steps:
Step 1: Log into the partner admin console and navigate to the company workspace
Step 2: Click on the workspace profile in the bottom left of the screen.
Step 3: This will bring up the profile info for the workspace as shown in the Figure below. The fifth field on the right is the DNS Suffix field. You can add DNS Suffix.
Step4 : After updating DNS Suffix, Click on Save.
Your DNS Suffix automatically gets appended to unqualified host names.
When you configure private DNS servers, you can configure and apply Zero-Trust security policies to your private domains the same way you apply security policies to public domains for Web and SaaS Security.
For example you may have two local apps:
You may like to give access to all employees to the application domain app.mycompany.local
and give access to only developer group for the database private domain db.mycompany.local
You can define private domain policies at workspace, group and at user level. To create private domain policies policies, Follow below steps
The screenshot below the case where we are blocking access to the private domain app.exium.local
for the group “US Team”.
After adding this policy, all the users in group “US Team” will not have access to app.exium.local.
To learn more about implementing SASE, XDR, IAM, and GRC for your organization and explore tailored solutions that meet your unique requirements, contact Exium at partners@exium.net for a consultation or demonstration. If you are ready to get started, check out our testing and onboarding process.