I do have 1 Peplink 380 with 2 Internet connections on WAN 1 and WAN 2.
I both WAN, I did configured DDNS (with dyndns.org) with the same configuration.
The idea is to be able to remotely reach my internal network using a single domain.
So, DDNS server should be always updated with at least one of the available public IP’s.
For doing that, Peplink should have a mean to check what is the public IP address configured in the DDNS server, and if that public IP is from a WAN that, for some reason, is not active, it should update the DDNS server configuration with the public IP from one of the other WAN’s that are active.
However, it seams that this is not working this way. The test I made was very simple:
With all WAN’s active, I did checked in my DDNS server account what was the IP address that was set. With this information, I did checked what was the correspondent WAN connection and simply unplugged the cable.
Peplink gets the information that the WAN connection is down (no cable detected), but it doesn’t update the DDNS server with the IP from one of the other active WAN’s.
Does anyone already had similar problem?
Any suggestion on how to solve this?