kate3
Member
- Joined:
- Jul 2024
- Posts:
- 208
- From:
- Utrecht, NL
Month four was DNS propagation delays yes up to 3600 seconds
3600 seconds is the TTL ceiling on most .tk zones, not propagation lag. The registry caps it deliberately. Your "delay" was probably resolver cache expiry, not upstream push failure. Check with
dig +trace
next time; if the authoritative returns immediately but Cloudflare/Google cache stale, that's on you for not tuning TTL down before the incident.
Still, 400-second failover is respectable for a free TLD. Most people running these things do not even have a second registrar.
virsh list --all | wc -l: 47
JokoNord
Member
- Joined:
- Jun 2024
- Posts:
- 190
- From:
- Jakarta, ID
The 7 minutes minhmin reports is probably similar geography yes
Sir, very good analysis sir. I use RackNerd Los Angeles, very far from my Jakarta customers sir. But price is good sir. I think I will study your script and make for my .id domains sir, .id not free but stable sir, worth it for customer trust sir. Thank you very much for sharing sir.
traffic worse than my packet loss
YuriDavid
Member
- Joined:
- May 2024
- Posts:
- 174
- From:
- Kyiv, Ukraine
.id not free but stable sir
.id is PANDI, local Indonesian registry. They had a 3-day outage in 2021, DNSSEC key rollover went wrong. Not free, not immune. The only stable domain is the one you have tested failover for.
Also: spaces. Tabs are for people who hate their colleagues.
indentation is not optional
zoekyo
Member
Less Is More
- Joined:
- May 2024
- Posts:
- 102
- From:
- Kyoto, JP
The only stable domain is the one you have tested failover for.
This. I run one small server in Tokyo, one domain, paid, no failover script. If it breaks I fix it. The alert is my users emailing me. Less is more. The overhead of monitoring three free registries across two continents sounds like a second job.
Guru deutschlag, your efficiency is impressive but I wonder at the cost in attention.
rm -rf / --no-preserve-root ☯