• 3 Posts
  • 32 Comments
Joined 4 months ago
cake
Cake day: March 19th, 2024

help-circle














  • Bluetooth can do it locally, but yes, for things on ZigBee or Z-Wave, it’s gotta have an antenna hub. WiFi switches and lights most likely do “phone-home” to the cloud in some way (usually for color or brightness control via app, Govee especially loves this). The down side, other than the obvious privacy implications, is that if your ISP has an outage, so do your switches.

    Home Assistant attempts to mitigate both the privacy and offline issues, while putting all of the different brands and hubs into one place.





  • AmbiguousProps@lemmy.todaytoPrivacy@lemmy.mlQuad9 censoring DNS requests?
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    2 months ago

    but then once you’ve thousands of servers running the same piece of software across the globe deploying updates and features becomes way slower and way harder. You’ve to consider tests, regressions, a way to properly store and sincronize the blocklists across nodes etc…

    This is what we’re trying to explain to you, this is how DNS works. Those thousands of servers? Recusrive DNS resolvers, ran by Cloudflare. All watching and caching the records from Cloudflare’s authoritative nameservers in near real time, because that’s how it was designed. You don’t need to test for regressions, figure out how to properly store and synchronize the “blocklist” (it’s not a blocklist, it’s changing a domain record or simply using a CNAME to point to the registrar) or whatever else, because DNS is continuous, and it was designed to do what you’re describing, in the 90’s.

    Yes, if you’re updating your infrastructure, you’d want to test. But this isn’t that.

    Ever ran into an expired domain and thought about how the registrar can just park an expired domain and make it an ad for themselves? That’s just them adding a CNAME in their authoritative nameservers, which gets distributed globally. The prior delinquent owner can still be hosting, but because they don’t have the authoritative nameserver they can’t use the domain anymore.


  • AmbiguousProps@lemmy.todaytoPrivacy@lemmy.mlQuad9 censoring DNS requests?
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    2 months ago

    What you said here is not really on topic, but it is literally part of DNS. I already explained it in my other comment, but here:

    DNS, by design, uses authoritative nameservers, which is what cloudflare and quad9 host. These authoritative hosts distribute their records to caches (usually just recursive DNS resolvers) to ease and distribute the load. It’s literally in all of their documentation, and explained in pretty plain english on their pages.

    https://www.cloudflare.com/learning/dns/what-is-dns/

    https://www.quad9.net/about/

    Much of the Quad9 platform is hosted on infrastructure that supports authoritative DNS for approximately one-fifth of the world’s top-level domains, two root nameservers, and which sees billions of requests per day.

    When a record is updated in your domain (or cloud) provider, it is distributed via an authoritative nameserver hosted by that company. These get distributed to the root name servers, which then distribute the records to other authoritative nameservers.