DNS propagation timelines: when "live" is actually live
Propagation is not instant. Here is how long each step takes and what to expect during the wait.
Rejwan Nirob·Mar 7, 2026·5 min readYou publish a DNS record. The registrar UI shows it as live within seconds. The reality is that propagation across the global DNS network takes longer - sometimes a few minutes, sometimes 24 hours. For cold-email setup, the difference matters because it dictates when you can start sending.
The hops a DNS record makes
Your record is published to the authoritative nameserver. From there, recursive resolvers around the world cache it. Each resolver respects the TTL (time-to-live) on the record, which determines how long the cached value is considered fresh. Mailbox providers like Google and Microsoft run their own resolvers with their own caching behaviour.
Realistic timelines
- Authoritative nameserver - instant after publish
- Major resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1) - typically 1 to 5 minutes
- Most ISP resolvers - 15 to 30 minutes
- Long-tail resolvers worldwide - up to 24 hours
- Mailbox provider resolvers - 5 to 60 minutes for Workspace and M365 in our partner-program telemetry
Why polling matters
Marking a mailbox as "live" the moment a DNS record is published is wrong. The record may not yet be visible to Google or Microsoft. A real provisioning system polls each mailbox provider until DKIM verification succeeds before marking the mailbox live. Inboxlee polls every 60 seconds and typically clears within 5 to 30 minutes.
Mailboxes are not marked live until DKIM verification succeeds against the actual mailbox provider. The wait is visible in the dashboard, with an ETA based on observed propagation curves.
Frequently asked
How long does DNS propagation take for a new cold-email domain?
For mailbox-provider visibility (Google Workspace, Microsoft 365), typically 5 to 60 minutes in our partner-program telemetry. Major resolvers like Google 8.8.8.8 and Cloudflare 1.1.1.1 pick up changes in 1 to 5 minutes. Long-tail ISP resolvers can take up to 24 hours, but they do not block cold sending once the major providers see the records.
Why is my mailbox not "live" if my DNS record is already published?
A published record is not the same as a verified record. The receiving provider has to query the record from their own resolver, which respects TTL caching across the global DNS network. Inboxlee polls each mailbox provider every 60 seconds until DKIM verification succeeds, then marks the mailbox live - typically within 5 to 30 minutes of provisioning.
How can I check if my DNS record has propagated?
Run dig +short <recordname> from multiple resolvers (dig @8.8.8.8 ..., dig @1.1.1.1 ...) and compare. If all major public resolvers return the new value, propagation is essentially complete. Tools like dnschecker.org check 50+ resolvers worldwide in one view. Inboxlee polls Google and Microsoft directly to avoid the false-positive of records being globally cached but not yet picked up by the actual mailbox providers.
What TTL should I use for cold-email DNS records?
1 hour (3600 seconds) is the standard. Short enough that you can iterate quickly during setup; long enough that recursive resolvers do not have to re-query every minute. For records you expect to change often (CNAMEs pointing at services), 300 seconds is acceptable. For stable records (SPF, DKIM, MX), 1 hour or 1 day are both fine.