DNS not working with Mobile connect but working with Netextender on SMA appliances

03/26/2020 33 People found this article helpful 199,067 Views

Download

Print

Share

• LinkedIn
• Twitter
• Facebook
• Email
• Copy URL The link has been copied to clipboard

Description

Cause

Mobile connect DNS will not be used unless suffix list is specified

Resolution

When using the Netextender all requests (regardless of the suffix) will be directed to the DNS servers supplied by the SRA appliance.

When using the Mobile connect however only requests that match the suffix list supplied by the SRA will be sent to the SRA. All other DNS requests that do not match the suffix list will be directed to the public DNS server that is configured for a local connection (Ethernet, Wi-Fi etc.).

Example suffix configuration is shown below (suffix lists can also be configured under local groups and local users) :

In this example the only DNS requests that will go to the 192.168.0.144 (internal DNS server) will be the ones that end with either of the two suffixes:

-          company.com

-          acme.com

All other DNS requests will be sent to a public DNS server configured under other local adapters.

To check the list of Mobile connect DNS servers and the corresponding suffixes please use the following command in the command line interface:

netsh name show effectivepolicy

Related Articles

• SMA1000: How to manage Connect Tunnel client Auto-updates
• Appliance reboot changes the configuration.
• How to secure Virtual Office portal from all external access

Categories

• Secure Mobile Access > SMA 100 Series