DNS provider
DNS propagation in DigitalOcean DNS
Saving in DigitalOcean DNS updates your zone fast — the internet caches old answers until TTL expires.
Provider gotcha: For DKIM, the hostname field is only the left part — e.g.
google._domainkey — not the full google._domainkey.example.com.Read DNS propagation for background.
Step by step
Step 1 DigitalOcean Control Panel → Networking → Domains → select your domain → Add 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. Type TXT, enter the hostname fragment and paste the value. Apex often appears as
@.Step 5 Open DNS Propagation to compare resolvers. Typical: Usually minutes; TTL and recursive caches still apply.
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 DigitalOcean DNS?
Usually <strong>minutes</strong>; TTL and recursive caches still apply.
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.