FW 1.35 Breaks DynDNS updates?

P4Colin

We have a Flex 100H with 2 WAN connections. On this router, ge2 is the active/primary connection, and ge1 is the backup/passive connection. Previously on 1.32, when the primary connection went down, the DynDNS address updated appropriately to the backup address and routed internet traffic out the backup WAN connection.

After the 1.35 update, we had an outage affecting the primary connection today. While the failover happened and all computers were routed out the backup WAN connection, the DynDNS address did not update. We got error messages about GE1 being "link-down" when this is the backup internet connection that is fully up and operational, and what is being used to route the computers out to the internet:

PeterUK

Might have to do some testing but I did post here about DDNS

More improvements to DDNS Backup Address — Zyxel Community

so if you enable connectivity check on the interface does that work?

also what setting are you using for DDNS? Interface, Custom IP, Public IP or Auto

Edit firmware 1.35

So I have two DDNS
one is Dynu Basic primary Ge2 set for Interface with backup VLAN31 set with Public IP
other is user custom now-dns.com primary Ge2 set for Public IP with backup VLAN31 set with Public IP

With Ge2 interface unplugged they both go to backup interface correctly
with Ge2 set with connectivity check I fail ping upstream from FLEX200H and both DDNS go to backup interface correctly

Zyxel_Melen

Hi @P4Colin

Could you share your configuration file for us to replicate your issue? You may send me a private message with it.