@RVicker do you need redundancy for SSL VPN (in which category you posted) or for Site to Site VPN?
Multiple DNS names might work for SSL VPN (never tested) but for Site to Site (or Tunnel Interface) it will not, you need to define the connections separately.
Customer has multiple Internet services for redundancy.
While you can put in to addresses in the Site-To-Site definition in IPSEC VPN and it will "fail over" from the client end there are reasons to put multiple IPs in the same DNS hostname. Wanting to see if the Sonicwall will "walk" the list of IPs till it gets a connection.
Answers
@RVicker do you need redundancy for SSL VPN (in which category you posted) or for Site to Site VPN?
Multiple DNS names might work for SSL VPN (never tested) but for Site to Site (or Tunnel Interface) it will not, you need to define the connections separately.
--Michael@BWC
Customer has multiple Internet services for redundancy.
While you can put in to addresses in the Site-To-Site definition in IPSEC VPN and it will "fail over" from the client end there are reasons to put multiple IPs in the same DNS hostname. Wanting to see if the Sonicwall will "walk" the list of IPs till it gets a connection.
Hi @RVicker , in the IPSec VPN Advanced make sure you have this enabled to ensure it reconnects using the new resolved IP