31
23.1 Legacy Series / Re: ddclient and ClouDNS
« on: May 10, 2023, 05:05:28 pm »
Thanks for the suggestion. Your workaround would work fne but running only once a day means that I might have to wait upto 24 hours before cloudns updates my DNS record.
I currently use the legacy "Dynamic DNS" plugin. When that is finally removed from OpnSense (this summer?), unless the bug is fixed in the meantime, I would implement a workaround which monitors my external WAN ip address and whenever a change is detected would invoke the ClouDNS supplied script. The workaround would involve using Monit service since I already a service which does something very similar. This way I would have a granularity of the order of minutes and I would not overload ClouDNS with requests when the ip address does not change.
I have opened a ticket on Github for the plugin here: https://github.com/opnsense/plugins/issues/3430
I currently use the legacy "Dynamic DNS" plugin. When that is finally removed from OpnSense (this summer?), unless the bug is fixed in the meantime, I would implement a workaround which monitors my external WAN ip address and whenever a change is detected would invoke the ClouDNS supplied script. The workaround would involve using Monit service since I already a service which does something very similar. This way I would have a granularity of the order of minutes and I would not overload ClouDNS with requests when the ip address does not change.
I have opened a ticket on Github for the plugin here: https://github.com/opnsense/plugins/issues/3430