Scriptable GeoDNS: Leaving AWS for Bunny

Posted by sshah03 1 hour ago

Comments

Comment by askbjoernhansen 22 minutes ago

The "cloud provider rates" for this are a bit crazy. It's great bunny.net is offering a (more flexible!) product basically for free.

The NTP Pool does ~1m dns queries a second on the hourly peak with a small-ish (old) Go program (called `geodns`) running on a bunch of mostly small VMs around the world. The average is much less, but paying $0.70/million for ~11 billion queries a day would be a lot of money for a "random volunteers on the internet" project at "cloud provider rates".

Comment by whinvik 24 minutes ago

I actually went and looked at the linked Terraform blog post and I realized something.

It mentions that you used CDKTF because you prefer its expressiveness. The actual TF is generated from CDKTF. Having struggled with understanding and writing TF in the past, now, I don't really have to care with agents. I let them rip, then just read the plan output.

I am sure we will find more such examples where we can rip out an intermediate step completely because of agents.

Comment by arm32 34 minutes ago

Bunny's scriptable DNS is something I geek out so hard over. Bunny's DNS products in general, actually, are highly underrated. Kevin, my offer still stands to come work on it! :P

Comment by temp0826 30 minutes ago

Hasn't stuff like this been solved with anycast and typical routing algorithms of old etc? Or is this solving a different problem? (This doesn't affect me but have been considering moving some stuff from aws/cloudflare to bunny)

Comment by PaoloBarbolini 27 minutes ago

Very few providers offer anycast. It's also kind of simpler to take servers from multiple providers and have DNS be the integration layer between all of those.