Fast DynamicDNS updates if OPNSense behind other router? [solved: works oob]

[nibblerrick]

Hi!

My problem is, I have a router which I have to use (Speedport Hybrid) so OPNSense is behind this router. I can't get a static public IP.
So at the moment DynanimcDNS-check works either with the default interval or a cronjob which can be defined to check e.g. every minute.
I think checking is done with the dyndns-service which is hardcoded. As far as I read they'll block you if you don't have >10min intervals.
So question is, is there anything possible (don't has to be GUI-configurable) to get OPNSense notice an IP-change?
Other methods than check X minutes eventually? Having an open connection to anywhere and recheck when it drops? I really have no idea atm, so I am asking.
10 Minutes doesn't sound so much but if you want e.g. a VPN connected this ten minutes it takes to get the update will everytime be the moment you need it, you know what I mean... :-)

[bartjsmit]

Some posts would suggest that the Speedport Hybrid supports DynDNS. I think you should always run a dynamic DNS updater on the device that holds the public IP, since it will be the first to detect the change.

Bart...

[nibblerrick]

Thanks, yes, it does, but limited. They've done some improvements in the past, but it isn't like the options you get in OPNSense. And I had it sometimes not running reliable. So I try not to rely on the speedport and try to find out if there are other possibilities.

An approach might be to have a connection to somewhere open all the time and when it drops it should check IP change?

[franco]

Hi there,

Normally, Gateway monitoring also provides re-invoke of DynDNS (and RFC 2136) in case the interface is back up and the IP has changed. Do you have Gateway monitoring activated? It's off by default.


Cheers,
Franco

[nibblerrick]

Ok, so this takes some days to test, because on the site where OPNSense is running I just got a static IP. On the site where I have the "problem" there is atm still some other sense running which I will migrate. Hope I can finish it this weekend (quite some stuff configured in the actual appliance and when migrating I like to clean up some things and try to get CARP running).
If the monitoring really re-inkoves the DynDNS that would just be great.
I'll let you know as soon as I migrated all the stuff. Thanks!

[franco]

looking forward to you report

[nibblerrick]

After migrating all the stuff, getting multiWAN to work (seems with gatewaygroups and routing it bevahes a bit different than on pfSense actually) I monitored the process now for a while and it works really great!
Nothing more to say, it just works! Thanks!

[franco]

Cool, thanks for reporting back.