• ram@bookwormstory.social
    link
    fedilink
    English
    arrow-up
    29
    ·
    1 year ago

    Any moderation or oversight is considered “abuse”, even if it’s a result of the instance admins completely failing in their due diligence. Really, how poorly did they moderate CSAM as to necessitate their registrar stepping in???

  • Rob Bos@lemmy.ca
    link
    fedilink
    arrow-up
    11
    ·
    1 year ago

    It’s so easy to run your own DNS servers, I don’t expect that it’ll be offline long, unless it’s the registrar.

    • KairuByte@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      15
      ·
      1 year ago

      Running your own DNS server doesn’t do much, unless your users are polling that DNS server, or a DNS server that pulls from it. No large DNS provider is going to honor your random ass DNS servers mappings, and that’s a good thing.

      And honestly, trusting some random DNS server isn’t a good idea. All it takes is one malicious entry and https://google.com suddenly loads in a cryptominer.

        • KairuByte@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          7
          ·
          1 year ago

          Yes, but my browser doesn’t give a fuck. As it should be for many reasons, including general security.

          Your DNS only works for services/machines you have explicitly set to follow it, or devices under them in the network hierarchy.

          • Rob Bos@lemmy.ca
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            That is nonsense. DNS is a federated system and my servers are authoritative for my domain.

      • jmcs@discuss.tchncs.de
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        I think he means he’s running the name server for his zone (i.e. the authority for subdomains of his domains), which of course doesn’t help if the top level domain gets suspended and the NS record gets deleted.

    • Melmi
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      It looks like the registrar changed the nameserver, which is a harder thing to recover from. Still, didn’t keep them down for long. Looks like they figured something out