i dont know what happens... but when i run ddupdate for cloudflare without --force option, it always says Existing ipv4 record matches, skipping update ... is worth note i have cloudflare with 2 domains (with 2 domains, see #79 also), i dont know if this have something to do
just when i log to console and manually type ddupdate -f -e my.domain it seem to work ... -l debug doesn't show any useful hint neither
update: now i had to delete cache and retry (cache is located in ~/.cache/ddupdate/cloudflare.com.ip)
p.s.: as ddclient supported just one domain per service name before, all configurations revolved around service names... but as some time ago, support for multiple conf sections were added, configs now should be referenced by domain names instead (not needed before) ... this inconsistency could bring problems
i dont know what happens... but when i run ddupdate for cloudflare without
--forceoption, it always saysExisting ipv4 record matches, skipping update... is worth note i have cloudflare with 2 domains (with 2 domains, see #79 also), i dont know if this have something to dojust when i log to console and manually type
ddupdate -f -e my.domainit seem to work ...-l debugdoesn't show any useful hint neitherupdate: now i had to delete cache and retry (cache is located in
~/.cache/ddupdate/cloudflare.com.ip)p.s.: as ddclient supported just one domain per service name before, all configurations revolved around service names... but as some time ago, support for multiple conf sections were added, configs now should be referenced by domain names instead (not needed before) ... this inconsistency could bring problems