From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to prevent a dns amplification attack
Date: Thu, 28 Mar 2013 23:06:52 +0700 [thread overview]
Message-ID: <CAA2qdGXpviGjyzMs6t37VzB9m5vqEvUVcDWJ1fFavmA5V6eefQ@mail.gmail.com> (raw)
In-Reply-To: <515463E0.60607@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
On Mar 28, 2013 10:38 PM, "Michael Mol" <mikemol@gmail.com> wrote:
>
> On 03/28/2013 04:51 AM, Norman Rieß wrote:
> > Hello,
> >
> > i am using pdns recursor to provide a dns server which should be usable
> > for everybody.The problem is, that the server seems to be used in dns
> > amplification attacks.
> > I googled around on how to prevent this but did not really find
> > something usefull.
> >
> > Does anyone got an idea about this?
>
> I'm not sure it can be done. You can't make a resolver available to
> "everybody" without somebody in that "everybody" group abusing it, and
> that's exacly what happens in a DNS amplification attack.
>
> Restrict your resolver to be accessible only to your network or, at
> most, those of the specific group of people you're seeking to help.
>
> You *might* try restricting the resolver to only respond to TCP requests
> rather than UDP requests, but if the resolver sends response data along
> with that first SYN+ACK, then nothing is solved, and you've opened
> yourself up to a SYN flood-based DoS attack. (OTOH, if your resolver
> went offline as a result of a SYN flood, at least it wouldn't be part of
> an amplification attack any longer...)
>
Can't we rate limit UDP DNS request?
E.g., limit each source IP to, let's say, 1 UDP per second?
That should be doable easily using iptables.
Rgds,
--
[-- Attachment #2: Type: text/html, Size: 1748 bytes --]
next prev parent reply other threads:[~2013-03-28 16:07 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 8:51 [gentoo-user] How to prevent a dns amplification attack Norman Rieß
2013-03-28 9:07 ` Adam Carter
2013-03-28 22:16 ` Norman Rieß
2013-03-28 15:12 ` Volker Armin Hemmann
2013-03-28 20:51 ` Kevin Chadwick
2013-03-28 20:57 ` Kevin Chadwick
2013-03-28 21:04 ` Michael Mol
2013-03-28 22:36 ` Kevin Chadwick
2013-03-28 15:38 ` Michael Mol
2013-03-28 16:06 ` Pandu Poluan [this message]
2013-03-28 16:10 ` Michael Mol
2013-03-28 18:26 ` Norman Rieß
2013-03-28 19:16 ` Alan McKinnon
2013-03-28 19:38 ` Michael Mol
2013-03-28 20:02 ` Alan McKinnon
2013-03-28 20:53 ` Paul Hartman
2013-03-28 20:59 ` Michael Mol
2013-03-29 0:49 ` Peter Humphrey
2013-03-29 8:53 ` Norman Rieß
2013-03-29 13:27 ` Alan McKinnon
2013-03-29 13:36 ` Michael Mol
2013-03-29 22:34 ` Paul Hartman
2013-03-29 23:01 ` William Kenworthy
2013-03-29 23:09 ` Michael Mol
2013-03-30 4:07 ` Walter Dnes
2013-03-30 12:06 ` Norman Rieß
2013-03-30 14:53 ` Rene Rasmussen
2013-03-30 15:15 ` [Bulk] " Kevin Chadwick
2013-03-30 15:30 ` Tanstaafl
2013-03-30 15:11 ` Kevin Chadwick
2013-03-30 16:44 ` Norman Rieß
2013-03-30 17:30 ` [gentoo-user] Re: [seriously O/T] " Mick
2013-03-29 13:24 ` [gentoo-user] " Alan McKinnon
2013-03-28 16:53 ` Jarry
2013-03-28 19:40 ` Paul Ezvan
2013-03-31 2:08 ` Paul Hartman
2013-03-31 8:47 ` Jarry
2013-03-31 19:07 ` Norman Rieß
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA2qdGXpviGjyzMs6t37VzB9m5vqEvUVcDWJ1fFavmA5V6eefQ@mail.gmail.com \
--to=pandu@poluan.info \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox