CheckInterval is the same as TTL about caddy-dynamicdns HOT 5 CLOSED

From the (admittedly short) time I just spent playing around with libdns, it looks like leaving the field empty doesn't cause any problems (the TTL is set to the default value) I only tested this on libdns/cloudflare.
Another option is to have the default be equal to the CheckInterval.

from caddy-dynamicdns.

I guess we could separate them. I haven't heard of a use case for checks more frequent than 5m before. Why do you need to check that often?

Because it makes sense for CheckInterval to roughly be the TTL, since we're not doing lookups more often than CheckInterval. 🤷‍♂️

But if there's a good use case for this I guess we can separate them out.

from caddy-dynamicdns.

My IP address changes often enough that it sometimes becomes a problem, and I don't see any reason why not 🤷‍♂️

Because it makes sense for CheckInterval to roughly be the TTL, since we're not doing lookups more often than CheckInterval. 🤷‍♂️

This is only true if you have a single client (and even then, it's all a matter of timing). With multiple clients, it's less likely that they have the DNS cached, even if a single client still has the old record cached.

from caddy-dynamicdns.

I'll implement a new TTL config parameter. What should the default be? (Empty/Zero?)

from caddy-dynamicdns.

Should be configurable now -- at least, in the JSON config!

from caddy-dynamicdns.