07/27/2022 320 People found this article helpful 469,283 Views
With regular Mac OS X/Linux/Windows based client connections, SonicWall can prioritize all DNS traffic over the VPN. However, with iOS based devices (IPhone/iPad/iPod touch) using the SonicWall Mobile Connect client, DNS requests will be sent across the VPN tunnel only when it matches the DNS suffix configured on the NGFW appliance. This is an intended behavior, due to requirements by Apple. When using Split Tunnels, only DNS requests that match the VPN DNS suffix search domains will use the VPN DNS servers. Requests to domains that do not match the VPN DNS suffixes go to the local (3G/WiFi connection) DNS servers.
EXAMPLE: DNS suffix is set to example.com.
Requests to www.example.com will use the remote VPN DNS server. Requests to intranet.corp.example.com will use the remote VPN DNS server. Requests to www.sonicwall.com will use the local DNS server, as configured by the device's WiFi or 3G connection. Requests to intranet.examplecorp.com will use the local DNS server, as configured by the device's WiFi or 3G connection.
NOTE: The DNS suffix on the NGFW appliance can be configured on the SSL VPN | Client Settings page.
This release includes significant user interface changes and many new features that are different from the SonicOS 6.5 and earlier firmware. The below resolution is for customers using SonicOS 7.X firmware.
This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.
The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.