DevOps / SRE / Platform · 30.07.2026, 15:04 UTC
DNS is infrastructure. It’s time to manage it that way.
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | The New Stack ↗ |
| Veröffentlicht | 30.07.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
Attackers aren’t always the reason for DNS failures — they can often be something much more routine.
For example, the failure could result from regular domain management operations at the registrar level, as one study points out.
A live example of DNS failure was the Cloudflare 1.1.1.1 2025 DNS global outage last summer that lasted for 62 minutes. It occurred not because of a cyberattack, but a misconfiguration in their systems.
Anthony Eden, founder and CEO of DNSimple
Beyond routing traffic, domains carry business value, intellectual property, and brand identity for enterprises, which is why those enterprises spend large sums on them.
Those domains breathe inside the vendor dashboard — whether a registrar’s or a DNS host — and multiple stakeholders manage them manually, often leaving no record of who changed what.
When asked about the management gap, Anthony Eden, founder and CEO of DNSimple — a developer-focused domain management automation and DNS hosting company — tells The New Stack, “Most engineers who are working at companies are already required to use tools like Terraform or Ansible to control all of their other services. So that means deploying servers and managing storage instances, things like that.
“And I think DNS and domain management need to be treated the same way.”
Domain management as code
According to Eden, domains deserve the same operational rigor an enterprise applies to its servers, cloud infrastructure, and deployments. In enterprises, Terraform already provisions compute and storage as Infrastructure as Code (IaC). DNS belongs in …