os-ddclient

[Grossartig]

Just came here to say that the new ddclient works well for my needs (namely, with Namecheap DDNS). It was a bit confusing that one has to uninstall the old dyndns client before installing the new one (otherwise the config pages wouldn't show up in the OPNsense menu), but besides that, it was easy to set it up for my needs.

Thanks!

[meyergru]

I can live with os-dyndns being supported until 21.7. The relevant missing features of os-ddclient are for me:

1. Getting the IP from the interface instead from a web service
2. Using custom URLs for updates

Both of which seem to get fixed for the upcoming 22.1.1 as far as I can see.

BTW: I was surprised that despite so many bugs being reported here, the transition was completely smooth for me. I have quite a special configuration (including IPv6) but did not have to revert to the backup boot environment that I created before the update.

[franco]

To sum things up the release notes for tomorrow's 22.1.1 WRT ddclient plugin are as follows:

* Add spdyn, inwx and dns-o-matic (contributed by Rene Schuster)
* Add Hurricane Electric provider (contributed by Netboy3)
* Add option to force SSL, on by default (contributed by Robin Mueller)
* Add Cloudflare and custom service (contributed by Robin Mueller)
* Add STRATO provider (contributed by Alex Mi)
* Add use interface as IP source
* Fix ip6only.me (contributed by Robin Mueller)
* Fix uppercase use in usernames


Cheers,
Franco

[mueller]

Hello,

I had hoped that after the update to 22.1.1 this thread has become obsolete.
Especially because now there is the possibility to select "custom" in the settings.
About this I could configure deSEC with the plugin os-dyndns.

Unfortunately, this is probably not possible with the new plugin os-ddclient, because the field "Update URL" to be filled in is not present.

I find this very unfortunate, deSEC (desec.io) is a provider that deserves an entry because it is really, really good.

Thanks for your work anyway.

Greetings

[franco]

Thanks for the rant but isn't the URL part of the protocol being used and you simply fill in the server name to contact?


Cheers,
Franco

[mueller]

Hello,

of course the error can also be with me :-)

... if "custom" is selected under "service", there are three protocols to choose from:

none
DynDns1
DynDns2

The (update) URL of deSEC is:
https://update6.dedyn.io

If I now enter "update6.dedyn.io" as server name, no connection is established.

I have tried all three - without success.
At least the log file always says: No results found!

[franco]

With IPv6 it could be complicated... did you select an interface? If you selected WAN do you have GUA assigned? SSL is on I presume?


Cheers,
Franco

[franco]

(force SSL is hidden unter general settings-> advanced toggle)

[ar]

Sorry to chime in, I've just walked through the official ddclient-client repo and the one in opnsense-plugins one and I'm unsure how to migrate the Hetzner DNS API integration currently availble in the dyndns-package.

What would be the correct contribution way, first contribute the perl implementation for their API in ddclient, then head over to opnsense and add it there once it has been released upstream?

Sadly I see no other way, as cURL is not "just" an option with ddclient to work around it for now, but I'm new to it, so maybe I'm missing the vital part here.

Also I see an interval-setting, is ddclient not triggering on if up/down events?

[mueller]

Hello,

SSL is enabled.
I have selected WAN.
Assign GUA: I still have to read up on this ;-)

With the plugin os-dyndns this was set up quickly and runs smoothly ...

[wadhwa]

Cloudflare DNS update only works with Global API key but it does not work if I create an API token with DNS edit for the zone. DynDNS I can create API key with specific DNS zone edit access and it was working fine. This is unsafe and creates security issues.

To sum things up the release notes for tomorrow's 22.1.1 WRT ddclient plugin are as follows:

* Add spdyn, inwx and dns-o-matic (contributed by Rene Schuster)
* Add Hurricane Electric provider (contributed by Netboy3)
* Add option to force SSL, on by default (contributed by Robin Mueller)
* Add Cloudflare and custom service (contributed by Robin Mueller)
* Add STRATO provider (contributed by Alex Mi)
* Add use interface as IP source
* Fix ip6only.me (contributed by Robin Mueller)
* Fix uppercase use in usernames


Cheers,
Franco

[Mastah]

Franco, I'm trying to add gandi as provider, could you please tell me after I've forked the repo, how can I test the change I made on the plugin on my opnsense install ?

Like that I can test, validate, use it and ask for merge request !

Edit: please tell me I don't have to manually patch the files on my opnsense install ^^

[Mastah]

Btw I've looked at the ddclient project, since 3.9.1 there have been no release in two year. Some people seem to still be working on it though.
Gandi service as been added to the develop branch, for example, like many other services, but at the pace of the project release version, it will be a long time before we can see those services in opnsense.

[Steven]

Been trying to test the new os-ddclient. I use Google as my dynamic DNS. When I went to use the new client I could not setup using my provided Username and Password. For some reason the new plugin says the Username google provided me had "invalid characters" and prevent me from saving the settings. Works fine with the old plugin and I have reverted.

Is there some kind of bug with character limitation for username in the new os-ddclient? I'm using the valid username provided by Google for my DNS. The Username that Google provides for their DNS is just 16 alpha numeric characters.

[franco]

@Stephen maybe you want to upgrade to 22.1.1 first and try again.

@Mastah ... basically you do something like this...

# opnsense-code plugins
# cd /usr/plugins/dns/ddclient
(make your modifications to src/ directory files)
# make upgrade
(install new code to test your changes in the system)

@mueller let me get back on the issue of the log file


Cheers,
Franco