logoalt Hacker News

It's always DNS, so why are we running our own?

59 points • by misker1 • today at 9:19 AM • 45 comments • view on HN

Comments

mx7zysuj4xew • today at 3:40 PM

> "It's always DNS"

This is a stupid meme that became a truism that really needs to die.

Stop mystifying basic network services.

All you're doing is scaring people off from running their own independent services leading to further consolidation and monopolization of the web

➕ show 1 reply
talkingtab • today at 4:07 PM

What came to me as I read this is the prevalence of Bread Making Machines. It seems to me We have becomes a society that thinks we cannot do things. Bread making is a skill that was pretty universal - and without a machine. Now, instead of learning the skill, we buy a machine or get a library or pay a service. In many cases these {machines, libraries, services} work in simple cases but have severe limitations. Plain Old People developed DNS and all the other networking things. (thank you Van Jacobson, et al.)

There is a lot of complexity out there, but I have found many times that the solutions that protect you from that complexity are often as complex or more so.

reticulates • today at 12:10 PM

I'm not familiar with your product, just the blog post + cell architecture documentation. Question: the documentation states that basins are assigned to a cell on creation and cannot move. Why choose to have explicit DNS records instead of wildcards with a subdomain per location? e.g: {basin}.us-east-1.s2.dev where *.us-east-1.s2.dev points to the cell? My best guess is that you prefer to have explicit architecture in case you need to move to a new cell for some reason, but maybe there was a different reason? The stuff around hitting the database on every query that necessitates a firewall seems like a huge risk vs. a wildcard CNAME which adds no additional burden.

➕ show 2 replies
bajard • today at 12:58 PM

My ISP kept intercepting, editing and blocking my DNS queries. I had to encrypt, obfuscate, self-host, re-route and randomize them to get rid of this harassment.

➕ show 2 replies
MiscIdeaMaker99 • today at 1:35 PM

Back in the day, I remember running our own DNS servers because we had customers who wanted to white-label our product with their own domains, and _lots_ of marketing departments didn't want to deal with their IT people, so we offered to host DNS for them. Of course, that's assuming they had IT people at all.

About half of the domains were registered by us on behalf of the customer, while the other half delegated a sub-domain to us. There was also a small minority who hosted all of the DNS themselves.

getfacl • today at 11:50 AM

Out of curiosity, was using PowerDNS with CloudSQL (fed from a spanner stream) considered?

There are always trade offs of course but it would have the advantage of DNS spikes not impacting spanner.

➕ show 2 replies
whinvik • today at 1:51 PM

I am very curious how they decided to have most infra in GCP but only DNS on AWS Route 53. I would expect that one could have everything on just GCP no?

The other interesting thing that I am starting to think more about is that every part of the infra stack will get slowly rebuilt because of AI. More load, more granular permissions, more firewalls are some of the things I can think that will need to be built in.

➕ show 4 replies
TacticalCoder • today at 1:47 PM

DNS is incredibly complex IMO. But I still run unbound at home: it s of course not the same thing as running a publicly facing DNS.

But being able to blacklist hundreds of thousands, heck probably millions, of domains that are homoglyph attacks on my usual banking and brokers website is just too good to pass upon.

I started doing that after my broker sent me a warning by email about a phishing site that was a 100% perfect copy of the real thing. Basically:

    mycoolbroker.com
vs:

    mycoo1broker.com
Of course I use 2FA etc. But I still wouldn't want my credentials phished and then using those an attacker could try to reset the 2FA.

So I wrote a little piece of code generating a shitload of potential homoglyphic attacks on my most important sites' names.

I also blacklist a great many TLDs entirely. So many countries get null routed / NX_DOMAINed.

And so many ads disappear. And sk many domains serving porn and malware.

All going down the drain.

I love it.

As a side note I also reject trafic from a huge number of IP blocks (entire countries / entire ISPs / entire companies like Meta).

It s amazing how much of the Web / Internet keeps working just fine after all that.

It s also pretty much something you set up once then forget about it.

And I did all that in the pre-LLM days. Now it s even easier.

➕ show 1 reply
misker1 • today at 9:26 AM

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.

➕ show 3 replies
icedchai • today at 3:27 PM

How frequently are new DNS records being added / modified?

➕ show 1 reply
andrewstuart • today at 12:23 PM

You are. Not me.

arbor-group • today at 2:57 PM

[flagged]

ehteshamaliii • today at 2:03 PM

[flagged]

dominojab • today at 1:56 PM

[dead]