Harder to use for multiple domains (records) simultaneously

[Chealer]

The cloudflare-ddns command launches a foreground process which updates a record and exits as soon as the record is up-to-date. However, the package provides infrastructure to keep that record updated in case of future IP address changes, thanks to systemd configuration files which make it behave similar to what a daemon would accomplish, as explained in the README's systemd timer section.

Unfortunately, it is either not possible or not clear how to use that infrastructure to maintain 2 different records (for example, foo.org and bar.org). The configuration file can store 1 token and 1 target record, but it is not clear that it can store more, and using several configuration files basically requires modifying/copying systemd configuration files. As of version 2.1, the configuration file appears to be unspecified.

The Debian package's French description reads:

cloudflare-ddns est un programme ponctuel : exécutez-le, il met à jour les enregistrements DNS et il quitte.

But I assume that is a mistake. The translator must have used plural assuming that several records were supported.

[Tachi107]

Hi @Chealer, thank you for opening this issue! Sorry for not replying earlier, but GitHub didn't send me any notification.

Yes, this is a known limitation, as outlined in issue #22. Still, depending on your use case, you may be able to create a single A or AAAA record named ddns.example.org, which is updated by this tool, and multiple CNAME records pointing to it.

It is not possible to update multiple records in a single atomic operation using Cloudflare's API, which is the main reason why I didn't add this feature (yet).

Let me know if this fixes your issue!

[Chealer]

Hi @Tachi107,

Hi @Chealer, thank you for opening this issue! Sorry for not replying earlier, but GitHub didn't send me any notification.

Not at all, that's still a fast reply by comparison with most projects. But thank you for your care!

Yes, this is a known limitation, as outlined in issue #22. Still, depending on your use case, you may be able to create a single A or AAAA record named ddns.example.org, which is updated by this tool, and multiple CNAME records pointing to it.

Right, this would be a good workaround to document, but it doesn't help with servers which truly serve multiple top-level domains due to CNAME limitations.

It is not possible to update multiple records in a single atomic operation using Cloudflare's API, which is the main reason why I didn't add this feature (yet).

For what it's worth, I do not really see how this constitutes a problem (unless you mean it causes more work to be needed for implementation), but thanks for sharing.

Let me know if this fixes your issue!

To clarify, this is not "my issue" just because I reported it. I already worked around the difficulty this caused on my server.