Hi. I’m wondering if this is the same issue as discussed here …
So far as I know, the DDNS updating issue (particularly, following “preferred” WAN when it returns to good health) has not been addressed.
We and our clients generally use no-ip.com and have found it to be nearly 100% reliable when properly updated. However, suppose there is a situation where one has two WANs. WAN 1 has a high capacity and WAN 2 is a “dog” but serves as a back-up. If WAN 1 fails, the DDNS on WAN 2 will be updated but will usually NOT be updated again once WAN 1 (the one with far greater capacity) returns to good health. So, inbound traffic will use the “dog” WAN even though the good one is performing well.
I’ve looked at the firmware release notes and I don’t see where any changes to this behavior have been discussed.
Same issue?