Simply updating ddclient is insufficient according to user reports. We need to identify and make changes to the config script to make actually work.
- Difficulty level
- Unknown (require assessment)
- Why the issue appeared?
- Will be filled on close
- Is it a breaking change?
- Unspecified (possibly destroys the router)
- Issue type
- Feature (new functionality)
|Duplicate||BUG||c-po||T1763 CloudFlare DDNS support|
|Resolved||BUG||c-po||T1030 Upgrade ddclient from 3.8.2 to 3.9.0 (support Cloudflare API v4)|
It is currently impossible to update zones on cloudflare dns via ddclient because the generated configs for cloudflare are mising a zone=<domain.tld> directive.
I also note that the comment for each entry also says "DynDNS provider configuration" regardless of the provider used.
Example bad config file:
# DynDNS provider configuration for 104-1831-gw.104-1831.tdude.co protocol=cloudflare max-interval=28d firstname.lastname@example.org password='<snipped>' 104-1831-gw.104-1831.tdude.co
Example good config file:
# Cloudflare provider configuration for 104-1831-gw.104-1831.tdude.co protocol=cloudflare max-interval=28d email@example.com password='<snipped>' zone=tdude.co 104-1831-gw.104-1831.tdude.co
The zone could be specified by an extra parameter on the CLI but I can't think of a use-case where we can't just extract the root zone from the host-name.
As this is merged into equuleus can we close this?
Of course we can add the zone option in future versions - but if it is to be auto generated that's even better and more user friendly.