Feature request: update N of M A/AAAA records #200

New Issue

saavagebueno · 2025-11-20T04:21:26-05:00

saavagebueno commented

2025-11-20 04:21:26 -05:00

Originally created by @redtripleAAA on GitHub (Jul 7, 2022).

Originally assigned to: @qdm12 on GitHub.

What's the feature?
Support multiple A records for the same hosts
Extra information?
For example: one that is doing the DDNS as normal which works perfectly fine
and another A records for the same hosts to have the option to get DDNS from another locations
or to set it manually as static IP address

Currently, when you have a host set to talk to Cloudflare
It will rewrite whenever it gets the IP (Which is expected from the current setup)
However, I have this setup that requires the subdomain to have (A) DNS records

A >> 1.1.1.1
A >> 192.168.1.15

Example screenshots (Sometimes it works like this)

That sometimes works actually with the current setup, however, sometimes it writes both with the new DDNS if got detected with changes.

Thanks.

Originally created by @redtripleAAA on GitHub (Jul 7, 2022). Originally assigned to: @qdm12 on GitHub. 1. What's the feature? Support multiple A records for the same hosts 2. Extra information? For example: one that is doing the DDNS as normal which works perfectly fine and another A records for the same hosts to have the option to get DDNS from another locations or to set it manually as static IP address Currently, when you have a host set to talk to Cloudflare It will rewrite whenever it gets the IP (Which is expected from the current setup) However, I have this setup that requires the subdomain to have (A) DNS records A >> 1.1.1.1 A >> 192.168.1.15 Example screenshots (Sometimes it works like this) <img width="1100" alt="Screen Shot 2022-07-07 at 9 18 59 PM" src="https://user-images.githubusercontent.com/5244872/177897379-fef78b99-add5-41d5-b09b-0bbfa44d1c53.png"> That sometimes works actually with the current setup, however, sometimes it writes both with the new DDNS if got detected with changes. Thanks.

saavagebueno added the Status: 🗯️ Waiting for feedback Category: Good idea 🎯Status: 🔒 After next release Category: Provider update ♻️ labels 2025-11-20 04:21:26 -05:00

saavagebueno commented

2025-11-20 04:21:27 -05:00

@qdm12 commented on GitHub (Jan 19, 2024):

Thinking about this a bit...

Check updates.json for the last IP for this domain+host+ip version
1. Last IP not found: update all records (not one at random, to be consistent). This happens on a fresh start with no persisted data.
2. Last IP found: find records containing the last IP
  1. At least one record found: update all matching records
  2. Record not found: update all records (not one at random, to be consistent)

That should do the trick right?

Or would you like to be able to specify i.e. record ids?

Although ideally I would like to extend this to all providers 😉

@qdm12 commented on GitHub (Jan 19, 2024): Thinking about this a bit... 1. Check updates.json for the last IP for this domain+host+ip version 1. Last IP not found: update **all** records (not one at random, to be consistent). This happens on a fresh start with no persisted data. 2. Last IP found: find records containing the last IP 1. At least one record found: update all matching records 2. Record not found: update all records (not one at random, to be consistent) That should do the trick right? Or would you like to be able to specify i.e. record ids? Although ideally I would like to extend this to all providers 😉

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#200