os-ddclient

[franco]

That's a strange way to continue a thread and virtually nobody had feedback on 1.8 yet which brought a few improvements, although I don't know about "someone with developing skills"

[dinguz]

I thought I'd give ddclient a try after upgrading to 22.7-rc1, as I couldn't get it to work with 22.1
The log file says it can't determine my ip address, however it's shown in the web interface.
Any ideas as to what is wrong?

[hescominsoon]

it's broken..has been for a while...

[franco]

Checkip method "interface" is probably suboptimal on a point to point interface. Feel free to open a bug report with ddclient on this.

But that's why the remote check services exist. Though some of those don't work on HTTPS for whatever reason (dyndns).


Cheers,
Franco

[jclendineng]

Im assuming the legacy dyndns client is going away in the new update? If so I need to migrate all the cloudflare sites to the new system but I dont see a cloudflare API option in the "new" plugin.  How are people managing cloudflare dns updates in this plugin? Also if we are keeping the "legacy" plugin in some form Id prefer that as it just works for all our sites.

[chemlud]

Im assuming the legacy dyndns client is going away in the new update? If so I need to migrate all the cloudflare sites to the new system but I dont see a cloudflare API option in the "new" plugin.  How are people managing cloudflare dns updates in this plugin? Also if we are keeping the "legacy" plugin in some form Id prefer that as it just works for all our sites.

Many, many people have started many, many requests to keep the old but functional plugin. Nobody cares on the dev side. Sad but no way to change. I will stop updating until I have time and opportunity to switch all installs to the new plugin. It's a mess to say the least.

[mightyi]

Can someone direct me to a guide to configure GoDaddy in the new ddclient?  I've been looking everywhere, but so far found nothing helpful!

[SpeakinTelnet]

Many, many people have started many, many requests to keep the old but functional plugin. Nobody cares on the dev side. Sad but no way to change. I will stop updating until I have time and opportunity to switch all installs to the new plugin. It's a mess to say the least.

Came here to see if others had the same complaint, I'm floored. Do you know of any way to keep opnsense updates to security only? Considering that ddclient hasn't received a real update in a while I don't see this beeing addressed in the near future

[dnll]

Can someone direct me to a guide to configure GoDaddy in the new ddclient?  I've been looking everywhere, but so far found nothing helpful!

I'm new to OPNsense (migrating from pfSense) and what I did is install ddclient and use it for Cloudflare DDNS (it works fine after some toying around) and use de legacy dyndns plugin for GoDaddy which is still supported under the latest stable OPNsense version.

I am also looking for GoDaddy to be properly added to the WebUI of ddclient in OPNsense.

[Vesalius]

Im assuming the legacy dyndns client is going away in the new update? If so I need to migrate all the cloudflare sites to the new system but I dont see a cloudflare API option in the "new" plugin.  How are people managing cloudflare dns updates in this plugin? Also if we are keeping the "legacy" plugin in some form Id prefer that as it just works for all our sites.

Many, many people have started many, many requests to keep the old but functional plugin. Nobody cares on the dev side. Sad but no way to change. I will stop updating until I have time and opportunity to switch all installs to the new plugin. It's a mess to say the least.

Came here to see if others had the same complaint, I'm floored. Do you know of any way to keep opnsense updates to security only? Considering that ddclient hasn't received a real update in a while I don't see this beeing addressed in the near future

We keep ending up here even though the dyndns sky is not falling, early in this thread @franco stated OPNsense will not remove a pre-existing legacy dyndns install or configuration on update to 22.7 even if 22.7 no longer includes it. Also, using the example in his post below you will still be able to reinstall the legacy dyndns at the CLI on a new install of 22.7.

https://forum.opnsense.org/index.php?topic=26446.msg130278#msg130278

[opn_nwo]

I'm trying to follow this discussion, but I'm a bit confused. Does os-ddclient in 22.7 supports Cloudflare or not?

[IsaacFL]

I'm trying to follow this discussion, but I'm a bit confused. Does os-ddclient in 22.7 supports Cloudflare or not?

I have gotten it to work, but it only works with the global api and takes a lot of trial and error. 

Use your cloudflare email as the username, global API Key as password.  Use your top level (example.com) domain as zone, then hostnames (ipv4.example.com, host1.example.com).

IPv6 is problematic. There is no way to specify that it is ipv6, so if you have a dual stack (A and AAAA) host, it fails.  You can do as above, with a non-dual stack host (ipv6.example.com), if you use one of the external ipv6 only web methods. But it needs to be a separate entry.

You can force update, by going to command line, and entering: # ddclient -force

The old ddns worked much better. As far as I can tell ipv6 is no longer a priority to opnsense developers as they keep dropping from plugins.

[meyergru]

IPv6 is problematic. There is no way to specify that it is ipv6, so if you have a dual stack (A and AAAA) host, it fails.

That is not entirely correct: I added a switch "allow IPv6" in the advanced options a while ago. If you use that, IPv6 will effectively be preferred when available.

[IsaacFL]

IPv6 is problematic. There is no way to specify that it is ipv6, so if you have a dual stack (A and AAAA) host, it fails.

That is not entirely correct: I added a switch "allow IPv6" in the advanced options a while ago. If you use that, IPv6 will effectively be preferred when available.

I should have been more clear. I was talking about the ability to create AAAA records vs A records. 

All "allow IPv6" does is put "ipv6=yes" in the config file which allows the use of ipv6 protocol to talk to the ddns service.

What is missing is the ability to specify you want to create AAAA record.

instead of:
use=if, if=ix0       which reads the ipv4 address and creates an A record

It needs:
usev6=if, if=ix0    this will read the ipv6 address and create an AAAA record.

If you have a dual stack host.example.com where you need both A and AAAA records created, I couldn't get that to work.  Seems to try to update the AAAA record with the ipv4 address which fails.

[meyergru]

You have to use a DDNS service that finds out the IPv6 by themselves when they are contacted via IPv6 and keep a given EUI-64, just change the prefix. That is what I do.