Bunny DNS goes free: the CDN moat just swallowed another category

What happened

Bunny.net — the Slovenian CDN that has been quietly eating Cloudflare's lunch at the price-conscious end of the market — just made its authoritative DNS service free for everyone. No query cap, no zone cap, no record cap. GeoDNS, latency-based routing, and the smart DNS features that previously sat behind a metered tier are all in the free SKU. The blog post frames it in the company's house style ("a faster internet won't build itself"), but the move is unambiguous: DNS is no longer a line item on Bunny's invoice.

The context matters. Bunny had been charging roughly $0.40 per million queries for its DNS product, which is competitive with Route 53 but more expensive than Cloudflare's free tier. Pulling DNS to zero removes the last metered friction in their funnel — sign up, point your nameservers, and you're already a customer before you've ever swiped a card. The post explicitly positions this as an infrastructure-bootstrapping play, but the unit economics tell a simpler story: a DNS query costs Bunny almost nothing at the volumes they already serve for their CDN, and every domain that points NS records at `bunny.net` is a domain that's one click away from also enabling Bunny's edge cache, storage, optimizer, and DNS-based traffic steering.

The HN thread (627 points at the time of writing) is mostly positive, with the predictable subthread asking the predictable question: if it's free, what's the catch? The honest answer is in the topology. Bunny needs you on their nameservers anyway to route CDN traffic optimally. Charging for DNS was always slightly self-defeating.

Why it matters

This is the second time in fifteen years the developer-facing DNS market has been reset to zero, and it's worth understanding why it keeps happening. DNS is a structurally terrible standalone business: the marginal cost of a query is microseconds of CPU and a UDP response, the switching cost for customers is a 5-minute nameserver change, and the product is undifferentiated by design — RFC 1035 doesn't leave much room for proprietary value-add. The only durable moat is anycast network presence, and anyone who has built that for a CDN already has the DNS infrastructure as a byproduct.

Cloudflare understood this in 2010 and used free DNS to bootstrap what became a $20B company. Bunny is running the same play in 2026, but the market they're entering is different. The standalone DNS specialists — DNSimple, easyDNS, ClouDNS, NS1 (now IBM), Constellix — have spent fifteen years arguing that you should pay for DNS because of better support, better APIs, better observability, or better routing logic. Some of those arguments are real. None of them survive contact with a competitor who gives the base product away to subsidize their CDN.

The interesting question is what happens to the long tail. Route 53 will be fine because it's a captive AWS-internal product; you don't pick it, you inherit it from your account setup. Cloudflare DNS will be fine because it's already free. The squeeze is on the middle: providers whose entire pitch is "managed authoritative DNS with a better dashboard." Their TAM just shrunk to enterprises with compliance requirements that exclude consumer-grade providers, and that's a small, slow-growth market.

There's also a quiet centralization story here that the HN comments mostly miss. Every domain that moves to Bunny is a domain whose resolution path now depends on a single Slovenian company's anycast network. That's fine until it isn't — see the Cloudflare DNS outage in July 2025 that took out a substantial slice of the internet because secondary NS providers had also been quietly consolidated. "Free DNS" is a benefit for the operator and a slow-rolling systemic risk for the internet as a whole. The right architectural response is to run a secondary on a different network — Bunny's free tier actually makes this easier, not harder, because you can now afford a secondary you couldn't justify paying for.

What this means for your stack

If you're already on Bunny's CDN, this is a no-brainer migration. Move your zones over, save the line item, and use the GeoDNS features you probably weren't paying $0.40/M for before. The API is reasonable, Terraform support exists via the community provider, and the dashboard is actually faster than Route 53's.

If you're a Cloudflare DNS user with no CDN attachment, there's no reason to switch — Cloudflare's DNS is mature, fast, and equally free. The migration cost isn't worth the marginal performance delta. But this is a good moment to set up a secondary nameserver on Bunny as a redundancy play. Multi-provider DNS is one of the cheapest resilience wins in production and the free tier removes the last excuse not to do it.

If you're paying for DNSimple, NS1, or any boutique provider, do an honest audit of what you're actually getting for that money. If the answer is "a nicer dashboard" or "the API is slightly better," that's not enough justification anymore. If the answer is "DNSSEC with key rotation that doesn't require a PhD," "audit logs that satisfy SOC 2," or "a support contract with a human on the other end," the premium is probably still worth it — but the gap is closing.

For anyone running a small SaaS or side project, the practical upshot is that you can now build a globally-distributed, GeoDNS-routed, CDN-fronted application for $0/month at the edge layer, with the only meaningful cost being origin compute. That's a meaningful shift in what one person can ship without a budget meeting.

Looking ahead

The DNS-as-loss-leader pattern is now a fixed feature of the CDN market, which means the next category to fall is probably WAF or basic bot mitigation — both of which Cloudflare already gives away on the free tier and which Bunny will almost certainly follow on within 18 months. The CDN business is increasingly a bundle where the headline product (cached HTTP traffic) is the only metered component and everything else is glue to keep you from churning. For developers, this is mostly good news. For investors in pure-play DNS or pure-play WAF companies, the writing has been on the wall for a while; today it just got underlined.