Legacy DDNS retiring without a replacement for URL callbacks?

[chemlud]

Code Select Expand

cat /var/tmp/ddclient_opn.status

is always empty, but adding a "." or "1" with nano doesn't help, after switching to OPNsense as backend it's always empty again (same error in log). Editing the file after switching to backend OPNsense results in no new log entries ("debug" level) and apparently triggers no IP updates to DYNDNS services.

Deleting

"/var/tmp/ddclient.cache"

(alone or in combination with /var/tmp/ddclient_opn.status) doesn't help either, as recommended here

https://github.com/opnsense/plugins/issues/3344

by sfdementor.

The commands to downgrade affects all plugins? I don't see any reference to ddclient in the commands?!?

[franco]

Sorry, to downgrade a plugin you need to select the proper one by changing the directory. I've fixed the previous post.


Cheers,
Franco

[chemlud]

I had a look at this ddns.cache file (while switched to ddclient):

The entry for spdyn shows no ip=... and mtime=0 while for other dyndns providers the correct IP and a non-zero mtime is shown.

But trying to edit the file with nano is not possible, everything is full of artefacts when trying to enter text. Is nano broken? or my serial console with minicom (2.8, opensuse tumbleweed)?

[chemlud]

... I switched the ddclient to 1.9_2 with the commands outlined above, hope that stops the 5 min interval update attempts at SPdyn...

[chemlud]

Is it possible to lock ddclient on a 22.7.11 before upgrading to 23.1 or will an upgrade remove all package locks?

[franco]

Locks are not possible through major upgrades because they could make the upgrade fail.


Cheers,
Franco

[chemlud]

To sum up the current situation with dynDNS in OPNsense:

- Old plugin is "legacy" (although working) and will be discontiuned with 23.7.

- "New" plugin is discontinued by developer, no help in sight. Bugs since 23.1 spam some dyndns provider with unnecessary updates every 5 min.

- New OPNsense (python) script can't be started from GUI, currently.

This is not very positive overall, to say the least...

[franco]

I think that sums it up nicely. A lot of complains, no one willing to do better. This is how open source dies (in the case of DynDNS).


Cheers,
Franco

[chemlud]

Again: I'm a user, not a coder...

[franco]

Right. I'm just trying to state the facts for the whole situation from user to software to developer.


Cheers,
Franco

[joecool]

franco:  I have a php script that I use via the "Update URL" line in the legacy provider that handles PorkBun.  They use an API to do ddns instead of standard protocols.  Would this be helpful in any way?

[chemlud]

@franco, what would be a viable way forward to keep dynDNS functional in 23.7 and beyond?

No question there is a significant number of users vitally relying on this feature as can be seen from the plethora of posts and threads on this topic since the discontinuation of the "legacy" plugin has been announced. Let's start the discussion early, as 23.7 not far away...

[chemlud]

So no discussion means.... no discussion?

Could we figure out an amount of money needed to be raised by the community to keep dynDNS updates via OPNsense functional 23.7 and beyond?

There is not that much time left to come up with a solution, I guess...

[joecool]

The time has come and 23.7 just got released but we aren't any closer here.  I looked online and pfsense just added Porkbun support here:  https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/d9d91d5df28c235baba4bfe3cc7c792037df35c2

Is that something that could be ported over?

[franco]

> The time has come and 23.7 just got released but we aren't any closer here.

Not very nice... and clear progress has been made since March 24 when this was last posted. This is a warning to stay fair.


Cheers,
Franco