Hacker News Reader

Comment by tomzin0 | Hacker News Reader

Thanks but no thanks. https://www.quad9.net/news/press/quad9-faces-new-dns-censors...

So they provide full information on what happened, with all legal papers attached at the end, and a link to a site that gives you a list of all "blocked sites" that where effected by that order.

While the outcome is quite unfortunate, the way they provide all info here seams like a plus in my book here.

If a state/entity comes after your org tomorrow, and you got to either fight legally or leave the market (like cisco in the story), what would you do?

The French legislation is targeting all major resolvers, Quad9 is not really any better or worse than others just for this.

A niche resolver may get away under the radar, but only because they were not targeted.

So then what do you use or recommend instead?

Mullvad [1], dns.watch, dnscrypt [2]

1 - https://mullvad.net/en/help/dns-over-https-and-dns-over-tls

2 - https://dnscrypt.info/public-servers/

I use a combination of 1.1.1.1, 9.9.9.11, and OpenDNS over DNSSEC via Pihole. Not sure if it's a "good" strategy, though.

I think the France legislation is aimed at most major resolvers. You might get away with more niche ones for now, but the only stable way is to self-host a recursive resolver (like unbound) that walk the DNS tree themselves.

Host your own dns resolver. It isn't hard.

Hosting is never hard. It's about maintainability. How do you handle HA? How will you expose the service? What about backups? How efficiently are you running it? That's just the tip of the iceberg. For an average joe, this is not something they wanna deal with

Bro it's a DNS server. People happily run Pi-holes without all that.

Good luck when something goes wrong, which it will. At the very least, you need HA for pi-hole which is easy to do with something like nebula-sync

> (1) How do you handle HA? (2) How will you expose the service? (3) What about backups? (4) How efficiently are you running it?

We are talking a DNS resolver at home or on a VPS.

1. you don't need HA, if it dies you revert back to your ISP DNS while you fix it. And you always have a secondary resolver set up anyway.

2. you just set up its ip address as first dns server on your home router and as DoH on your devices browsers.

2. you don't need to back up a local resolver, the only data it has is cache.

4. a local DNS resolver serving the needs of a household needs very little resource.

You are doing a bare minimum job which is of course not what I intended. Your workloads doesn't seem to be that sensitive. If you can afford a few minutes of downtime, sure. I cannot afford downtime because lots of critical services will fail which will require manual intervention

Reply on news.ycombinator.com