• IphtashuFitz@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    2
    ·
    7 months ago

    That’s yet another reason to use a DNS as blocker, and not let your browser use DNS over https.

    I haven’t done it myself yet, but I figure that sooner or later I’ll need to update my router to block all outbound DNS that doesn’t go through my DNS ad blocker. Some devices try to use their own hardcoded DNS to get around them…

      • IphtashuFitz@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        7 months ago

        DNS blocking is about the only way to block ads & tracking on things like streaming devices. You can’t install Firefox or uBlock on an Apple TV for example. You can block ads on many of the apps on the Apple TV as well as all the telemetry they try to collect with a well configured pi-hole and selected DNS blocklists.

        • Flying Squid@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          7 months ago

          True, but using a computer with an adblocker and a second gen Chromecast (which you don’t need Chrome for) also eliminates that.

    • TheEntity@lemmy.world
      link
      fedilink
      English
      arrow-up
      13
      ·
      7 months ago

      DNS-based ad blocking is unfortunately much less effective. It’s still better than nothing though, that’s for sure.

      • IphtashuFitz@lemmy.world
        link
        fedilink
        English
        arrow-up
        10
        ·
        7 months ago

        A multi-layered approach is the best approach. My pi-hole blocks advertising domains, malware domains, etc. That helps tremendously with all the “smart” devices that include DVRs, streaming devices, etc. where you can’t install something like ublock. I also make sure something like ublock is installed wherever possible.

      • AA5B@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        7 months ago

        Because then it can bypass your ad-blocking DNS

        DNS over HTTPS was a great idea for privacy if left in your hands, but immediately ran into the reality of intrusive advertising

      • Hexarei@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        Because dns ad blocking is typically done with something like dnsmasq which doesn’t support DNS over HTTPS, though it’s easy enough to setup a resolver/forwarder that does

    • yeehaw@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      7 months ago

      No, it’s another reason to use Firefox. A Brower that is not owned and managed by an advertisement company.