os-ddclient

[depc80]

Please note that 23.7 will kill dyndns (apparently ddclient will be the successor).

23.7 seems like a long way no? We're at 23.1.7 so I guess I can chill for now.

[pmhausen]

23.7 seems like a long way no? We're at 23.1.7 so I guess I can chill for now.

23.1 in January 2023, 23.7 in July 2023, ... there won't be 23.[2-6].

[franco]

Yeah, but the experience for many users is: This functionallity has been up and running for YEARS and problems started by "solving problem" that were non-existent to most users of dynDNS.... ;-)

If only we had not bothered to keep it alive at all perhaps you'd be more favourable towards how we would end up here sooner. Personally, I don't want this thankless job of fiddling with DynDNS getting complained at either way. It has to stop.


Cheers,
Franco

[chemlud]

Yeah, but the experience for many users is: This functionallity has been up and running for YEARS and problems started by "solving problem" that were non-existent to most users of dynDNS.... ;-)

If only we had not bothered to keep it alive at all perhaps you'd be more favourable towards how we would end up here sooner. Personally, I don't want this thankless job of fiddling with DynDNS getting complained at either way. It has to stop.


Cheers,
Franco

Hi franco, I asked for an amount of money to fix this once and for ever (one of the various threads we had on this topic over the last year(s?) ), but iirc I never got an answer. For me this would  be the only professional way forward, if the dynDNS functionality is not considered an integral part of a router/firewall for those many, many users without a fixed public IP on WAN... ;-)

I'm looking for solutions, not problems.

[whatever]

Hey, just something that might be helpful for those who use a dynamic dns service that isn't supported/working properly with ddclient.

I use namecheap, which is only supported using 'ddclient' as the backend. But I have a particular setup in which my "default" gateway is a gateway group comprised of three wireguard gateways. Using 'Interface' as the IP check method and selecting WAN, ddclient always detects my wireguard IP, despite WAN being selected as the interface. It would probably work just fine with a more "vanilla" setup.

Anyway, what I ended up doing and which may be helpful to others, is using dns-o-matic. It's more of a "meta" dynamic dns service in that it can update your IP at your dynamic dns service without you having to switch your dynamic dns provider. I created an account with dns-o-matic. And using dns-o-matic (and configuring ddclient to use dns-o-matic rather than namecheap) detects the correct IP and everything works properly and my IP is updated in my namecheap dashboard. It's not the ideal solution but it works.

Maybe everyone already knows this and I just stated the obvious. But I didn't know and it helped me out.

Cheers

[depc80]

23.7 seems like a long way no? We're at 23.1.7 so I guess I can chill for now.

23.1 in January 2023, 23.7 in July 2023, ... there won't be 23.[2-6].

Damn.

Anyway, I got both IPv4 and IPv6 update by changing backend to OPNsense and use ip4only.me, nsupdate-info.ipv6 for Check IP method instead of interfacev4 & v6.

Btw @franco ip6only.me is a dead site, it is ip6.me i think.

[franco]

Btw @franco ip6only.me is a dead site, it is ip6.me i think.

Both seem to work from here.


Cheers,
Franco

[depc80]

You're right. My bad, I didn't notice at first. ZA put it in dead site category and block it.

[TarteTatin]

Hi,

I tried to move from a Cloudflare-ddns Docker container to os-ddclient, but I can't make it work at the moment.

I have several domain names to update, on the same Cloudflare account, and my Cloudflare API token includes all zones of this account.

So each of my domain names is configured as such:
- Service: Cloudflare
- Username: <empty>
- Password: <cloudflare_account_api_token>
- Wildcard: unchecked (I only want to update my domain names, because I use CNAMES for subdomains)
- Zone: <example.com>
- Hostname(s): <example.com> (exactly like Zone)
- Check ip method: Interface
- Interface to monitor: WAN_832 (device: vlan0.832, like this configuration https://docs.opnsense.org/manual/how-tos/orange_fr_fttp.html)
- Force SSL: checked

I tried at first to update all my domain names in the same Cloudflare service, like what I was doing in a cloudflare-ddns Doker container, but I get a lot of errors. So I have separated the domain names like the configuration above, one entry for each, but I see no "Current IP", nor "Updated" in the Dynamic DNS service.

In the logs, I get the same Notice every five minutes:

Code: [Select]

2023-05-22T23:21:31 Notice ddclient[33961] 94731 - [meta sequenceId="3"] FAILED: Unable to obtain information for 'vlan0.83' -- missing ip or ifconfig command
2023-05-22T23:21:31 Notice ddclient[33961] 93072 - [meta sequenceId="2"] FAILED: Unable to obtain information for 'vlan0.83' -- missing ip or ifconfig command
2023-05-22T23:21:31 Notice ddclient[33961] 92075 - [meta sequenceId="1"] FAILED: Unable to obtain information for 'vlan0.83' -- missing ip or ifconfig command
Two things:
- the device is "vlan0.832", but the logs specified "vlan0.83", like if it is truncated
- my WAN_832 as an IPv4, but no IPv6. Only an IPv6 delegated prefix which is tracked by my LAN interfaces.

In the Cloudflare interface, the API-token is refreshed all fives minutes, so there is a communication.

Thanks for your help.