DNS propagation, which is the time it takes for DNS record changes to update across the internet, generally ranges from a few minutes to 48 hours. Some responses indicate it can occasionally extend to 72 hours, though this is less common. The primary influencing factor is the Time To Live (TTL) value configured for the DNS records; lower TTLs lead to faster propagation. However, the process is also affected by ISP and recursive resolver caching practices, and the asynchronous nature of DNS server updates globally. While many changes become visible within a few hours, it is recommended to wait for the duration of the old TTL to ensure complete propagation. Tools that bypass or minimize caching can be helpful for quicker verification.
8 marketer opinions
DNS propagation, the time it takes for DNS record changes to update across the internet, typically ranges from a few minutes to 48 hours. Some sources indicate potential propagation times extending to 72 hours, although this is less common. The actual time depends on several factors, including the TTL (Time To Live) value set for the DNS records, ISP caching practices, and the asynchronous nature of DNS server updates globally. While updates often become visible within a few hours, complete propagation can take longer.
Marketer view
Email marketer from GoDaddy explains that DNS propagation refers to the time it takes for DNS record updates to be distributed across the internet. While GoDaddy usually reflects updates within 4-8 hours, global propagation can take up to 48 hours.
22 Apr 2025 - GoDaddy
Marketer view
Email marketer from Namecheap explains that DNS propagation is the time it takes for changes to your domain's DNS records to update across the internet. This process can take anywhere from a few minutes to 48 hours, depending on your DNS records' TTL.
11 Jul 2021 - Namecheap
4 expert opinions
DNS record propagation time is primarily governed by the Time To Live (TTL) setting of the domain. Once the authoritative servers are updated, the new DNS data is returned for queries. However, recursive resolvers may cache old values for a duration up to the TTL of the old record. Therefore, waiting for the duration of the old TTL is recommended before relying on the updated DNS information. Tools with short cache times can be useful for quick propagation checks.
Expert view
Expert from Email Geeks shares that once you’ve made a change, wait for as long as the TTL of the _old_ record before relying on it.
28 Nov 2022 - Email Geeks
Expert view
Expert from Word to the Wise shares that their tools won’t cache for longer than 60 seconds regardless of TTL, which can be handy for a quick propagation check.
14 Aug 2021 - Word to the Wise
4 technical articles
DNS propagation, the process of updating DNS records across the internet, generally takes between a few hours and 48 hours. While some changes might propagate faster, it can occasionally extend to 72 hours. Propagation time depends on factors like the Time To Live (TTL) value of the DNS records and caching practices by DNS servers. Lower TTLs lead to faster propagation but can increase query load. Cloudflare's network aims to accelerate DNS resolution, but propagation remains subject to TTL values and caching.
Technical article
Documentation from Cloudflare responds that while Cloudflare's global network helps to accelerate DNS resolution, propagation still depends on the TTL values of your DNS records. Lower TTLs will propagate faster, but may increase query load. Generally you should expect most changes to propagate in line with set TTL, but in rare cases it may exceed this due to caching.
24 Oct 2021 - Cloudflare
Technical article
Documentation from DNS Propagation Checker shares that DNS Propagation is a term referring to the time it takes for the DNS records of a domain name to be updated across the internet. The DNS record change is not instant, it takes time to update the DNS servers around the world. This process usually takes between 24-48 hours. In rare cases, it can take up to 72 hours.
2 Apr 2024 - DNS Propagation Checker
Do I need domain host access to update DMARC records?
How do CNAME records affect DNS records like SPF, DKIM, DMARC, and MX?
How do I add a TXT record to a DNS configuration for Google Postmaster?
How do I configure DNS records to send emails from two different ESPs using the same subdomain?
How long does DMARC policy propagation take and how to handle authentication failures?