Dig Smart: Building a Reliable Cloud Native DNS for Modern Networks
summary
Swisscom builds a geo‑redundant cloud‑native DNS for its 5G core using ExternalDNS → PowerDNS with CoreDNS forwarders, deploying one PowerDNS plus local DB per cluster and cross‑cluster ExternalDNS instances that copy records into the other cluster; it runs tens–hundreds RPS, must be low‑latency, and supports advanced records like NAPTR/SRV. Automation is GitOps only (GitOps‑only control plane); live demos show record creation, cross‑cluster lookups, and failover when a PowerDNS or forwarder is scaled to zero, but limitations include intervaled sync, no health checks, no DNS round‑robin across clusters, and lost‑cluster entries not auto‑revoked.
AI-written summary · about
chapters (14)
- 0:00Cloud native DNS challenges
- 1:055G core DNS requirements
- 4:18DNS system architecture
- 7:35DNS server options for Kubernetes
- 9:24PowerDNS with ExternalDNS
- 12:16Live demo: DNS record creation
- 15:07DNS forwarding in clusters
- 17:39Live demo: DNS forwarding
- 18:00Multi-cluster DNS resilience
- 20:52Live demo: multi-cluster DNS
- 25:36Design trade-offs
- 28:25System achievements
- 29:30Resources and GitHub
- 29:53Q&A
related talks
54mAutomating your DNS
32mEnhancing DNS Reliability in Kubernetes With Node Local DN...
32mInfra: Give Developers Autonomy with OctoDNS
38mTowards the Cloud Native Telco: Learning from the Trenches
22mHow We Un-Scattered Our DNS Setup and Unlocked New Automation Options
38mIntro + Deep Dive: CoreDNS
38mCoreDNS: Intro and Deep Dive
38mCoreDNS Intro And Deep Dive