Live data from Hacker News

Bunny DNS – A scriptable DNS platform

bunny.net

81–90 of 90 posts

Re: Bunny DNS – A scriptable DNS platform

#81

Earlier quoted context omitted.

I guess I'm just curious about how far off we're talking about. Is it accurate by country? Accurate by general region if not the entire state? Depending on the purpose you're using it for I'm just wondering about the accuracy level for sake of "good enough" uses.

I would guess that it is accurate at the continent level.

Our goal was not to use this to orchestrate a global CDN, it's just one of the many use-cases and can be combined with anycast easily. This is just one example and we're not really trying to push GeoDNS specifically. What we envision is smart load balancing, backups, dynamic routing for validation or service discovery and a bunch of other things that are currently very painful to do. GeoDNS is an old concept and can be solved much better without scripting anyway.

In terms of accuracy, it is generally very accurate on a country level. Anything else is pretty useless.

Re: Bunny DNS – A scriptable DNS platform

#82
post #31

Earlier quoted context omitted.

> I strongly believe that it'd be way better for their clients if the client could just do `export default async function handleDns(event) { ... }` I'm the tech lead of Cloudflare Workers and you're absolutely right about this. We actually introduced such a syntax as an option a while back and are encouraging people to move to it: https://blog.cloudflare.com/workers-javascript-modules/ Your argument is exactly one of…

Thanks! This article is pretty much what I had in mind and exactly my 500-words argument! I don't know how I missed it. This is def one of the things that made me think Cloudflare Workers were not so polished. Are you hiring? I've got many more ideas where this came from :)

We're hiring too. You can help us make this amazing!

Re: Bunny DNS – A scriptable DNS platform

#83

I've been following Bunny (BunnyCDN/Bunny.net) for a while and love what they are doing. Couple of suggestions: • Every code snippet should be copy/pasteable (and work well), that article might be the entry point to what many are doing. • I have this feeling this is following Cloudflare's Workers style of `addEventListener('fetch', eventHandler);`. I need to write a 500-word essay on that, but the short version is th…

That was actually the original idea, then for compatibility reasons, we decided to take this path initially. We are exploring adding fallback support as well, given that it greatly simplifies things and DNS can't really afford to do a whole lot of waiting anyway.

Re: Bunny DNS – A scriptable DNS platform

#84

We serve thousands of custom domains for our SaaS customers. The end users of these domains are globally distributed and served from 14 different data centre locations across the world. To do the geo IP matching we tried a lot of things, third party services etc but couldn't find one that works well and are priced well. For example, the hosted DNS service we use also have a IP based filter chain feature but are price…

We don't strictly use an IP DNS database to figure out the location, but a series of factors that make it much more accurate than standard GeoDNS. Something we've had to do to improve our own routing for the CDN. We're constantly looking for feedback and how to solve problems, so make sure to reach out. Your feedback is what allows you to improve.

Re: Bunny DNS – A scriptable DNS platform

#85
post #7

Like the idea. But… 1) Claim privacy first and then have a cookie banner. 2) Say “routing” when you mean location/IP based DNS. 3) Is that a loosely typed language in the scripting engine? Not sure I would want DNS queries to be relying on that. I am sure there is still some innovation left in DNS. SDDNS I’d call it: Software defined DNS. Especially with the splinternet we are walking into these days. Just don’t thin…

Absolutely correct on the privacy. We're actually dropping everything from Google / Facebook and anything third-party at the moment (since it's not technically legal in Europe anyway). It will be a bit of a process though.

Re: Bunny DNS – A scriptable DNS platform

#86

Somewhat related (and shameless plug), I coded a Lua-scriptable (Javascript planned) DNS server a while ago[0]. I'm using it in a few low traffic domains, but the code needs some additional love :-) [0] https://github.com/luismedel/redns

I've been looking for something like this within my internal network.. I want scrip-table control over DNS.. but I run all Linux/Bsd's and this looks to be .NET are the instructions on running in Linux and/or Docker containers?

