Dynamic DNS is still broken

[Sakata_T]

Since last topic got hijacked with VPN stuff that doesn't seem related to this issue, and the issue persists several updates since, remaking this post as a new one.

Since the update to 23.1 early May, the Dynamic DNS is not functioning as it should.

I have 2 WANs, from different carriers. Both are DHCP. I do a lot of work where I'm not in the office, and need to be able to reach the correct WAN reliably.

The Current IP is showing correctly on the status page of the service, but the IPs that are sent to NameCheap are
incorrect. Despite the correct IPs being listed on the settings page for the service, NameCheap is being updated for both "ip1.myoffice.net" and "ip2.myoffice.net" with the IP of WAN1.

I've now lost access to access to WAN2 several times. Each time was due to thinking that an update that was recently pushed has hopefully resolved this issue, turned the DynDNS service back on, and then having it set the records for IP2 to WAN1 instead of WAN2.  Since it often shows that the service appears to be working correctly when I turn it on, I leave it - only to find that at some point it decides to do... whatever it's doing when it breaks.

Is this on the radar to be fixed soon?