Is the only way around this to allow these clients access to a LAN DNS server, and just take the hit that we'll be providing their DNS services while they're connected? Perhaps we could provide our internal DNS as primary and Googles as a secondary? In these situations of course, the DNS lookups fail. However the overall settings of the SSLVPN is for anyone connected to use our internal DNS servers for all DNS lookups. This means that in one or two cases, we don't want the client to access our DNS servers. However we have one or two users and associates who are using their own devices, so for these users we tailor down the IP addresses that they are allowed to talk to over the VPN. In the Sonicwall itself you specify the DNS servers you want your clients to use while they're connected to the VPN, so we specify two of our internal DNS servers, so that queries are resolved as they would be if the client was local.įor full-on staff members with their own domain-joined laptops, this isn't a problem. We use Sonicwalls as our firewalls, and they provide SSL-VPN functionality using their NetExtender software, which is installed on clients wanting to connect to our LAN. Wanted to throw a question open to see if anyone is in a similar situation as I have, and if so, how they're handling it:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |