i've been working on a website to let you do DNS experiments and as always I'm surprised by how many design decisions there are to make for such a small-scale project
even leaving the UX design aside (which is so hard!!), I have absolutely 0 motivation to do maintenance work on my projects, so I need to be careful now to make sure I don't have to do maintenance later
one decision was whether to make the DNS server distributed to improve latency. I decided to run just 1 server with the HTTP server and DNS server sharing a process because managing distributed systems really sucks and it's an educational project, it's ok if it's a bit slow
I need to live stream DNS queries to clients as they come in. I spent a bunch of time thinking about how to do this (firebase? redis?) and eventually decided -- they're in the same process! I can just send the queries directly using a Go channel. No need to add a component.
originally I was letting anyone set any arbitrary dns record on any subdomain and I got stressed about the security implications of that, so I had to spend a few hours figuring out more secure way to do that which doesn't add friction for users
• • •
Missing some Tweet in this thread? You can try to
force a refresh
