How We Un-Scattered Our DNS Setup and Unlocked New Automation Options
summary
Company owns over a hundred domains spread across five registrars and 30+ name servers, causing slow lookups and rollout limits. Teams consolidate registrars, adopt Google Cloud DNS, and put DNS as YAML in Bitbucket with Bitbucket pipelines that lint, load a custom resource record database (trie-backed Go validator), run a staging deployment, then require a peer review before production. Deploy pipeline takes ~1.5 minutes, staging check ~45s, enabling fast rollbacks, automated safety checks, open-sourced tooling and automated Let's Encrypt certs via Kubernetes ingress.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:45What is the Problem here?
- 6:12Divide and Conquer DNS Data
- 7:29Do we really have competing goals?
- 9:25Zone Data (Template)
- 10:32Resource Record Database (RRDB)
- 10:55RRDB Internals: Trie Data Structure
- 12:10RRDB Internal: Today's Features
- 13:10RRDB Internals: Past Disasters
- 14:55New Deployment Workflow
- 17:59Benefits of New Process
- 19:41Battle-tested Existing Tools
- 20:16Achievements Unlocked
related talks
54mAutomating your DNS
32mInfra: Give Developers Autonomy with OctoDNS
37mHandling the Largest Domains Migration, Ever!
31mManaging thousands of DNS records in a GitOps fashion using Ansible and NS1
38mHow we revolutionized developer experience with 3.5 Platform Engineers
37mDig Smart: Building a Reliable Cloud Native DNS for Modern Networks
31mHow We Went From Two Major Outages to 99.98% Reliability in 6 Months
35mGitOps or a Journey to a Production Incident and Swiftly Back Again