os-ddclient

[franco]

Sit tight for now and keep discussion going is the best thing to do. I personally don't even mind multiple dyndns plugins of varying scope as long as they do a good job of containing their functionality and adhere to MVC framework extensibility which is also going to make it easier to work on for hobby programmers in the first place. It's more of a win-win than the previous convoluted solution that has no real way to yield maintainership to individual users of a particular service.


Cheers,
Franco

[chris1gr]

I agree with Franco. We need a dyndns plugin that works without issues. Then add a CNAME of that dyndns domain to any other dns service.

[tracerrx]

So to be clear, if we currently depend upon DDNS and are running on 21.7.8, what will happen when we upgrade to 22.1?  Is os-dyndns just deprecated but functional or will it just be unavailable?  I don't see any way of installing/setup os-ddclient before the upgrade from 21.7.8 to 22.1.

[marjohn56]

Deprecation for the existing client is/was planned for 22.7 - not 22.1 so six months. However, it may continue to be available. I really don't mind putting under the TR belt if it means it stays around.

[NetGobbler]

i know os-ddclient is intended to replace os-dyndns but currently os-ddclient support for servers is terrible. does not even support cloudflare, especially with tokens.

is this a known issue? and something that is planned to be resolved before removing os-dyndns? since using os-dyndns currently warns you in the UI about its pending removal

I've now figured this out, plugin is a backend engine to a standard frontend template. 
I'm covered thanks to being a dyndns user - luckily my NAS has me covered for this too.

[chemlud]

Just to confirm this: Has nybody upgraded to 22.1 yet? And the old dyndns is still up and running afterwards?

Otherwise an upgrade will break my tunnels, some FW-rules etc.

[tiermutter]

Not updated, did a fresh install with RC1 where os-ddclient was not available.
os-dyndns is still running and working.
You can install os-ddclient in plugin-section while using os-dyndns, seems to work parallel, but didnt try that.
When os-dyndns and os-ddclient are both installed, one of the services (in my case os-ddclient) is not available via GUI menu, I had to go to configpage using the search function.

[DrGonzoNL]

I updated and all is working with os-dyndns which was previously installed.

If you install os-ddclient you can only access it via the search function as stated earlier. I think the most important points are made, you want to specify the listening interface that is not possible. Also the lack of common servers such as freedns is not user friendly. I could find documentation on the freedns page for ddclient but unfortunately it is not in the drop-down list.

[ChrisChros]

I am using ddnss.de which is also not in the list. I had to edit the config file manualy and now its working. One benefit is that ddclient is only updating when the IP has changed, os-dyndns did this regularly every hour.

Editing via CLI is for me not the best way, hopefully in a later version it is also possible via GUI to add the credentials for not "out of the box" supported ddns-services.

[chemlud]

I see with dyndns only once daily/if Ip changes an update at ddnss.com. But good to know that that it at least works (not sure how the problem with changes on VPN IPs will bite though)...

[AdSchellevis]

Contributing additional service providers isn't very difficult....
Checkout the code (https://github.com/opnsense/plugins/tree/master/dns/ddclient) and open a pull request on GitHub.

If ddclient supports the provider, it's literally just adding the option in:

https://github.com/opnsense/plugins/blob/c970a82d15dcd1a3c68d03296bebd4e8e67da40b/dns/ddclient/src/opnsense/mvc/app/models/OPNsense/DynDNS/DynDNS.xml#L55-L68

Optionally followed by specific settings (if needed) in
https://github.com/opnsense/plugins/blob/c970a82d15dcd1a3c68d03296bebd4e8e67da40b/dns/ddclient/src/opnsense/service/templates/OPNsense/ddclient/ddclient.conf#L53-L56

I'm not planning to create an account with every vendor in the world, just added some options so there is an easy starting point since the old plugin will be removed (as explained in https://forum.opnsense.org/index.php?topic=26446.msg127896#msg127896).



Best regards,

Ad

[chemlud]

@Ad

I' still wondering what your reaction would be if you go to your pharmacy at night with a severe headache and the pharmacist tells you to come in, as it's not that hard to synthesize aspirin and he will show you how to fill some capsules afterwards... ;-)

Just kidding...

[yeraycito]

I installed ddclient and got the unpleasant surprise that it has no graphical interface in Opnsense 22.1 so I installed dyndns which does and is very easy to configure. I think it is a step backwards to remove dyndns from Opnsense, a solution would be to keep ddclient and dyndns and let each person choose the one they want.

[AdSchellevis]

install os-ddclient and make sure to remove os-dyndns first (or patch https://github.com/opnsense/plugins/commit/400110af010e8a2cd3ea0f01d4b3db87154bacb6 to show both in the menu)....

[yeraycito]

Thanks, I didn't know that, I've already installed it. I have configured duckdns in ddclient with the following configuration extracted from here: https://sourceforge.net/p/ddclient/wiki/protocols/

protocol=duckdns    
server=www.fqdn.of.service    defaults to www.duckdns.org
password=service-password    password (token) registered with the service
non-fully.qualified.host    the host registered with the service.

do not have IPV6 configured in Opnsense. I get some errors in the ddclient log. What I can't see anywhere is how to know if the service is working properly.