Dynamic DNS with multi-WAN broken?

[patrick3000]

I've just spent the past couple of weeks migrating a rather complex setup from PfSense to OPNsense. Everything appears to be working except for one problem. I have two WAN interfaces, a primary and secondary, with a gateway group and failover from the primary to the secondary whenever the primary goes down. I also have dynamic DNS which I use to access the router from the road for a couple of different services (OpenVPN and a Nextcloud server). The problem is that Dynamic DNS always resolves to the IP address of the secondary WAN, even though it's set to resolve to that of the primary WAN.

I found a post on github about this last year at this link: https://github.com/opnsense/plugins/issues/3076. In that post, the commenters referred to this as a bug, but it was never resolved. They talk about how it worked in the the "legacy dynds," but I'm not sure what that plug in is, and it doesn't appear in the most recent version of OPNsense.

I also use No-IP as my dynamic DNS provider, as the commenters in the github thread do, so maybe it's only broken with No-IP, or maybe it's a more general issue. It would be a hassle for me to switch to a different dynamic DNS provider because I would need to change my Nextcloud domain.

Does anyone know anything more about this or have a workaround?

[pjw]

I’m hoping to bump this topic up as I experience the same problem with no clear resolution.

I’m running 23.7_3 production on my router.  I have a multi-WAN setup with the following config:

- Main broadband (cable) on WAN1
- Starlink on WAN2

I have firewall rules to split traffic between the two (work goes out Starlink, rest of house goes out broadband).  The rules are also configured to fail over to the other in the case the link goes down.  Living out in the sticks, this happens more often than not.  The failover works great to keep things uninterrupted, but it seems this breaks my dyndns setup.

I’d like my Dynamic DNS to track my external domain that lives out of the WAN1 connection.  However, when the broadband on WAN1 fails and the firewall fails over to WAN2, my dyndns (managed by ZoneEdit) picks up the Starlink IP address.  The issue is when things fail back (WAN1 is back up) then the IP address doesn’t update, even though Dynamic DNS in OPNsense sees the correct upstream IP.  I don’t know how to kick it to make the update.  Verbose debug logging didn’t show anything obvious to me.

Any thoughts or help would be greatly appreciated.