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?

    • cracked_void@kbin.earthOP
      link
      fedilink
      arrow-up
      1
      ·
      20 hours 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.

    • kalpol@lemmy.ca
      link
      fedilink
      arrow-up
      5
      ·
      1 day ago

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

      • Link@rentadrunk.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        22 hours ago

        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?

        • khannie@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          20 hours ago

          Reverse lookups are comparatively time consuming and a single IP may resolve to many domain names.

        • cracked_void@kbin.earthOP
          link
          fedilink
          arrow-up
          1
          ·
          20 hours ago

          It’s not the ISP I’m most worried about, although, in regard to their TOS, that one seems to go south, too.

  • tal@lemmy.today
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    1 day ago

    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.

  • hexagonwin@lemmy.today
    link
    fedilink
    arrow-up
    4
    ·
    1 day 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)

      • unexposedhazard@discuss.tchncs.de
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        1 day ago

        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.

        • cracked_void@kbin.earthOP
          link
          fedilink
          arrow-up
          3
          ·
          1 day ago

          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.

          • muxika@piefed.muxika.org
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 day ago

            What would be a better alternative that you’d recommend to hide a public IP? I’m familiar with self-hosting, so I could deploy the necessities.

  • neidu3@sh.itjust.worksM
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 day ago

    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

      • neidu3@sh.itjust.worksM
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 day ago

        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.

        • Balinares@pawb.social
          link
          fedilink
          arrow-up
          2
          ·
          19 hours 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.