os-ddclient

[keropiko]

Thank you!

[Netboy3]

Support for Hurricane Electric (HE.net) for both their Dynamic DNS and TunnelBroker services was just merged and should be available in the next release.

[lilsense]

found a script for cloudflare DDNS updater

https://github.com/K0p1-Git/cloudflare-ddns-updater

hope that someone can integrate this as well.

[Netboy3]

hope that someone can integrate this as well.

No need to integrate external scripts. ddclient knows how to manage the cloudflare DynDNS service natively and an update was merged into OPNsense 5 days ago that adds cloudflare to the GUI. It should be there for the next OPNsense update.

[slackadelic]

found a script for cloudflare DDNS updater

https://github.com/K0p1-Git/cloudflare-ddns-updater

hope that someone can integrate this as well.

Yeah just saw this myself.  The patch that Ads provided earlier in the thread does allow you to have both in the GUI and usable so you can slowly migrate over.

I'm going to wait for the updated GUI changes before moving over from the legacy plugin as I use he.net for DNS on one of my domains, the underlying ddclient does support it, but the GUI just doesn't have the config.

but alas, it's easy to wait

[waxhead]

Just wanted to throw in that I too don't like the new dyndns client. The old one works , the new one does not support (as far as I am able to figure out) freedns.afraid.org which I use.
My solution was to drop the new dyndns client and use cron on one of my servers instead.

[Layer8]

OK, 22.1 was just released a few days ago and my dashboard says:

Please make sure to upgrade to os-ddclient before 22.7 is released as this plugin will be removed from our repository

So, if i check the changelog it took ~a half a year from 19.1 to 19.7 and ~also 6 months from 20.1 to 20.7.

Dont panic guys, i think there is enough time to mature ddclient before dyndns is end of life in opnsense.

@Devs: Is a half a year also a realistic period for 22.7-release?

Edit: Corrected 21.7 to 22.7 in the last sentence. Thx jp0469. And btw also thanks for the hint with the month, thins makes absolutely sense. 

[jp0469]

@Devs: Is a half a year also a realistic period for 21.7-release?

Did you mean 22.7? Considering that the ".7" represents the month then I would say it's very realistic that July will come about a half year after January. 

[franco]

Looking at the volume of the support of ddclient development after 22.1 came out I think the next release of the plugin with 22.1.1 will already be a lot better. Again, the mission was not to replace all at once. It was to start replacing it.

And yes there are 6 months to 22.7 and now it looks like we can make it there with ddclient. In any case wait for 22.1.1 next week and then reassess the situation after having checked the attached release notes. Some things may not have been picked up yet but if it is technically possible they will.


Cheers,
Franco

[alexdelprete]

No need to integrate external scripts. ddclient knows how to manage the cloudflare DynDNS service natively and an update was merged into OPNsense 5 days ago that adds cloudflare to the GUI. It should be there for the next OPNsense update.

Great news, next week we should get the update, right? Will it support both token types? (global and DNS token)

[der.ro]

Sadly the current ddclient version only supports the global API key. In the development branch there is support for DNS keys but don't know when this will be released.

[alexdelprete]

Sadly the current ddclient version only supports the global API key. In the development branch there is support for DNS keys but don't know when this will be released.

I bet in a couple of months ddclient will be complete as dyndns...meanwhile, I'll stick with dyndns...

[ChargerDad]

ddclient doesn't seem to work with duck dns tokens in it's current state.   Form requires you to enter a password, which isn't required for the token auth to work at Duck DNS and with the dyndns plugin.  Probably needs another update to allow validation with a blank password similar to the one which allowed for upper case characters in the username??

[Lost_Ones]

For duck DNS,
I recall using DuckDNS in the dropdown,  no username, token as the PW, then my domain   xxxxx.duckdns.org under hostname.

I noticed in the log, it failed a couple times with the KO, the updated. 

Good luck

[Mastah]

I've checked, protocol=gandi does exist on 3.9.1.

Code: [Select]

Dynamic DNS services currently supported include:

DynDNS.com  - See http://www.dyndns.com for details on obtaining a free account.
Zoneedit    - See http://www.zoneedit.com for details.
EasyDNS     - See http://www.easydns.com for details.
NameCheap   - See http://www.namecheap.com for details
DslReports  - See http://www.dslreports.com for details
Sitelutions - See http://www.sitelutions.com for details
Loopia      - See http://www.loopia.se for details
Noip        - See http://www.noip.com/ for details
Freedns     - See http://freedns.afraid.org/ for details
ChangeIP    - See http://www.changeip.com/ for details
nsupdate    - See nsupdate(1) and ddns-confgen(8) for details
CloudFlare  - See https://www.cloudflare.com/ for details
Google      - See http://www.google.com/domains for details
Duckdns     - See https://duckdns.org/ for details
Freemyip    - See https://freemyip.com for details
woima.fi    - See https://woima.fi/ for details
Yandex      - See https://domain.yandex.com/ for details
DNS Made Easy - See https://dnsmadeeasy.com/ for details
DonDominio  - See https://www.dondominio.com for details
NearlyFreeSpeech.net - See https://www.nearlyfreespeech.net/services/dns for details
OVH         - See https://www.ovh.com for details
ClouDNS     - See https://www.cloudns.net
dinahosting - See https://dinahosting.com
Gandi       - See https://gandi.net
dnsexit     - See https://dnsexit.com/ for details
1984.is     - See https://www.1984.is/product/freedns/ for details

Comparing to the huge list of service available on dyndns, it's really embarrassing to force ppl to move to ddclient, that in his current stat on opnsense, only support 7-8 protocol ...
When dyndns supported about 60 DNS services ...

In my case, I'm using gandi. If I switch (or forced to switch to on version 22.7) to the ddclient plugin on opnsense, I won't been able to use it for Gandi anymore.
This is a major downgrade for me, and shouldn't happen in this current stat.

You need to at least support all the protocol available (cf. list on top) to even consider moving to ddclient.