When i perform a DNS request on the SSL VPN i can see the packet being forwarded, however i dont get a reply. I think it has something to do with SSL VPN not having a default gateway where where the IPSEC does, i may be completely off here but sonicwall has decided its not there problem despite us having a support contract.
In the advanced VPN settings I was able to configure the firewall to assign the Sonicwall's IP as the DNS server to the clients, but that did not resolve the problem. If I have put another DNS server on the network somewhere I can, but I'd like to avoid that if possible. To configure the SonicWALL appliance(s) to obtain the DNS server information automatically, select Obtain DNS Server Address Automatically. To specify DNS servers, select Specify DNS Servers and enter the DNS Server IP addresses. The VPN > DHCP over VPN page allows you to configure a SonicWALL security appliance to obtain an IP address lease from a DHCP server at the other end of a VPN tunnel. In some network deployments, it is desirable to have all VPN networks on one logical IP subnet, and create the appearance of all VPN networks residing in one IP subnet address space. What are the networks configured for your VPNs? Each VPN needs to be aware of the networks it will be connecting to. Your 'Destination Network' settings need to include the other networks so for instance on the 10.25.0.0 network the VPN destinations should include both the 10.100.0.0 network as well as the 10.30.0.0 network. Services: VPN using iPad/iPhone/iPod Touch (using L2TP option on the SonicWall appliance) Feature/Application: This document explains how to configure the iPad/iPhone/iPod Touch (we will refer to the name iPad for the rest of this document) L2TP Client access to the SonicWall WAN GroupVPN SA using the built-in L2TP Server. Jan 18, 2016 · Verify the DNS Server 1 and DNS Server 2 are properly specified. Take note of the setting “User Name and Password Caching” and adjust accordingly to your security policy! Enabling “Create Client Connection Profile” will allow the SonicWALL NetExtender client to save the profile (recommended). DNS traffic is so small that it shouldn't have any discernible effect on your server unless you have the cache set too low. The server's network stack should be configured to look to 127.0.0.1 (or its local address) for DNS resolution, and the service configured with forwarders. Insofar as the Sonicwall relates, you can set it either way.
This article describes on how to configure the SonicWall to resolve internal Domain names and IP addresses. Incorrect configuration could lead to these issues: Unable to resolve local resources. Analyzer /GMS reports show internal Private IPs instead of the machine name.
In this test, a VPN tunnel between two SonicWALL Appliances with VPN functionality, both located behind DSL Connection with dynamic IP-Addresses has been established. As Firmware, Version 6.4 was used. Additionally, an account from a provider offering dynamic DNS translation and a software tool to update Confusion with DNS on Windows server and Sonicwall
VPN_l2tpServerSetup - SonicWall
DNS name resolution when using SonicWall Mobile Connect 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. How can I configure DNS and WINS server settings for VPN Specify the required DNS and WINS servers IP addresses and click OK. How to Test: Use the KB ID 170505850768290 for Global VPN configuration steps and connect a Global VPN client. Once connected, check the DNS and WINS server setting for Virtual Adapter Connection in the PC to make sure it has correct DNS and WINS IP server addresses. Sonicwall VPN - No DNS Resolution - Spiceworks Mar 16, 2020