Automating your DNS
summary
Shows how DNSControl (Stack Exchange) uses a domain-specific JavaScript DSL to put DNS under git with PRs, CI/CD previews and API-token provider access (Cloudflare, Azure, AWS and others). Demonstrates editing dnsconfig.js, running check/preview, catching ambiguity errors, merging a PR and pushing changes; demo partially succeeds due to caching. Cites why this matters: public resolvers handle trillion queries/day, 82% of companies report DNS-caused downtime, and the tool is provider‑agnostic so missing providers get added via API-backed plugins.
AI-written summary · about
chapters (14)
- 0:00DNS automation intro
- 1:04DNS security risks
- 5:23DNS origin and evolution
- 7:53How DNS works today
- 11:06Unmanaged DNS problems
- 13:13DNS as code with Git
- 15:17DNS Control tool
- 16:41DNS Control’s approach
- 25:52Live demo setup
- 27:15Configuring DNS records
- 32:27DNS Control CLI
- 35:40Adding DNS changes
- 49:13Demo takeaways
- 50:15Q&A on DNS Control
related talks
32mInfra: Give Developers Autonomy with OctoDNS
18mThe parts of DNS nobody explained to you
22mHow We Un-Scattered Our DNS Setup and Unlocked New Automation Options
52mCalloused DNS: doing it right
20mWhat's in a Name? Your Guide to the Wacky World of DNS
37mDig Smart: Building a Reliable Cloud Native DNS for Modern Networks
38mCoreDNS: Intro and Deep Dive
38mInfra: Give Your Developers Autonomy with OctoDNS