• floquant@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      33
      arrow-down
      1
      ·
      edit-2
      6 days ago

      Yeah, I don’t get the point of including a protocol together with 3 big corpos. Use a recursive resolver (with caching) instead of a forwarding one, and it’s fully decentralised at the TLD level. If the root nameservers or .com’s stop responding, either your uplink is down or the internet as we know it has ended

        • 4am@lemmy.zip
          link
          fedilink
          arrow-up
          14
          ·
          5 days ago

          It’s a haiku:

          It’s not DNS

          There’s no WAY it’s DNS

          …it was DNS.

      • marcos@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        5 days ago

        for some reason

        You mean things tend to fail at the highly redundant eventually consistent format-agnostic global distributed database and not on the stateless data transformers?

        Who could have guessed?

    • mlg@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 days ago

      Me waiting for the remaining 60% of vulnerable records to enable DNSSEC