os-ddclient

[alexdelprete]

I'm talking OS-DynDNS, I won't be playing with ddclient.

Can't OS-DynDNS be migrated to @mimugmail repository? So we can simply reinstall it from there and that's it.

[jclendineng]

I'm talking OS-DynDNS, I won't be playing with ddclient.

Can't OS-DynDNS be migrated to @mimugmail repository? So we can simply reinstall it from there and that's it.

Also, what was wrong with the old one? If the new one is unmaintained, doesn't work for a lot of services, and is harder to use, I guess I don't understand why we are switching...doesnt make a lot of sense.

[chemlud]

I'm talking OS-DynDNS, I won't be playing with ddclient.

Can't OS-DynDNS be migrated to @mimugmail repository? So we can simply reinstall it from there and that's it.

Also, what was wrong with the old one? If the new one is unmaintained, doesn't work for a lot of services, and is harder to use, I guess I don't understand why we are switching...doesnt make a lot of sense.

Define "we" in your last sentence... ;-)

[alexdelprete]

Also, what was wrong with the old one? If the new one is unmaintained, doesn't work for a lot of services, and is harder to use, I guess I don't understand why we are switching...doesnt make a lot of sense.

Devs make their decisions, there surely is a valid reason. My concern is that the ddclient, checking the issues and the PRs, is worse than dyndns regarding release maintenance.

There was a PR for cloudflare API token support since 1.5y, never reviewed or committed, now I noticed one of the devs scheduled it for next release.

Anyway...I'm sure we'll find the proper way to keep using dyndns, either on an external repo, or as a last resort, we can install it on another server in the network: it's not a functionality that requires OPNsense. Sure, having it integrated in OPNsense is better, but it's not the end of the world.

[franco]

Long story short: we are trying to find a maintainable solution for the next 10 years or so. os-dyndns is a slowly but surely ageing disaster.

Keeping os-dyndns forever defeats the purpose of doing all of this.

And yes for some people os-dyndns is a lot of work behind the scenes.


Cheers,
Franco

[dinguz]

FWIW, I tried ddclient and couldn't get it to work. I have switched back to os-dyndns for the time being, while the quirks are being ironed out. I used it with NoIP (.ddns domain).
If someone is working on it, I'll gladly provide the logs and work with them.

[tiermutter]

I tried ddclient on a Debian machine and it works fine with ddnss.de and spdyn.org without any predefined provider-configs. I think when there is the possibility to use (bootpersistant) custom provider, ddclient will be fine for everyone using any provider.

[Pocket_Sevens]

For some reason, I update the ddclient.conf file with my config but the file gets cleared after each reboot.  I can see the new GUI page but I don't see freedoms as a choice. 

And yes, I did delete dyndns plugin and install ddclient.

[franco]

When you have os-ddclient installed it will rewrite ddclient configuration from GUI settings always. But you can use "ddclient" package manually. For this purpose do not install os-ddclient.


Cheers,
Franco

[opn_nwo]

I usually upgrade within few days of a new release, but this time I'll old off until ddclient is updated with support for Cloudflare and interface selection. That functionality is very important for my home network and I don't want to spin up a separate VM just for that.

[chemlud]

I usually upgrade within few days of a new release, but this time I'll old off until ddclient is updated with support for Cloudflare and interface selection. That functionality is very important for my home network and I don't want to spin up a separate VM just for that.

The old dyndns package is still in the repos for 22.1, I tried a fresh install over the weekend, it's there. So no problem, you can update. I have no Realtek Nics though and I havn't tried every feature in 22.1 yet...

[beeric]

The old dyndns package is still in the repos for 22.1, I tried a fresh install over the weekend, it's there. So no problem, you can update. I have no Realtek Nics though and I havn't tried every feature in 22.1 yet...

If I'm moving from 21.7, is it going to remove dyndns or automatically install ddclient in addition?

[franco]

Once again, os-dyndns operation is not affected on 22.1.


Cheers,
Franco

[pyrodex]

If this is going to be a forced retirement/switch to os-ddclient please for the love of all things tech include AWS R53 support. I've scoured the ddclient github and can't find any pull requests and/or issues to support AWS R53. While I understand the need to move forward you can't move forward and remove a lot of features.

[BadSamaritan]

I Agree with above comment. I use AWS R53 and Tunnel Broker(HE.net) which are built in options in the old dyndns client. They don't exist in the ddclient settings. It doesn't  have to be an all in one in my opinion. I've seen projects for aws53 updates that could maybe be worked into a new module. For example: https://github.com/crazy-max/ddns-route53