Posted by dabinat 8 hours ago
So it's content DNS service; with server-side resource record shuffling; and with JavaScript, and badly written examples that don't check the question type, just to make it weird.
I've owned domains for ~20 years... I'm okay for paying for the domain, I'm okay with some of that money being used to maintain the DNS servers... I've never had a company charge for queries. Why would they do that?
Dynamic, geo routed, load balanced low TTL queries tend to have a fee.
We're doing discovery on API key scopes at the moment, we don't yet have a public ETA for this but rest assured it's being worked on!
Regarding IPv6-only origin support, We brought this in just last week! We now support IPv6-only addresses direct as an origin, as a hostname, as well as dual stack hostname resolution.
Best, Joe
If you had have supported API key scoping then I'd have a ton of businesses/startups running on you. As it stands currently it's difficult for me to recommend you to orgs that are scaling up. Compliance in particular was the biggest issue. For one-man shops it's a no-brainer.
In your defense, Cloudflare has historically also sucked in this area.
Anyways, I'm looking forward to this feature!
How does the USD1 minimum works? Say I have setup a pull zone and i don't use it for over a month, I get charged anyway?
Thanks.
So, my scripts on my servers dont have the bunny api key. Its only saved within those edge functions and I authenticate against the edge functions.
A little bit more effort than scoped keys but it works
- Akamai DNS
- AWS Route 53
- Azure DNS
- Cloudflare (excluding personal/hobbyist plan)
- Google Cloud DNS
And many, many others. And I note the site you posted this comment on is using Route 53, so probably paid as I doubt their query volume would be in the free tier.
Paying for DNS for personal/hobby stuff is probably pretty uncommon, because like you say, most domain registrars will offer it for free. But commercial websites often will, particularly larger ones with serious traffic.
Otherwise, that is my observation also.
A good provider will have different locations across the world, and users connect to the nearest datacentre. The free DNS some domain registrars offer is, sometimes, hosted at one single location. If the server is in the US and the user is in Europe, you're adding 80-150ms to requests. If they use "anycast" servers, the user could connect to a server 1-20ms away.
The only annoyance is that their domain import auto-detects existing records, but it seems to miss a lot of them so you end up manually copying a lot of things over anyway.
(Excluding NSEC-style enumeration, which is not always available.)
Spirit: ensure you keep a good copy of your zone files (bind format), their import / export has issues (it also doesn't include SOA or NS records). I spent time (before the recent fixes) manually validating records.
https://registry.terraform.io/providers/BunnyWay/bunnynet/la...
I deploy my website using their API. So on every push, GitHub Actions builds it and copies the dist/ to Bunny and purges the cache afterwards. Everything has been working perfectly. I can only recommend. It's also quite easy if you don't know about the modern way of doing things and just want to use an FTP to put your website online. Especially attractive for IndieWeb folks.