Anyconnect reconnect does not do DNS lookup

[jtennant]

Because of a bug, we have decided to split our HA pairs of FP4115's running ASA into separate devices. The problem I'm seeing now is, when a user is connected to vpn1, and then vpn1 goes down, anyconnect tries to reconnect but only to the ip of vpn1. It does not apprear to be doing a DNS lookup and then trying to hit vpn2 (we put an F5 in front to server up proper available vpn devices). The keepalives seem to be working but without that second dns lookup on the name, the user just sits and waits....

What am I missing?

[Karsten Iwen]

I think you are trying to implement things in a quite uncommon way and that is causing problems. For example, why should Anyconnect to a new DNS request if the name is still cached. But in a different setup, you will likely not face these problems.

Some ways to implement this:

1. VPN-Loadbalancing: You do not need an external loadbalancer, the ASAs implements this natively.
2. Loadbalancing on the F5: Here the client should only see one virtual IP regardless of which or how many devices are behind the loadbalancer.
3. If you want to have two IPs that the client can access, use two FQDNs and configure the second as a backup-server in the AnyConnect client profile.

With all these ways it should work as expected.

[jtennant]

We decide to try your option 3. It appears to be working very well. Thank you very much!