Athena NGFW (previously known as Network Secure) provides comprehensive protection for every network perimeter, ensuring the safety of your valuable assets, data, and users from emerging threats.
SSL VPN supports resources access only through an Internal DNS server. When there are such application resources, usually, the user will have several DNS servers for internal devices to resolve the domain when accessing the applications. The configuration will allow SSL VPN users to resolve the domain using the defined DNS server. The configuration page is as shown in the following figure.
On the Local DNS page, there are Preferred DNS and Alternate DNS. You only need to configure the Preferred DNS if there is only one internal DNS. After the configuration, the Client PC uses the above DNS servers checkbox to activate the function.
With this feature enabled, it is not allowed to configure the local domain names of resources, and the automatic logout feature will become invalid.
The Local Domain Name of Resource is used if the address used in the resource is an internal domain name and the intranet has a dedicated DNS server for resolution. Add rules in Local Domain Name of Resource so that resolution requests for this part of the domain name are prioritized by the intranet DNS server.
Click Add to enter the Add Domain Name of Resource page as shown below.
Domain Name: Define the domain name of resources to be accessed.
Description: Description of the domain name entry.
1. If the resource application uses an internal domain name and there is an internal DNS server to resolve these domains, adding the Local Domain Name of Resource is recommended to prioritize the internal DNS server resolved. Otherwise, leave the section blank.
2. The maximum supported resource is 100 entries, and only the English alphabet is supported.