The Day the DNS Died
summary
SparkPost runs 8,000 DNS queries per second and hits undocumented cloud limits that throttle at roughly 1,024 qps per network interface, which causes 90%+ query loss and seven-hour mail delays. The response is a ground-up DNS tier: dedicated VPCs, per-tier resolver clusters, multiple ENIs/IPs, local caches (dnsmasq) per instance, tuned Unbound with serve expired, and network ACLs to avoid stateful security-group tracking. The redesign restores availability and survives subsequent DNS incidents.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:50Introduction
- 2:20Version 1. Centralized Internal Resolver Cluster
- 5:00Version 2, AWS VPC Resolver
- 6:19Version 1.5. Centralized Internal Resolver Cluster
- 20:27New DNS Design
related talks
29mDNS: Old Solution for Modern Problems
25mDark Side of the DNS Force
34mIt’s Always DNS: So Let’s Break It On Purpose
28mDarwin & Protocols
15mYou Depend on DNS, This Is How It Works and You Won't...
09mDNS is the entry point for every application on the internet
01h 27mDNS at 30
26mMisuse of DNS, the Second Most Used Protocol
