Immutable solution version
Cloudflare DNS TTL: plan propagation before you migrate
Complete solution
Guide Cloudflare DNS TTL: plan propagation before you migrate: It is the single variable controlling how fast your DNS change reaches users, and there is no way to force resolvers to drop a cached record early. ## The migration sequence 1. Use this when you hit exactly this in Cloudflare DNS TTL. Not for different errors or different tools.
TL;DR: It is the single variable controlling how fast your DNS change reaches users, and there is no way to force resolvers to drop a cached record early. ## The migration sequence 1. # DNS TTL and propagation TTL (time to live) tells resolvers how long to cache a DNS record. At least 24 hours before the change, lower the TTL on the records you will touch (e.g. to 300 seconds).
Fix
It is the single variable controlling how fast your DNS change reaches users, and there is no way to force resolvers to drop a cached record early. ## The migration sequence 1. Expected: this specific failure stops.
At least 24 hours before the change, lower the TTL on the records you will touch (e.g. to 300 seconds). Expected: this specific failure stops.
Make the change. Expected: this specific failure stops.
Verify propagation from multiple vantage points (. Expected: the value or setting is exactly right, nothing ambiguous.
Keep the old records alive until the new ones are verified. ## Checklist - TTL change first, wait, record change, verify, TTL restore. - Keep old infra answering until propagation is confirmed, not until the change is "done". Expected: this specific failure stops.
Details
DNS TTL and propagation TTL (time to live) tells resolvers how long to cache a DNS record. 2. Wait out the OLD TTL: resolvers that cached the record under the old TTL keep it until that TTL expires. This is the part teams skip. 3. 4. dig @8.8.8.8 , dig @1.1.1.1 , and a resolver on another continent). 5.
When to use
You hit exactly this: Cloudflare DNS TTL: plan propagation before you migrate in Cloudflare DNS TTL.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Cloudflare DNS TTL (versions mentioned here: 8.8.8, 1.1.1).
Evidence
Verified against the live Create DNS records and DNS concepts docs: TTL definition, propagation behavior, recommended TTL management around migrations. Refs: https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/ and https://developers.cloudflare.com/dns/concepts/dns-concepts/
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_EmV3rKCCSqNpWJUtojB8AQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Cloudflare DNS TTL: plan propagation before you migrate <span>— Vectle</span></a>