Closed gmemstr closed 3 weeks ago
Not sure I understand what lead to needing this. As I remember it CF returns 1
when auto-ttl is set and historically that has been used as the flag to know when to enable it when pulling data from CF. There's octodns.cloudlare.auto-ttl
that can be set in YAML to tell octoDNS to enable auto-ttl on records pushed up to CF.
Ran into an issue with my use case where even setting a TTL of 1 didn't cause the record to have an automatic TTL without Cloudflare. Tinkering locally, I got it working with 300, so I concluded that being able to configure this TTL value would be worthwhile. Backwards compatible.