-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update multiple A records #22
Comments
Hi @tonimelisma, thanks for checking out this project! You could run multiple instances of the tool, one for each name you want to update, but it is way more robust to have cloudflare-ddns update a single record, like I seem to remember that apex records (that is, Does this solve your issue? |
Hey, I'm pretty sure the DNS RFC standard forbids a CNAME of www.example.com pointing to a parent domain A record example.com. I'm using your package because it's installable via APT on Ubuntu. Unfortunately that doesn't have any automation to run Is I'd offer to do a PR but unfortunately I haven't done C++ in over 25 years so my skills are a bit rusty 😆 |
Interesting, would you be able to point me to that document? As far as I know you can't do
Happy to hear that! I maintain that too.
Yeah, that's true. systemd provides a well defined mechanism to run multiple instances of a service, and I could look into leveraging that, if wanted. But thinking about it, adding multi-record support to the tool itself might result in a better user experience.
Of course :) It doesn't receive lots of commits because it already does what I and a few friends need it to do.
I've considered this option before, and I'd like to avoid it if possible. See issue #14 for some rationale. Of course, if there are no other ways around this issue I'd probably implement it.
Don't worry, I appreciate the offer :) Edit: looking at https://webmasters.stackexchange.com/questions/127252/is-a-cname-from-the-domain-apex-to-the-www-record-the-correct-way-to-configure-a it seems that |
Hey @tonimelisma, did you try to set up a |
Hey @Tachi107. No, it didn't. I also have a need to update other A records in other domains under my Cloudflare account. I suppose you can either keep this issue open as a feature request or if you don't want to implement it, close the issue and I will look for a replacement software. Thanks for the program and have a great week. |
Why not? Could you please help me better understand why you specifically need A records and cannot use CNAMEs?
My answer would be to user cross-domain CNAME records, but I seem to understand that it doesn't seem to work for you.
The thing is, it's not that I don't want to implement it, but any possible implementation of multiple A records support would be flaky. What happens if you loose network connection after only the first record is updated? You end up in an inconsistent state. There's no way to atomically update multiple records, so any implementation of this feature would be inherently fragile. The only way to make this reliable is to solve the issue in an alternative way, i.e. by using CNAMEs pointing to one single dynamic record. Does this now make more sense to you? Do you have any better idea about how to approach this inconsistency issue? I really want to solve this issue, we just need to figure out how :) |
For this case i have a request , The idea is use multi-intense on systemd. Im on debian 12, and im not an expert on systemd, but this method seems clean to me :
Change on unit Part :
Change on ddns Part :
If you want to add another domain, I think you just need to duplicate the config file with the domain name and enable : One of the only fears I have is that cloudflare limits the number of updates per different process. For the CNAME debate, you can very well have an A record that you update, and the other records can be CNAMEs. |
Hi @egildi81, thank you very much for your feedback! Yeah, I too was thinking about using systemd's multi-instance support, but I first need to refine the caching system because it currently has issues with updating multiple records at once. I'm pretty much done, but you can look at PR #20 for details. Once that's done I'll look into this to figure out what's the best way to implement this feature. Thank you all again :) |
After thinking about this more, I really can't find a good use case for this, and a case where such a feature would work better than CNAMEs. I'll mark this as wontfix, but if you think you can find an elegant solution to this, I'll be happy to review patches! |
Hi @Tachi107, |
Oh, that is something I didn't understand... This changes the usefulness of the feature indeed.
I didn't consider this feature important enough to spend time on it, but I did understand that it is something that users want. Hence if somebody wanted to work on this I'd review and (if clean enough) merge the feature. Edit: to be clear, now that I better understand the issue, I'll eventually work on fixing it myself.
Sure!
Thanks for your patience in making me understand why this is needed :) |
I have both a www.example.com as well as example.com records that need updating. Is there a way to update both using the .ini file? I couldn't figure out a way.
The text was updated successfully, but these errors were encountered: