Bunny.net zeros out managed DNS — pressure shifts to Cloudflare and Route 53

What happened

Bunny.net announced today that its managed DNS product is now free for everyone, with no query limits, no zone limits, and no tier gating. The pricing page that previously listed $0.20 per million queries and a small per-zone fee now reads $0. Existing paid customers get refunded the prorated balance on their next invoice. The post frames the move bluntly: *"a faster internet won't build itself."*

The product itself isn't a stripped-down loss-leader — it runs on Bunny's existing 130+ PoP anycast network, supports DNSSEC, ANAME/ALIAS flattening at the apex, geo-steering, latency-based routing, and per-record health checks. These are the features that historically separated Route 53 and NS1 from the free tier of Cloudflare DNS. Bunny is keeping them all and pricing them at zero.

The HN thread (158 points and climbing) is split between two reactions: long-time Bunny customers cheering a vendor that keeps shipping aggressive pricing moves, and skeptics asking the obvious question — *how long does free last when the VC clock starts ticking?* Bunny is bootstrapped and profitable on CDN revenue, which is the relevant context most commenters are missing. DNS is a rounding error on their infrastructure bill; giving it away is a customer-acquisition tactic for the rest of the stack.

Why it matters

Managed DNS pricing has been weirdly sticky for a decade. Route 53 has charged $0.50 per hosted zone per month plus $0.40 per million queries since roughly 2013. NS1's enterprise tiers start in the four figures monthly. Cloudflare gives DNS away but couples it tightly to their proxy and analytics. Bunny just collapsed the entire pricing axis: same enterprise feature set, zero dollars, no requirement to put your traffic through their CDN.

The economics here aren't mysterious — DNS queries cost approximately nothing once you've built an anycast network for other reasons. A query is ~70 bytes in, ~150 bytes out, served from RAM, no upstream egress. The marginal cost rounds to zero. What Bunny figured out is what Cloudflare figured out a decade ago: if you already have the PoPs for CDN, the right price for DNS is whatever maximizes downstream attach to the things that *do* cost money. Cloudflare's bet was tying DNS to the proxy. Bunny's bet is that a frictionless on-ramp to their CDN, edge storage, and video platform converts better than charging twenty cents per million queries.

The community reaction in the HN thread is worth reading carefully. The top-voted concern isn't pricing sustainability — it's lock-in via proprietary features. ANAME flattening, geo-steering rules, and Bunny's specific health check semantics don't export cleanly to BIND zone files. If you adopt the advanced features, your migration cost away from Bunny is non-trivial even if the data itself is portable. That's not unique to Bunny — Route 53's alias records have the same property — but it's the right thing to think about before you cut over.

The second substantive concern: DNS resilience as a single point of failure. The 2016 Dyn DDoS, the 2021 Akamai Edge DNS outage, the recurring AWS us-east-1 Route 53 control plane incidents — all argue for secondary DNS with a different provider. Bunny going free doesn't change that calculus; it makes it cheaper. Run Bunny as primary, Cloudflare or deSEC as secondary, and you've eliminated a class of correlated failure for $0/month.

What this means for your stack

If you're paying Route 53 for DNS and not using it as part of a broader AWS-integrated setup (health checks tied to ELBs, failover routing tied to CloudFront), the migration is genuinely a few hours of work for measurable savings. A 100-zone account doing 50M queries/month is paying ~$70/month to Route 53 for what Bunny is now giving away. That's not life-changing money for a Series B, but it's a clean win for the long tail of side projects, agencies managing client domains, and small companies that ended up on Route 53 because it was the AWS default.

If you're on Cloudflare DNS already, the case to switch is weaker. Cloudflare's free DNS has been good for years; the differentiation here is mostly philosophical (Bunny is bootstrapped and EU-based, Cloudflare is a public US company). The genuinely interesting move is using Bunny as the secondary for a Cloudflare primary — or vice versa — to get multi-provider DNS resilience without paying anyone.

The broader move to watch is what AWS does. Route 53 pricing hasn't moved in over a decade because there's been no competitive pressure on the enterprise feature set. With Bunny matching the feature checklist at $0, that pressure now exists. Don't expect Route 53 to go free — AWS doesn't operate that way — but expect the next pricing update to quietly drop the per-zone fee or raise the free query allowance.

Looking ahead

The interesting question isn't whether Bunny's free DNS sticks — they can sustain it indefinitely on CDN margin. The question is whether this triggers a broader unbundling, where every commodity edge service (DNS, basic WAF, simple load balancing) gets priced at zero by infrastructure companies that want your traffic. The CDN business is consolidating around a few players with enough scale to give the periphery away. If you're a DNS-only or WAF-only vendor in 2026, your pricing model is now under siege from companies for whom your entire product line is a customer-acquisition line item.