• 3 Posts
  • 133 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle





  • The first thing that pops up in my mind is your public IPv4. You see, in your home LAN every device uses the same public IPv4 to communicate in the internet. So if one device browses for something like an iPhone and you’re being tracked then those ad brokers deliver iPhone ads to this public IPv4 and every device behind this public IPv4 will see those ads. Nobody on the internet knows whether behind this public IPv4 is a single device or a LAN with many devices.









  • Vexz@kbin.socialtoPrivacy@lemmy.mlTime to ditch #duckduckgo
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Me too. I was so reluctant to pay for a search engine at first since there are good alternatives out there I don’t have to pay for. But I just at least wanted to try the first 100 free searches and was blown away by how great it is. It has some unique features like prioritizing or blocking specific domains, lenses and custom bangs. I payed the $10 the same day for Pro tier and 5 days later (yesterday) I even upgraded to Ultimate tier with ChatGPT-4 (called Kagi Assistant). I really, really enjoy Kagi so far. Most probably it’s gonna be my one and only search engine for the next years to come.




  • Looks like my answer wasn’t saved, great…

    Anyway, sorry for not reading all of that, but I’ll make it short and stop discussing because I feel like this is leading nowhere.

    Unless you’re using hyperlocal and cover all TLDs and wanna browse the internet there’s technically no way around but to use an online DNS server. So coming back to the privacy aspect of this topic the question is: Which one do you trust?


  • tl;dr: Cut out Cloudfare’s recursive resolver (or anyone else’s) and run your own via PiHole and Unbound.

    Tell me you didn’t read the article without telling me you didn’t read the article. Let me point out the relevant part for you:
    “A recursive resolver (also known as a DNS recursor) is the first stop in a DNS query. The recursive resolver acts as a middleman between a client and a DNS nameserver. After receiving a DNS query from a web client, a recursive resolver will either respond with cached data, or send a request to a root nameserver, […]”

    See that last part with “or send a request to a root nameserver”? That is the DNS server on the internet your Unbound DNS server will ask if it doesn’t have the answer cached for you already.

    Umm, Unbound is on your machine. So you’re saying you are your own middle man lol…

    Exactly! Since the Unbound DNS server is your server you created your middle man server yourself. “middle man” has a very negative taste but in this case it really isn’t bad at all.

    It asks the authoritative nameservers, which is who external DNS servers ask. By using Unbound, you are cutting out those external DNS servers, because you/Unbound is the DNS server. You are asking the authoritative name server directly instead of inserting someone else to ask on your behalf.

    Okay, so you get it but you don’t get it fully. Again: Your Unbound DNS server can’t magically know which IPs are behind a domain name. So what does it do? It asks a DNS server on the internet because they know the answer. When you Unbound DNS server got the answer it then tells your computer.

    Unbound (your machine) is asking the DNS nameserver.

    YES! And where do you think is the DNS server Unbound asks if it doesn’t know the answer because it’s not cached yet? It’s some server on the internet.

    You’re saying you are your own middleman lol.

    I said you create your own middle man. Unbound is your middle man in this case because you make it look up the IPs behind the domains and it tells your computer these IPs then.

    Instead of:
    \ –> asks –> \ –> answers –> \ You do:
    \ –> asks –> \ –> asks –> \ –> answers –> \ –> answers –> \ Let me say it again: Your Unbound DNS server being the middle man isn’t a bad thing so please don’t think “middle man” is always a negative term.

    I’m saying cut out Cloudfare’s recursive resolver and run your own via PiHole and Unbound.

    I just linked Cloudflare’s article about it because they explain it well. Doesn’t mean one must use Cloudflare’s DNS servers.

    Did you read the article I linked?

    Yes, I did. But I knew what a recursive resolver is before I checked the link because I’m a professional IT administrator and I know how DNS works. It’s part of my job.