DNS provider
DNS propagation in Amazon Route 53
Saving in Amazon Route 53 updates your zone fast — the internet caches old answers until TTL expires.
Provider gotcha: TXT values must be wrapped in quotes in the value field. Multiple strings in one TXT are entered as separate quoted strings on one line.
Read DNS propagation for background.
Step by step
Step 1 AWS Console → Route 53 → Hosted zones → select your domain → Create record.
Step 2 Lower TTL before big changes if your provider allows — then raise after stabilization.
Step 3 After save, wait at least one TTL cycle before assuming failure.
Step 4 Query your zone’s authoritative nameservers directly. For apex SPF, leave the record name blank (not
@). For DMARC use _dmarc in the name field.Step 5 Open DNS Propagation to compare resolvers. Typical: Typically 1–5 minutes to Route 53 authoritative data; resolvers cache per TTL.
Step 6 Final check: DNS Preflight for SPF/DKIM/DMARC together.
DNS Preflight — full auth check for your domain.
Propagation — compare resolvers.
FAQ
What is DNS propagation?
Delay while recursive resolvers cache old TTLs — not instant worldwide.
How fast is Amazon Route 53?
Typically <strong>1–5 minutes</strong> to Route 53 authoritative data; resolvers cache per TTL.
Why does dig show the new TXT but my tool doesn’t?
Different resolver — use propagation checker and lower TTL next time.
What TTL should I use?
300–3600s during changes; longer when stable.
Where to verify all records?
DNS Preflight for SPF/DKIM/DMARC — Propagation tool for cross-resolver checks.