Switching to Bunny DNS

A recent post by Henrique made me look into Bunny DNS again. In the past I already tried it for one or two domains but eventually stopped using it because they didn’t support DNSSEC yet. Instead I relied on the wonderful services of DeSEC. But now that support for DNSSEC and TLSA records is finally here, I switched again to Bunny DNS with all 21 of my domains.

Making the switch was pretty easy with DNSControl. The only manual part was changing all the nameserver entries and DNSSEC records at the registrars. I bought most domains from Spaceship (because they are the cheapest), but some also from Netcup (again, because they regularly offer really cheap prices for .de and .eu) and my one .se domain from Simply.com.

Bunny is also a European provider, and as I also use Bunny CDN for some things like the media files on this blog, it allows me to use their deeper integration with the CDN. That way I can directly specify CDN pull zones as record type, and Bunny DNS will directly serve the A/AAAA records instead of an intermediary CNAME. And pull zones at the apex domain are possible as well.

Let’s see if I will stay within the free tier of 20 million DNS requests per month. But given that I have 40 dollars of credits (mostly from promotions) left in my account and my regular Bunny bill is just a few cents per month (I registered before their mandatory $1/month), I don’t really care.

A pretty niche wish from me is that Bunny CDN would allow using a custom ACME provider for TLS certificates, as they are using Let’s Encrypt, and I would like to use Actalis instead. But I can also live with Let’s Encrypt for the public files I serve via Bunny CDN.