What Is DNS TTL and How Does It Affect Website Monitoring?

When your website goes down, the problem might not be your server at all. Sometimes the issue is DNS — and DNS TTL values can mean failures persist long after the underlying problem is fixed. Understanding DNS TTL is essential for anyone serious about website availability.

What Is DNS TTL?

TTL (Time to Live) is a value in a DNS record that tells resolvers — your ISP's DNS servers, corporate DNS caches, browser caches — how long to cache that record before querying the authoritative DNS server again.

TTL is measured in seconds:

• TTL 300 = cache for 5 minutes
• TTL 3600 = cache for 1 hour
• TTL 86400 = cache for 24 hours

When someone visits yourdomain.com, their browser (or their network's DNS resolver) looks up the IP address. If they've visited recently and the TTL hasn't expired, they use the cached result without querying your DNS provider.

How TTL Affects Website Availability

DNS Failover Speed

If your server fails and you update DNS to point to a failover server, users with cached DNS records will still be sent to the broken server until their TTL expires.

With a TTL of 3600 (1 hour), a user who looked up your domain 30 minutes ago will continue being sent to the old IP for another 30 minutes after you update DNS — even though you've already pointed DNS to a working server.

Lower TTL = faster failover

This is why high-availability architectures often use TTLs of 60-300 seconds during incidents or planned migrations.

Propagation After DNS Changes

When you change a DNS record (updating an IP address, changing nameservers, adding a record), the change takes time to propagate. Users see the new record only after their cached version expires.

DNS "propagation time" is directly controlled by TTL — a common misconception is that DNS propagation takes 24-48 hours automatically. In reality, propagation can be as fast as your TTL value allows.

Monitoring Accuracy

Your uptime monitoring tool performs DNS lookups as part of each check. If monitoring servers have cached your DNS, they may not immediately detect a DNS failure.

Most monitoring tools re-resolve DNS on every check (not using OS-level caches), so they detect DNS failures accurately. But when you update DNS after fixing an issue, individual users may continue experiencing failures until their local TTL expires.

Common DNS Record TTL Values

Recommended TTL Strategy

Normal Operations

During stable operation, higher TTLs reduce DNS query load and improve performance:

• A/AAAA records: 3600 (1 hour) is a sensible default
• This means users get cached results quickly and your DNS provider handles fewer queries

Before Planned Changes

If you're planning to change DNS records (migrating hosting, changing IP addresses), lower your TTL in advance:

1. 1 week before: Lower TTL to 300 (5 minutes)
2. Wait for the old TTL to expire — if the current TTL is 3600, wait 1 hour for all caches to expire
3. Make the DNS change
4. Verify propagation using DNS lookup tools
5. After migration is stable: Raise TTL back to 3600

If you forget to lower TTL before a migration, you may face a multi-hour delay before all users see the new IP — even though DNS is already updated.

During Incidents

If you're rerouting traffic during an incident via DNS, you want low TTL:

• Emergency TTL: 60 seconds allows near-immediate failover
• Accept the trade-off: more DNS queries, slightly slower resolution for first-time visitors

Monitoring DNS Health

DNS failures are a genuine cause of website downtime. Common DNS issues:

• Expired domain (DNS stops responding entirely)
• Deleted or misconfigured DNS records
• DNS provider outage
• Domain hijacking via unauthorised DNS changes

Domain expiry monitoring with 60-day advance warnings ensures your domain never expires unexpectedly — preventing the catastrophic scenario of DNS failure from domain loss.

For DNS record changes and potential hijacking, monitoring your domain's DNS records for unexpected changes provides an additional security and availability layer. This is covered in what is WHOIS monitoring.

How External Monitoring Handles DNS

When your external uptime monitor checks your website:

1. The monitoring server performs a DNS lookup for your domain
2. It connects to the resolved IP address
3. It makes the HTTP/HTTPS request
4. It evaluates the response

If DNS is failing, the monitor will report a DNS error — a distinct failure type from a server error. Good monitoring tools surface this distinction, helping you diagnose whether the problem is DNS, the server, or the application.

Multi-location monitoring is especially valuable for DNS issues — DNS failures can be regional, affecting users in one area while others can still resolve your domain fine.

Checking Your Current TTL

To check the current TTL on your DNS records:

# Check A record TTL
dig yourdomain.com

# Check TTL at a specific DNS server
dig @8.8.8.8 yourdomain.com

# Check CNAME TTL
dig www.yourdomain.com CNAME

The TTL value in the response shows how many seconds remain before the cached record expires.

Monitor DNS availability and website uptime in real time at Domain Monitor.

Related Articles

• What Is Database Monitoring and Why Does It Affect Website Uptime?
• DNS Record Types Explained - A, CNAME, MX, TXT and More
• Advantages and Disadvantages of Using Website Monitoring In Your Company