logoalt Hacker News

misker1 • today at 9:26 AM • 4 replies • view on HN

I wanted to share our journey of running our own DNS server (it's not as scary in the age of AI, but still...). If anyone has questions I can answer them.


Replies

koito17 • today at 11:56 AM

If you're running a k8s cluster, you're already running a DNS server. It shouldn't be too scary IMO, but I've also wasted a lot of time writing DNS-related libraries and application in the past, so I'm probably biased.

I find the following part of the article interesting.

  These [DNS] records would need strong consistency too. When a basin is created, its address should be instantly resolvable, otherwise clients would be waiting around for a cached NXDOMAIN to expire.
DNS is, almost by design, an eventually consistent system. Strong consistency would mean authoritative servers for a zone have to coordinate updates and agree on the current state before answering queries. That would almost defeat the availability goals that date back to the very origin of DNS. To quote the very old RFC 1034:

  Access to information is more critical than instantaneous updates or guarantees of consistency
I am guessing S2 has clients query a specific DNS server directly so that there is strong consistency in practice. Also, it's unclear to me whether it's intended for records to propagate to other name servers. It'd be nice if the article included an appendix for people who don't know what S2 is (or how clients typically access the service).
➕ show 2 replies
xtiansimon • today at 12:52 PM

I manage my own DNS record at zoneedit (set it and forget it). What’s something else (tricky, instructive, whatever) about running your own DNS that I don’t experience?

➕ show 1 reply
slyall • today at 11:32 AM

What is the scale on the graph?

➕ show 1 reply
bigstrat2003 • today at 4:25 PM

It was never scary. DNS is a very simple service.