Avoiding DNS Pain
summary
Large public outages (April Azure, July Akamai-related, September Slack, October Meta, December AWS) expose DNS as a single point of failure; attacks scale via compromised credentials and dangling DNS entries that let attackers re-register deleted targets. Recommended fixes are concrete: perform a DNS maturity assessment, manage zones with DNSControl using a JavaScript IaC DSL, run git-based PRs with preview/test and push to production, use builders for SPF/DMARC and respect the 10 DNS lookup limit, and note support for 40–50 providers.
AI-written summary · about
chapters (4)
related talks
28mAvoiding DNS Pain
34mPractical Steps for Reducing Exposure and Detecting Compromise
12mHow DNS doesn’t work!
22mDNS is Under Attack - the Miscreant's Offensive Playbook with a Defensive Counter
01h 27mDNS at 30
25mDark Side of the DNS Force
09mDNS is the entry point for every application on the internet
47mDNS On Fire