mirror/stackexchange-dnscontrol
1
0
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2024-05-11 05:55:12 +00:00
Code Issues Releases Activity

CLOUDFLAREPI: DOCS: Clarify Cloudflare's TTL magic (#1986)

Browse Source
This commit is contained in:
Tom Limoncelli
2023-01-26 11:49:48 -05:00
committed by GitHub
parent 3a6b488b8a
commit e788491424
1 changed files with 19 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
documentation/providers/cloudflareapi.md
View File

@ -247,3 +247,22 @@ go test -v -verbose -provider CLOUDFLAREAPI -cfworkers=false
```
When `-cfworkers=false` is set, tests related to Workers are skipped. The Account ID is not required.
## Cloudflare special TTLs
Cloudflare plays tricks with TTLs. Cloudflare uses "1" to mean "auto-ttl";
which as far as we can tell means 300 seconds (5 minutes) with the option that
CloudFlare may dynamically adjust the actual TTL. In the Cloudflare API,
setting the TTL to 300 results in the TTL being set to 1.
If the TTL isn't set to 1, Cloudflare has a minimum of 2 minutes.
A TTL of 0 tells DNSControl to use the default TTL for that provider, which is 1.
In summary:
* TTL of 0, 1 and 300 are all the same ("auto TTL").
* TTL of 2-120 are all the same as 120.
* TTL of 121-299, and 301 to infinity are not magic.
Some of this is documented on the Cloudflare website's [Time to Live (TTL)](https://developers.cloudflare.com/dns/manage-dns-records/reference/ttl/) page.