Hi. It runs out of the box in Linux (BSD not tested, but it runs in macOS too). I'm in the process of configuring automatic releases in Github and a proper Docker image.

If you need help, write me to luis at .com :-)

Re: Bunny DNS – A scriptable DNS platform

#87
post #70

Earlier quoted context omitted.

Can you explain why would DNS be limited to Web ?

It's not. It's just that "internet routing" really refers to routing protocols, while TFA seems to mean something completely different, and, really, specifically HTTP routing.

Feels like you could use this to monitor say some mail servers and use DNS result to "route" to a healthy one for example, or the closest geo. Web seems to be one specific use case, and I feel using "internet" is fair here.

"Routing" is more debatable if you really want to be pendantic, but if you want to be pendantic, you need to be precise on web vs internet :)

Re: Bunny DNS – A scriptable DNS platform

#88

Earlier quoted context omitted.

That's of course purely anecdotal, but recently I explored static site generators. One of these was Hugo(written in go, which is pretty young ecosystem, I'm not very familiar with). Everything was pretty straight forward. Other one was Gatsby v4 (seems like pretty mature JS project). Oh boy. Docs suggest multiple ways to initialize new project, depending which page you open and without clear explanation of the differ…

Fair enough. I do agree that JS-based libraries, frameworks, and tools tend to have bad docs and questionable API designs, compared to equivalents that I've used in other languages. There is some cultural issue there that I don't understand. But... this is an embedded scripting environment! You aren't using any of that stuff.

Yes and no. You're definitely less exposed to JS ecosystem, but it's often the same issue with available examples, code snippets, docs.

I've similarly bad experience with for eg. plugins for VS Code. I wanted to add more supported syntax to org-mode plug in, at which point I found that their test suite is messed up.

Of course none of this is inherently fault of JS as a language, but current development culture around it promotes use of lots of silver tape, which makes me nervous, when I have to use anything JS-based.

Re: Bunny DNS – A scriptable DNS platform

#89
post #57

Earlier quoted context omitted.

At my employer, some users register with a pm.me email address. When users contact us via email, they use a different protonmail address and never the pm.me address. I know you can never rely on the sender address, but from a support perspective this is still strange and extremely troublesome (for example it is tedious to assign the user to an account). I assume that Protonmail users can only receive emails with pm.m…

In ProtonMail you can have email aliases (different address for the same inbox). By default, user@protonmail.com and user@pm.me exist. You can both send and receive from them. > to block pm.me or to handle it like a throwaway address How is a pm.me address more throwaway than a GMail one? I would say it's the other way around, especially considering that many ProtonMail users pay for their email service, so it's more…

> You can both send and receive from them.

This is not quite correct. According to Protonmail:

> but sending emails from a @pm.me email address requires a paid account.

https://protonmail.com/support/knowledge-base/pm-me-addresse...

My criticism is: You should never use an e-mail address from which you cannot send. This has nothing to do with Protonmail but is a problem in general.

Re: Bunny DNS – A scriptable DNS platform

#90
post #57

Earlier quoted context omitted.

In ProtonMail you can have email aliases (different address for the same inbox). By default, user@protonmail.com and user@pm.me exist. You can both send and receive from them. > to block pm.me or to handle it like a throwaway address How is a pm.me address more throwaway than a GMail one? I would say it's the other way around, especially considering that many ProtonMail users pay for their email service, so it's more…

> You can both send and receive from them. This is not quite correct. According to Protonmail: > but sending emails from a @pm.me email address requires a paid account. https://protonmail.com/support/knowledge-base/pm-me-addresse... My criticism is: You should never use an e-mail address from which you cannot send. This has nothing to do with Protonmail but is a problem in general.

> but sending emails from a @pm.me email address requires a paid account.

Forgot that, I personally have a paid account and I think many people using Protonmail do, the free accounts are not so good.

> You should never use an e-mail address from which you cannot send.

Depends for what, if you subscribe to newsletters you don't have to send emails, but I agree it's pretty dangerous to use an email that you don't have send access for.

Post reply on HN