ddclient plugin issue

[kamaradski]

same here I'm increasingly frustrated by the new os-ddclient plugin I also use it with Cloudflare and most of the time it's not working with exactly the same behavior as described by the OP.

os-ddclient 1.9
OPNsense 22.7.6-amd64
FreeBSD 13.1-RELEASE-p2
OpenSSL 1.1.1q 5 Jul 2022

[sp33dy]

i´m really struggling with ddns client(legacy works fine)

i´m trying to get freedns to work but it just wont update
'login=' is an invalid login.
line 4: Invalid Value for keyword 'ip' = ''
WARNING: last updated <never> but last attempt on Tue Nov 8 12:13:41 2022 failed.
FAILED: Could not get freedns update URLs from freedns.afraid.org

any one running freedns and got this working?

[chemlud]

It would be really nice to get some offical statement on the future of DynDNS in opnsense. Apparently there is no active development? At least I see no discussions.

Will one day in the near future the old DynDNS plugin be simply dropped and "deal with it"? Or what is  the plan?

[franco]

The next step, if any, will be announced. The new ddclient 3.10.0 is trapped in limbo in FreeBSD ports and even the original maintainer fears regressions. That doesn't change the fact that the old DynDNS isn't a mess either.

There are no plans to bring about a third plan as from a core perspective DynDNS really is a lost cause from what we've learned in 2022.


Cheers,
Franco

[chemlud]

lost cause: Maybe, but apparently really, really essential this DynDNS stuff for a significant fraction of users, considering the forum threads throughout 2021-22...

Thanks for clarification anyways. Hope this finds a happy ending some day...

[franco]

> significant fraction of users

Possibly rather "significant [for a] fraction of user", but voicing concern over the forum or bug tracker for business-irrelevant features is difficult for us to process in a meaningful way if actual work is attached to it. If we have customer requests we can reconsider a third plan as previously stated.


Cheers,
Franco

[chemlud]

...if the non-paying community is rather irrelevant (donations, forum support) then the least service to this unproductive crowd could be to keep the old plugin in the repo. ;-)

[franco]

That's true in request and action already :)

[chemlud]

correction:

...to keep the old plugin indefinitely in the repo (and remove waring for removal from repo from the Dashboard in the GUI...) :-)

[Patrick M. Hausen]

If it's so essential for enough people, someone should come up with a community plugin. I am sure, @mimugmail will happily integrate it into his repo.

[manilx]

Chiming in here. I today posted my issues with the new plugin also https://forum.opnsense.org/index.php?topic=31015.0
Works once and then has issues.

Upon finding this post I disabled the new plugin and installed the old one. Configured DNSOMatic. And behold works like a charm!

So yes, please keep this plugin in the repo and remove the warning.

[dedi]

Was also pushed to install the new plugin, just to end up with the old plugin one hour later.

[johanDG]

Hello,

Just a small message to say that in my case, despite of the weird error messages about accessing the pid file, the ddclient plugin seems to be working (using no-ip as dynamic dns provider).

The only thing that looks impossible is registering both an ipv4 and ipv6 address using the ddclient plugin (resulting in only ipv6 address to be updated)

Configuration:
Type   opnsense-business   
Version   22.10   
Architecture   amd64   
Flavour   OpenSSL   
Commit   9c48b424b