TTL
Time to Live: how long a DNS record is cached before it is looked up again.
TTL (Time to Live) is a value on every DNS record that tells DNS resolvers how long to cache the record before checking for an update. A TTL of 3600 means the record is cached for 1 hour. Low TTLs (60-300 seconds) mean changes take effect quickly but generate more DNS queries. High TTLs (86400 seconds = 24 hours) reduce DNS traffic but mean changes propagate slowly. Before making DNS changes, it is common practice to lower the TTL in advance so the old record expires quickly from caches worldwide.
Reference
Related terms
See also
Referenced on
- 25 DNS Jokes Every SysAdmin Will Painfully Relate To
- Brute-force defense for wp-login.php
- Build a DNS Resolver from Scratch in Node.js
- Build a DNS Resolver from Scratch in PHP
- Build a DNS Resolver from Scratch in Python
- Complete Guide to DNS Attacks and DNS Security (Prevention, Testing & Mitigation)
- Dangling CNAMEs and Subdomain Takeover Risk Across the Global DNS
- DNS Blog
- DNS Checker Bot & Scanner Documentation
- DNS Hijacking Explained: How Attackers Take Control of Your Domain's Resolution
- DNS Lookups in PHP: dns_get_record, gethostbyname, and Beyond
- DNS Lookups in Python: Complete Guide with dnspython
- DNS Propagation Checker
- DNS Propagation Myths Debunked: It's Really About Cache Freshness
- DNS Queries in Node.js: dns.lookup vs dns.resolve Explained
- DNS Rebinding Attack: How Browsers Are Tricked Into Bypassing Same-Origin Policy
- DNS Root Servers Explained: The 13 Servers That Run the Internet
- DNS Troubleshooting Tools: What the Pros Actually Use
- Fast Flux DNS: How Botnets Hide Behind Rapidly Rotating IP Addresses
- Free DNS & Network Tools
- Free DNS Lookup Tool
- Home
- How DNS Queries Work: A Developer's Guide to the DNS Protocol
- How to Report Port Scanning and Network Reconnaissance to an ISP
- How to Set Up a Custom Domain for Your Email (Google Workspace, Microsoft 365)
- How to Verify DNS Changes After Switching Hosting Providers
- HTTP Header Checker
- MX Record Lookup
- NXDOMAIN Attack: How Nonexistent Domain Floods Exhaust DNS Resolvers
- Phantom Domain Attack: How Unresponsive Domains Exhaust DNS Resolvers