Auto-switching servers by selecting country or continent in config generator?

[Anon23978 0]

Hello,

From the config generator help section, the following line indicates that the intermediate country or continent server will auto-switch endpoints should the current / active endpoint go down or have problems:
 

Quote

Selecting servers by country or contintents will allow your VPN client to switch automatically between servers. This gives you the significant comfort that in case of an AirVPN server unavailability, a working one will be picked for connection: no need for your intervention.

I run the native Wireguard implementation on Linux, so I simply use the configs as they are provided. For example, the generated "United States" config points to us3.vpn.airdns.org as its endpoint, which then routes the connection to an actual endpoint?
However, when the actual endpoint server encounters packet loss, us3.vpn.airdns.org has not automatically changed endpoints -- isn't it supposed to?
If so, what are the trigger conditions for it to make a change, and how long does it usually take to change to another endpoint server?

Thank you.

[OpenSourcerer 1445]

13 hours ago, Anon23978 said:

For example, the generated "United States" config points to us3.vpn.airdns.org as its endpoint, which then routes the connection to an actual endpoint?

ccX.vpn.airdns.org always points to the "best" server in the cc region. It's a DNS record updated every five minutes, so there is no routing done anywhere.
 

13 hours ago, Anon23978 said:

However, when the actual endpoint server encounters packet loss, us3.vpn.airdns.org has not automatically changed endpoints -- isn't it supposed to?

It's not instantaneous and depends on the AirVPN/AirDNS infrastructure (for updating this record), caches on your computer or network and how the caches/DNS servers are configured. In the case of OpenVPN the previously used remote address is even preserved between connection attempts to reduce DNS lookups, so the only way to force it to look up the name again is to terminate and relaunch OpenVPN completely. A similar thing may be happening with Wireguard.

[Anon23978 0]

49 minutes ago, OpenSourcerer said:

ccX.vpn.airdns.org always points to the "best" server in the cc region. It's a DNS record updated every five minutes, so there is no routing done anywhere.
 
It's not instantaneous and depends on the AirVPN/AirDNS infrastructure (for updating this record), caches on your computer or network and how the caches/DNS servers are configured. In the case of OpenVPN the previously used remote address is even preserved between connection attempts to reduce DNS lookups, so the only way to force it to look up the name again is to terminate and relaunch OpenVPN completely. A similar thing may be happening with Wireguard.

I see. Thank you for the explanation. I just wanted to make sure there was nothing (else) on my end that I needed to do in order to facilitate the auto-switching. It sounds like leaving the already established Wireguard connection alone should Just Workᵀᴹ.

[OpenSourcerer 1445]

2 hours ago, Anon23978 said:

It sounds like leaving the already established Wireguard connection alone should Just Workᵀᴹ. 

Most probably.

[Air4141841 25]

I posted previously in using my opnsense router. and a country as posted above: us3.vpn.airdns.org

 I checked my team viewer account and my devices on the airvpn tunnel were offline.  
I came home and checked the airvpn server stats and the server I was connected to previously for a few weeks was down.   and it did not "seemlessly". reconnect as wireguard is suppose too.

I moved back to openvpn briefly then switched back to wireguard again.    to my knowledge and monitoring of my devices it hasn't gone back offline again.    but at that time it did not reconnect like it was suppose to, rather frustrating