DNS propagation without the guesswork

Mano, after my VPS it crashed because DNS still point to old IP for 48 hours, I learn this the hard way. Now I want share so you dont suffer same.

The TTL Math:
Your old TTL is a promise. If he say 86400 seconds, resolvers can cache for 24 hours. Change TTL before you change record, not after!!

My timeline of shame:

• Day 0: A record TTL 86400, point to RackNerd
• Day 1: Move to Vultr, change A record, TTL still 86400
• Day 2-3: Caramba! Half world see old IP
• Day 3: Client angry, I learn about TTL

Tools I use now:

• dig +trace example.com — see full resolver chain
• Check-propagated.net (fictional but mano you get the idea)
• Google DNS 8.8.8.8 vs Cloudflare 1.1.1.1 vs local ISP
• Dnschecker.org for regional view

Pro tip: Lower TTL to 300 one week before migration. After stable, raise back. Your zone transfer cost more but your sleep cost less kkkkk.

Any other tools mano use?? Nossa I still learning this DNS thing.

Bro this is super useful!!!

One more tool: dnschecker.org shows propagation on map, 20+ countries!!!

Also dont forget about negative TTL!!! SOA minimum field!!! If record not exist before, resolvers cache NXDOMAIN also!!! Learned this when subdomain missing for 6 hours!!!

Price of mistake: one angry client, one free month from my pocket!!! Never again!!!