DNS Time to Live โ€“ What It Is and Why It Matters When Moving a WordPress Site

This article may contain affiliate links. If you buy through them, I earn a small commission at no extra cost to you.

When I recently moved a WordPress website to a new host, I updated the DNS A record to point to the new server. Everything on the backend was ready, but the live site didnโ€™t switch over immediately. Why? Because the DNS Time to Live (TTL) was set to 86400 secondsโ€”thatโ€™s a full 24 hours. If youโ€™ve ever wondered how long DNS changes take to update, TTL is the reason.

Hero image illustrating DNS Time to Live with a gradient background and a globe showing domain extensions on a keyboard key labeled domain name

Let me break down what DNS TTL means and share some best practices, especially if youโ€™re about to migrate a website.



What Is DNS TTL (Time to Live)?

In simple terms, DNS TTL tells other servers how long they should cache the DNS information (like your domain’s A record) before asking again for updated info. It’s measured in seconds.

Here are some common TTL values:

Comparison of common DNS TTL values: 300 seconds (5 minutes), 3600 seconds (1 hour), 86400 seconds (24 hours).
  • 3600 = 1 hour (a typical default)
  • 300 = 5 minutes (great for temporary changes)
  • 86400 = 24 hours (often used for stability)

Each DNS record (A, CNAME, MX, etc.) can have its own TTL. If your TTL is long, DNS changes can feel sluggish. If itโ€™s short, changes happen fasterโ€”but your authoritative DNS server gets queried more often.


What Does a DNS Server Doโ€”and Why Is DNS Cached?

When someone visits your website, their browser needs to convert your domain (like example.com) into an IP address. Thatโ€™s the job of a DNS serverโ€”it resolves human-readable domain names into server IPs.

Infographic showing how DNS Time to Live (TTL) works: a DNS resolver queries a DNS server, receives an IP address with a TTL setting, caches it temporarily, and rechecks after the TTL expires

To avoid asking that same question over and over, DNS servers cache the result for a set amount of timeโ€”thatโ€™s where TTL comes in. It tells the DNS server how long to store the result before checking back for changes.

Thatโ€™s why when you update a DNS record, the change doesnโ€™t take effect instantly everywhere. Some servers are still using the old, cached data until the TTL expires.

Want to go deeper? Hereโ€™s how I built my own DNS server on a Synology NAS.



How Long Do DNS records Change Take to Update?

A common question is: how long does it take for DNS records to update?

Thereโ€™s no one-size-fits-all answer. It depends entirely on the previous TTL setting. For example:

  • If your A record had a TTL of 86400 seconds (like mine), DNS resolvers may keep using the old IP for up to 24 hours.
  • If you had set it to 300 seconds, the update could take just 5 minutes to propagate.

This also applies to CNAME records and nameserver changes. Tools like whatsmydns.net let you track real-time DNS propagation worldwide.

In practice, Iโ€™ve noticed that large DNS providers like Google DNS (8.8.8.8) and Cloudflare (1.1.1.1) often refresh their cache more frequently than the TTL suggests. For example, I was able to request a new SSL certificate shortly after the A record changeโ€”even though the TTL was set to 86400.

That said, not all resolvers behave this way. Some DNS servers around the world strictly follow the TTL and wonโ€™t refresh until the full time has passed. Thatโ€™s why itโ€™s still important to lower TTL ahead of time if you need guaranteed speed.



DNS Time to Live Best Practices

Hereโ€™s what I recommend when dealing with DNS changes:

  • Lower the TTL to 300โ€“600 seconds at least 24 hours before making your move. This gives DNS resolvers a shorter cache window.
  • Make your DNS change (e.g., update A record to new host).
  • Wait for propagation, using DNS lookup tools to verify.
  • After propagation, increase the TTL back to 3600 or even 86400 for better long-term performance and fewer DNS queries.

Avoid leaving it permanently lowโ€”short TTLs increase load on your DNS infrastructure.

Illustration of DNS propagation showing an update reaching multiple DNS servers globally across continents.

Tip: A higher TTL reduces DNS traffic and server load, which is ideal for stable, unchanging records. But keep in mindโ€”it also introduces latency when you need to make updates, since resolvers hold onto the cached data longer.

One more thing: Some internet service providers (ISPs) and corporate networks may ignore your TTL settings and use their own refresh intervals. So even if youโ€™ve set a short TTL like 300 seconds, certain resolvers might still hold onto the old data longer than expected. Thatโ€™s why itโ€™s smart to plan a buffer period after the changeโ€”just in case.

