• non_burglar@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 day ago

    That enables an amplification attack.

    Technically, you’re right.

    An amplification attack is just telling the server to respond to a different/wrong ip with the response to a query than the actual asking request. This is solved generally with DNSSEC verifying the origin and requester ips match, if not, the request is dumped.

    However, if your authoritative server doesn’t have records for the request, it will simply forward it (if configured to do so) to an upstream and probably hardened server, or drop the request. Either way, it becomes not your problem.

    So unless the amplification attack is asking for records your server is actually hosting and for which your server is authoritative, this isn’t a huge concern.

    • hendrik@palaver.p3x.de
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 day ago

      Thanks! Learned something today. Last time I opened port 53 to the public it didn’t take long and I was sending out several Megabits per second in DNS traffic. Constantly. Mostly querying the same few things. But I guess I had it the wrong way round and that wasn’t the target. Or I’ve seen a different attack type… Guess I can now try again with the new knowledge.