DNS provider
DNS propagation in Google Cloud DNS
Saving in Google Cloud DNS updates your zone fast — the internet caches old answers until TTL expires.
Provider gotcha: The DNS name field for apex records must use a trailing dot:
example.com. — FQDN form. Omitting the dot can create the wrong relative name.Read DNS propagation for background.
Step by step
Step 1 Google Cloud Console → Network services → Cloud DNS → your zone → Add standard (or Add record set).
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. Use FQDN with trailing dot for clarity on apex; for
_dmarc use _dmarc.example.com. in the name field.Step 5 Open DNS Propagation to compare resolvers. Typical: Usually minutes once the zone is live at Google’s nameservers.
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 Google Cloud DNS?
Usually <strong>minutes</strong> once the zone is live at Google’s nameservers.
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.