Analyze your domain's DNS TTL settings under two key lenses: Everyday Page Load Latency vs. Server Migration Readiness.
| Host / Record | Type | Target / Value | TTL (Duration) | Everyday Performance Lens | Migration Lens |
|---|---|---|---|---|---|
| siteanalyzerfree.com | A |
192.168.1.168
|
1 day (86400s) | Optimal Speed | 24h Prep Needed |
| siteanalyzerfree.com | NS |
ns4.a2hosting.com
|
1 day (86400s) | Optimal Speed | 24h Prep Needed |
| siteanalyzerfree.com | NS |
ns1.a2hosting.com
|
1 day (86400s) | Optimal Speed | 24h Prep Needed |
| siteanalyzerfree.com | NS |
ns2.a2hosting.com
|
1 day (86400s) | Optimal Speed | 24h Prep Needed |
| siteanalyzerfree.com | NS |
ns3.a2hosting.com
|
1 day (86400s) | Optimal Speed | 24h Prep Needed |
| siteanalyzerfree.com | SOA |
Primary NS: ns1.a2hosting.com (Admin: root.mi3-ss119.a2hosting.com)
|
1 day (86400s) | Optimal Speed | 24h Prep Needed |
| siteanalyzerfree.com | MX |
[Priority 0] mail.siteanalyzerfree.com
|
4 hours (14400s) | Optimal Speed | 24h Prep Needed |
| siteanalyzerfree.com | TXT |
google-site-verification=eSwdO--SNMVSYZtNKQlQ9fSmzY8F1SJEzwZEFapSNQw
|
4 hours (14400s) | Optimal Speed | 24h Prep Needed |
| siteanalyzerfree.com | TXT |
v=spf1 +a +mx +ip4:66.198.240.24 include:spf.a2hosting.com ~all
|
4 hours (14400s) | Optimal Speed | 24h Prep Needed |
| siteanalyzerfree.com | SOA |
Primary NS: ns1.a2hosting.com (Admin: root.mi3-ss119.a2hosting.com)
|
24 hours (86399s) | Optimal Speed | 24h Prep Needed |
| siteanalyzerfree.com | A |
192.168.1.168
|
1 day (86400s) | Optimal Speed | 24h Prep Needed |
| www.siteanalyzerfree.com | CNAME |
siteanalyzerfree.com
|
1 day (86400s) | Optimal Speed | 24h Prep Needed |
Planning a server move? 24 hours BEFORE updating your A/CNAME record IP addresses, reduce their TTL setting in your DNS portal to 300 seconds (5 minutes). This ensures fast propagation during the cutover.
Once your server migration is complete and verified stable for 24 hours, remember to raise your TTL values back to 3,600s or 86,400s to regain optimal DNS caching performance.
DNS Time-to-Live (TTL) is a numerical setting (measured in seconds) attached to every DNS record. It dictates how long recursive DNS resolvers, ISPs, and web browsers are permitted to cache your server's IP address before requesting a fresh update.
When you set a low TTL (e.g. 300s / 5 minutes) on a domain that is not migrating, every returning visitor's browser or local ISP must continuously send fresh DNS queries to resolve your server IP. This adds an extra 20ms to 150ms round-trip latency to page load times. For everyday stability, TTLs should be set to 3,600s (1 hour) or 86,400s (24 hours).
If you are planning to switch web hosts or move to a new server IP, follow this two-step process:
1. 24 hours BEFORE migration: Reduce your A and CNAME TTL values to 300s (5 minutes).
2. 24 hours AFTER migration: Once the new IP is verified stable, raise your TTL back to 3,600s or 86,400s to regain maximum DNS caching speed.