Scriptable GeoDNS: leaving AWS for Bunny
Not investment advice. Muhabbit scores how much a story may matter, not which way to trade.
A blog operator migrated asset delivery and geo-aware DNS from Amazon CloudFront and Route 53 to Bunny.net’s Bunny CDN and Bunny DNS, citing Route 53’s US$0.50 per zone monthly fee, US$0.70 per million geolocation queries, US$0.75 per health check per month and US$1 monthly KMS charge for DNSSEC signing. Bunny DNS, introduced in 2022 and now nearly free for up to 500 domains, runs user-supplied JavaScript on each query; the operator uses it to return the two nearest of seven NixOS virtual machines located in Paris, Nuremberg, Ashburn, Singapore, San Jose, São Paulo and Sydney. The switch was uneventful, with content served from the b-cdn.net domain, separate caching per image format for AVIF and WebP negotiation, and logging disabled to limit personal data collection. The main drawback is Bunny CDN’s lack of HTTP/3 support, which the Slovenia-based company said it is working on without giving an ETA. The move highlights price pressure on AWS’s DNS and CDN bundles from lower-cost European providers courting small publishers with programmable features.
Muhabbit's AI wrote this summary in its own words from Hacker News's report. It can get details wrong, so check the source.
Named in this story
Bunny.net, Amazon Route 53, Amazon CloudFront, AWS