-
Notifications
You must be signed in to change notification settings - Fork 380
Description
Using ddclient to update the a DNS entry @ IN A of the domain georouter.ca (as an example)
I was able to make the update works using the following format (could be added to the doc ;) ) :
protocol=gandi
use=web, web=https://api.ipify.org/
zone=georouter.ca
ttl=300
password='<PASSWORD>'
use-personal-access-token=yes
@
The problem is that I have multiple domains to update and it's the same DNS field ( @ IN A )
Only the first one get updated the others are discarded
ddclient[3048]: SUCCESS: [gandi][@]> skipped: address was already set to xxx.xxx.xxx.xxx
Also, the cache get impacted because it thinks it's the same entry :
# ddclient-4.0.0
## last updated at Thu Jan 30 17:28:55 2025 (1738276135)
atime=1738276135,host=@,ip=xxx.xxx.xxx.xxx,mtime=1738276135,status-ipv4=good @
I'm not sure if that's normal or if that's a bug.
I think the program should look for ZONE if exists to have something like
## last updated at Thu Jan 30 17:28:55 2025 (1738276135)
atime=1738276135,zone=georouter.ca,host=@,ip=xxx.xxx.xxx.xxx,mtime=1738276135,status-ipv4=good @
I did not look at the code and I'm just wondering if that would be enough in this specific case to allow updates of multiple identical entries.
I believe zone could be used if exist to add context and avoid duplicates
I don't know if that's only related to GANDI or others protocols would have the same problem.
Let me know what you think and if there is something we can do.
Thanks :)