os-ddclient

[mueller]

Hello,

I like to use the services of deSEC (desec.io), because I appreciate the reliability very much - a great help for my Wireguard VPN connection on OPNsense.
In the future transition from os-dyndns to os-ddclient, the support therein for deSEC will be lost.

I once wrote an email to deSEC. They reacted promptly and OPNsense to add this support to os-ddclient:

https://github.com/opnsense/plugins/issues/2793

I think that is great. They are really fit, I can only recommend the dynDNS service.

Greetings,
Dirk

[nivek1612]

well, it is a least supposed to support google domains but will it accept the generated credential from my google domain accounts NO. Claims userid contains invalid characters

Anyone managed to get it to work with Google domains

[marjohn56]

well, it is a least supposed to support google domains but will it accept the generated credential from my google domain accounts NO. Claims userid contains invalid characters

Anyone managed to get it to work with Google domains

That's a bug in the validation routine in the Opnsense interface. I THINK it's already been taken care of, but not yet released. I manually patched mine to allow the API token I use for GoDaddy whilst I am playing with DDclient and Godaddy,

[nivek1612]

That's a bug in the validation routine in the Opnsense interface. I THINK it's already been taken care of, but not yet released. I manually patched mine to allow the API token I use for GoDaddy whilst I am playing with DDclient and Godaddy,

Cheers @marjohn

[AdSchellevis]

The validation issue should be fixed in https://github.com/opnsense/plugins/commit/c970a82d15dcd1a3c68d03296bebd4e8e67da40b , which can be patched using:

Code: [Select]

opnsense-patch -c plugins c970a82d1

Best regards,

Ad

[nivek1612]

Cheers yes that's allowing the credentials to be entered now.

Time to play now.

[lilsense]

Is Cloudflare API supported?

[AryasDad]

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

Adding another voice for AWS Route53 support with the new preferred dynamic DNS plugin.  I just upgraded to 22.1 and got knee-jerk nervous on the warning message about DYNDNS deprecation.  Tried the new plugin and saw Route53 is not an option, so reverted back to DYNDNS. 

I also echo others in this thread about choosing a replacement that has at least if not more of the same options of the deprecated plugin.  Though understand about the difficulty also expressed.

Hopefully by the time 22.7 rolls around, a more robust solution is available.

Thanks!

[xpendable]

In terms of alternate dynamic dns clients, was the inadyn client ever considered? It appears to be under active development, and has many predefined providers along with the ability to add custom providers.

[gpb]

In terms of alternate dynamic dns clients, was the inadyn client ever considered? It appears to be under active development, and has many predefined providers along with the ability to add custom providers.

Not advocating, just making a note that inadyn has a page in the freebsd documentation...though not in the opnsense install.

https://www.freebsd.org/cgi/man.cgi?query=inadyn&apropos=0&sektion=8&manpath=FreeBSD+11-current&format=html

[franco]

While it has a manual page there it's still being pulled from FreeBSD ports like ddclient and is not available in the base install. You can see from the header saying "FreeBSD and Ports".


Cheers,
Franco

[gpb]

Ah....figured that was too easy...yeah saw ports but wasn't sure if any ports are included via base...I guess not.  Seems strange since DDNS is such a common feature.  :/

[franco]

It would appear DynDNS as a whole is a low budget home owner driven use case.


Cheers,
Franco

[keropiko]

Hello all,

I Just replaced the dyndns plugin, but sadly there is no option with the ddclient plugin, to choose to which interface to update the hostname. So basically every hostname will update to the same primary gateway IP.

[franco]

@keropiko will be in the next version