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

Description

DNS requests are not using the Mobile Connect DNS server

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) :

 

Image

 

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

Image

Related Articles

  • SMA100 End of Support No-Charge Replacement FAQ
    Read More
  • SMA1000: Post upgrade to 12.5.0 on AWS and Azure, we show the error Could not retrieve the DNS settings once we log in to AMC/CMS console
    Read More
  • Firmware version required to upgrade to version 12.5.0.
    Read More
not finding your answers?