How long does it take for DNS record changes to propagate?

Summary

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.

Key findings

  • Typical Propagation Time: Most DNS record changes propagate within a few minutes to 48 hours.
  • Maximum Propagation Time: In some instances, propagation may take up to 72 hours, but this is relatively uncommon.
  • TTL Impact: The Time To Live (TTL) setting is the dominant factor affecting propagation speed.
  • Caching Influence: ISP and recursive resolver caching can delay the visibility of DNS updates.
  • Asynchronous Updates: DNS server updates occur asynchronously across the globe, leading to variability.

Key considerations

  • Waiting for Old TTL: Wait for the duration of the old TTL before relying on the updated DNS records.
  • Choosing TTL Values: Consider the trade-off between faster propagation (lower TTL) and increased query load.
  • Clearing Local Cache: Clearing your local DNS cache may allow you to see the updates sooner.
  • Using Propagation Checkers: Use tools with minimal caching to quickly check for DNS propagation.

What email marketers say
8Marketer 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.

Key opinions

  • Typical Range: DNS propagation usually takes between a few minutes and 48 hours.
  • Maximum Time: In some cases, propagation can take up to 72 hours, but this is less frequent.
  • Asynchronous Updates: The global DNS system updates asynchronously, meaning different servers update at different times.
  • Faster Local Updates: New DNS records may become visible much sooner than the maximum propagation time.

Key considerations

  • TTL Value: The TTL value of DNS records significantly impacts propagation time; lower TTLs propagate faster.
  • ISP Caching: ISP caching practices can cause delays, as old DNS records are temporarily stored.
  • Local Cache: Clearing your local DNS cache may help you see the updated records sooner.
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.

January 2023 - 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.

March 2024 - Namecheap
Marketer view

Email marketer from Stackoverflow responds that in their experience DNS updates normally happen within 30 mins to 2 hours, but can indeed take longer.

July 2023 - Stackoverflow
Marketer view

Email marketer from Quora answers that the global DNS system is updated asynchronously. This means that no two DNS servers on the planet will be updated at the same time. So it's possible for you to see a changed DNS entry on one server but the server next door still hasn't been updated. Most DNS updates can take anything from a few seconds to 72 hours to propagate fully.

November 2023 - Quora
Marketer view

Email marketer from Siteground explains that DNS propagation might take up to 72 hours to complete in rare cases; however, it is usually much faster than that. Once you point your domain to SiteGround, it should propagate in a few hours or less.

September 2023 - Siteground
Marketer view

Email marketer from Reddit responds that it generally takes 4-8 hours for a DNS change to fully propagate however it can take up to a maximum of 72 hours.

April 2024 - Reddit
Marketer view

Email marketer from Hostinger Academy shares that DNS propagation typically completes within 24 hours, though it can extend to 48 hours in certain cases. This variability stems from ISP caching practices, where old DNS records are temporarily stored. Clearing your local DNS cache might help you see the updated records sooner.

January 2024 - Hostinger
Marketer view

Email marketer from IONOS explains that DNS changes usually propagate within a few hours, but may take up to 24 hours in some cases. Factors affecting propagation time include the TTL value of DNS records and ISP caching behavior. For most users, the new records are visible much sooner than the maximum 24-hour timeframe.

November 2022 - IONOS

What the experts say
4Expert 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.

Key opinions

  • TTL Governs Cache Time: The TTL value of the domain dictates how long DNS records are cached.
  • Authoritative Server Updates: New data is returned once authoritative servers are updated, typically in milliseconds to seconds.
  • Recursive Resolver Caching: Recursive resolvers cache old DNS values for up to the TTL of the old record.

Key considerations

  • Waiting Time: Wait for the duration of the old TTL before relying on the changed DNS records.
  • Quick Propagation Checks: 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.

February 2023 - 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.

March 2024 - Word to the Wise
Expert view

Expert from Email Geeks explains that once the DNS data change is at all the authoritative servers (milliseconds to seconds, typically) the new data is returned for any queries. However, any recursive resolver that’s previously looked up the record will hang on to the old value for a while, usually for a length of time less than the TTL of the old record. So if the old record had a TTL of 86400 it could be up to a day before the entire internet sees the new value.

February 2023 - Email Geeks
Expert view

Expert from Email Geeks explains that the cache time for DNS record changes is governed by the "TTL" (Time To Live) of the domain.

February 2023 - Email Geeks

What the documentation says
4Technical 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.

Key findings

  • Propagation Time: DNS propagation typically takes a few hours to 48 hours, with occasional cases extending to 72 hours.
  • TTL Dependence: The Time To Live (TTL) value significantly influences propagation speed.
  • Caching Effects: Caching by DNS servers affects propagation times; lower TTLs reduce caching duration.

Key considerations

  • TTL Management: Lower TTL values result in faster propagation but can increase query load.
  • Cloudflare Acceleration: Cloudflare's network accelerates DNS resolution but is still subject to TTL values.
  • Variability: DNS propagation is not instantaneous and varies due to server caching and global update processes.
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.

August 2024 - 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.

January 2025 - DNS Propagation Checker
Technical article

Documentation from Google Workspace Admin Help explains that DNS changes can take up to 48-72 hours to fully propagate across the internet, although it often happens much faster. The actual time depends on the Time To Live (TTL) value set for the DNS records.

August 2022 - Google Workspace Admin Help
Technical article

Documentation from DigitalOcean shares that DNS propagation times vary, and are affected by the TTL value of the changed record and by caching DNS servers. A lower TTL means the DNS record is cached for a shorter period, resulting in faster propagation. Most changes propagate within a few hours, but can take up to 48 hours in some cases.

August 2024 - DigitalOcean