Building and Operating a Highly Reliable Cloud Native DNS Service With Open Source Technologies
summary
On‑prem cloud native DNS for Swisscom 5G is implemented with PowerDNS and ExternalDNS backed by per‑cluster databases and a CoreDNS forwarding layer; it serves private zones at tens-to-hundreds rps, supports rare records like NAPTR after an ExternalDNS fix, and exposes a load‑balancer IP for external consumers. A multi-cluster geo-redundant setup uses independent ExternalDNS instances that cross‑write so three clusters stay in sync, failover works when one PowerDNS is killed, and reconciliation repopulates records.
AI-written summary · about
chapters (11)
- 0:00Introduction to DNS reliability
- 2:10DNS in 5G core requirements
- 5:03Kubernetes DNS and architecture
- 9:16Automating DNS with ExternalDNS
- 12:29Demo 1: Basic service DNS
- 16:04CoreDNS forwarding setup
- 17:07Demo 2: CoreDNS and external access
- 20:21Multi-cluster DNS architecture
- 22:25Demo 3: Cross-cluster synchronization
- 28:00Limitations and achievements
- 31:31Q&A session
related talks
38mTowards the Cloud Native Telco: Learning from the Trenches
40mThe Rocket Science of Deploying Cloud Foundry in Multi-Cloud Environments
49mSwisscom's pioneering journey to run regulated workloads on AWS(SEC205)
42mOperating a multi-tenancy Kubernetes service on KubeVirt
30mLiberate Your Cloud Foundry Installation From Being Constrained to a Single Cloud
06mResiliency in a service provider world
23mGlobal Scale - Geo-Distributed Ingress
39mCloud Native at PostFinance - Is it completely normal?