Interestingly, the majority of DNS records on the Internet are configured with TTLs of 5 minutes or less. While this allows for fast changes, it often undermines effective caching, leading to more frequent DNS lookups and unnecessary load on authoritative servers. Unless your records change often, longer TTLs are typically more efficient.



Minimum TTL Values โ€“ How Low Can You Go?

Some DNS providers allow very low TTLs, like 60 seconds or less. But unless youโ€™re running a service that requires rapid failover or global routing changes, thereโ€™s rarely a need to go that low.

I usually stick to:

  • 300 for planned changes
  • 3600 for normal operation
  • 86400 for rarely changed records (like MX or SPF)

The maximum DNS TTL value is typically set to 86400 seconds (24 hours) for most users.



How to Change TTL in Cloudflare (And Why Auto Might Mislead You)

If you’re using Cloudflare as your DNS provider, TTL behavior works a bit differently depending on whether your record is proxied through Cloudflare’s CDN or not.

  • If the record is proxied (orange cloud), the TTL is automatically set to 5 minutes, and you canโ€™t manually change itโ€”itโ€™s always listed as โ€œAuto.โ€
  • If the record is set to DNS only (gray cloud), you can manually select the TTL from 1 minute to 1 day.

Hereโ€™s how that looks in the Cloudflare dashboard:

Cloudflare DNS settings showing TTL dropdown and proxy toggle for A record of edywerder.ch. TTL is set to Auto while proxied.

Note: This behavior is specific to Cloudflare. Other DNS providers let you set the TTL freely regardless of proxying.


Donโ€™t Forget Your Local DNS Cache

Even after a DNS record has been updated and propagated globally, your local system may still cache the old DNS entry. This includes:

  • Your browser (e.g., Chrome, Firefox)
  • Your operating systemโ€™s DNS cache
  • Your router or internal networkโ€™s DNS resolver
Flowchart showing DNS lookup process: from browser to recursive resolver to authoritative DNS server.

If youโ€™ve made a DNS change but still see the old site or IP:

  • Try a different device or network
  • Use a tool like nslookup or dig from the terminal
  • Clear your local DNS cache:
  • On Windows: ipconfig /flushdns
  • On macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  • On Linux: Restart systemd-resolved or nscd if used
  • On Windows: ipconfig /flushdns
  • On macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  • On Linux: Restart systemd-resolved or nscd if used

This is why even with a low TTL, some users still experience delaysโ€”their local cache simply hasnโ€™t been cleared yet.

If you’re curious to dive deeper into your domain’s DNS setup, you can analyze your DNS configuration in detail with DNSViz. It provides a visual breakdown of your records, validation, and any potential issuesโ€”especially useful if you want to debug propagation or DNSSEC problems.


Conclusion

DNS time to live isnโ€™t something most WordPress users think aboutโ€”until a migration or DNS change takes longer than expected. Understanding how TTL affects DNS propagation helps you plan ahead and avoid unnecessary delays.

If youโ€™re preparing to move a site or change records, always check your TTL setting. Lower it first, wait for the short TTL to kick in, then make your change. And once everything is live? Donโ€™t forget to raise it again.

I’d love to hear from you. Was this article helpful? Share your thoughts in the comments below. If you prefer, you can also reach me by email or connect with me on Reddit at Navigatetech.


FAQ

Anywhere from 5 minutes to 24 hours, depending on the TTL value previously set.

Yes, 3600 seconds (1 hour) is a good default for most A records.

You canโ€™t force remote DNS resolvers to update early, but lowering TTL before your change helps make updates faster when they happen.

Before you go …

If you found the breakdown of DNS Time to Live insightful, you might also be interested in how performance and reliability play out in the world of WordPress security. I recently explored that in depth in my review of SolidWP, a robust toolset designed to harden WordPress sites without slowing them down. Whether you’re managing your own servers or hosting for clients, this review offers a clear look at SolidWP’s features and real-world use cases. It’s a natural next step if you’re thinking about how to keep your site both fast and secure.

Full Disclosure

Any purchases made from clicks on links to products on this page may result in an affiliate commission for me.ย 

Please keep in mind that the quantity or price of items can change at any time.

As an Amazonย  Associate, I earn from qualifying purchases.

Als Amazon-Partner verdiene ich an qualifizierten Verkรคufen

As an eBay Partner, I earn from qualifying purchases.

Als eBay-Partner verdiene ich an qualifizierten Verkรคufen.

information

Amazon affiliate Program

Edy Werder is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com.

AlieXpress affiliate Program

Edy Werder is a participant in the ALIEXPRESS Affiliate Network, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to ALIEXPRESS properties and associated sub-sites.

Site map

Blogs