DNS provider
DNS propagation in Azure DNS
Saving in Azure DNS updates your zone fast — the internet caches old answers until TTL expires.
Provider gotcha: For apex records the name field uses
@. TXT values go in the TXT Records box — one value per line if the UI splits long strings.Read DNS propagation for background.
Step by step
Step 1 Azure Portal → your DNS zone → + 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. SPF/DMARC/DKIM names are relative to the zone — e.g.
_dmarc or google._domainkey for a selector.Step 5 Open DNS Propagation to compare resolvers. Typical: Minutes to about an hour depending on TTL and downstream resolvers.
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 Azure DNS?
<strong>Minutes to about an hour</strong> depending on TTL and downstream resolvers.
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.