My ISPs DNS lookup takes literally one second every time, so I went with Quad9, it really sped up my browsing. Do you know any other alternatives?

top 42 comments

sorted by: hot top controversial new old
[–] 12 points 6 months ago

Mullvad has a free DoH service.

  • source
  • [–] 11 points 6 months ago* (last edited 6 months ago) (1 child)

    You could probably just piggyback off some random DNS server out there that permits public queries. I doubt that most domains are logging everything.

    $ egrep "^[a-z]+$" /usr/share/dict/words|shuf|sed "s/$/.com/"|xargs -n1 host -t ns|grep "name server"|cut -d" " -f 4|awk '!seen[$0]++'|xargs -n1 host www.slashdot.org|awk '/^$/ {f=0} /has address/ {f=1} /^Name:/ {if (f) {print}}'
    Name: ns2.afternic.com.
    Name: ns1.bluehost.com.
    Name: ns2.bluehost.com.
    Name: ns-570.awsdns-07.net.
    Name: ns1.sedoparking.com.
    Name: ns02.cashparking.com.
    Name: ns01.cashparking.com.
    Name: ns1.namefind.com.
    Name: ns2.namefind.com.
    

    etc.

    That'll look up the DNS server for a bunch of domains and, omitting duplicates, list all of the ones that can resolve "www.slashdot.org", which I imagine likely means that they'll also probably be willing to resolve other domains.

    EDIT: Modified the above command line to randomize the order of domains it tries so that if multiple people use this, everyone doesn't just grab the same DNS server.

  • source
  • hideshow 1 child comment
  • [–] 9 points 6 months ago (3 children)

    There's not a ton - however you found Quad9 would have told you about the others.

    https://www.privacyguides.org/en/dns/

  • source
  • hideshow 3 child comments
  • [–] [S] 4 points 6 months ago (2 children)

    Huh, I didn't know AdGuard also runs a DNS service. Who is AdGuard, anyway? Their stuff seems so corpo.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 6 months ago

    Mullvad is probably the most trustworthy one.

  • source
  • [–] 5 points 6 months ago (1 child)

    I use NextDNS, which allows to set filtering rules.

  • source
  • hideshow 1 child comment
  • [–] [S] 1 point 6 months ago

    I didn't know that one too. They seem to be based in the US, and apparently they seem to be a profit-oriented organization. I'll keep them in the back of my mind, maybe I'll consider them in a few years.

  • source
  • parent
  • [–] 4 points 6 months ago

    Depends on where you're at. If that's Germany or close to it, we have the Digitalcourage DNS server, OpenNIC. I haven't tested anything else but there's also dnsforge.de, Digitale Gesellschaft in Switzerland, and of course Quad9 who operate globally.

  • source
  • [–] 4 points 6 months ago

    i just use Quad9 too, or firefox's builtin DoH cloudflare since i'm a bit lazy.. (though it's very likely not a good option)

  • source
  • [–] 7 points 6 months ago (4 children)

    The concept of a privacy friendly DNS resolver is a paradox. You can hope that they dont log your traffic, but you will never know.

  • source
  • hideshow 4 child comments
  • [–] [S] 8 points 6 months ago (3 children)

    Exactly, but isn't it better to have tried and fail than to not try at all?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 6 months ago (2 children)

    Sure yeah, but i think the better argument for switching is decentralization. Its dangerous for everyone to depend on one or a few monopolistic DNS providers. Thats also why you shouldnt use cloudflare.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 3 points 6 months ago (1 child)

    You're totally right. In the long run I'll probably get myself some selfhosted solution, but right now I want to focus on other things. Also, I stay away from Cloudlare as far as I can. I don't trust them.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 6 months ago*
    • mullvad.net
    • dnsforge.de
  • source
  • [–] 3 points 6 months ago (3 children)

    I always used 4.2.2.2 and 4.2.2.1. Not sure how privacy friendly they are, but probably miles more than 8.8.8.8

  • source
  • hideshow 3 child comments
  • [–] 4 points 6 months ago (2 children)

    I'll admit I'm not sure what the threat model is with 8.8.8.8.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 6 months ago (1 child)

    Well, it belongs to Google, so I assume they use it for logging which addresses do which lookups, and correlate this with their other fingerprinting databases. I very much doubt they run a public DNS just to be nice.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 6 months ago

    I mean, that'd be a major GDPR breach, be hard to extract any signal from because queries will usually be coming from a relay or from behind a NAT so you can't tell who the query even originates from, and DNS is cached heavily too so you only get a small fraction of the queries anyway. I'm not seeing a way the calculus work in favor, basically.

    OTOH the question of why they'd even run a public DNS is interesting, yeah. Running a public DNS is cheap and helps the Internet work better, and they make more money when the Internet works better since that adds up to more page views. Less charitably, though, it's possibly just a thing from back when they were an engineering company first and foremost and did that kind of stuff, and now they can't turn it off without breaking a lot of things and causing a lot of costly anger.

  • source
  • parent
  • [–] 3 points 6 months ago (1 child)
  • [–] 5 points 6 months ago (5 children)
  • [–] 5 points 6 months ago (4 children)

    The only downside here is that the root servers don't use TLS so your queries are plain text.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 6 months ago (2 children)

    Why does that matter when your ISP will know the IP of the server and a reverse lookup is probably very easy to find what domain you visited?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 6 months ago (4 children)
  • [–] 8 points 6 months ago (3 children)

    You still have to perform lookups by reaching out to the root resolvers.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 6 months ago

    I use DNS.watch and oisd in conjunction with a locally hosted caching dns proxy server.

  • source
  • [–] 1 point 6 months ago (3 children)

    I've been using a PiHole for years now. It's super easy to set up. In practice, it's been the most reliable thing I keep on a pi. Technically, you don't need to host it on a raspberry pi, but you should host it on an always-on computer on your network.

    Kind of a different way of looking at security; you can't guarantee someone's not keeping DNS logs, but you can guarantee that your DNS logs on a hard drive in your house aren't being shared.

  • source
  • hideshow 3 child comments
  • [–] 3 points 6 months ago (2 children)

    you still need to point the pihole somewhere though

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 6 months ago (1 child)

    Unbound is a better solution. It queries the root, TLD, and authoritative servers recursively. Then it caches the response (for a quicker response next time). It works flawlessly with Pi-hole.

    https://nlnetlabs.nl/projects/unbound/about/

  • source
  • parent
  • hideshow 1 child comment
  • [–] -3 points 6 months ago (2 children)

    Cloudflare (1.1.1.1) is pretty good.

    Of course, if you are self hosting, have a look at Unbound - also works nicely in combination with PiHole.

  • source
  • hideshow 2 child comments