From: Kevin Chadwick <ma1l1ists@yahoo.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to prevent a dns amplification attack
Date: Thu, 28 Mar 2013 20:51:51 +0000 [thread overview]
Message-ID: <20130328205151.7d03b413@kc-sys.chadwicks.me.uk> (raw)
In-Reply-To: <CAGK8UzAvszaBKCXeC-7t1LP8pqF+dEYLsQ9woVUBYcd6JFsuWA@mail.gmail.com>
On Thu, 28 Mar 2013 16:12:04 +0100
Volker Armin Hemmann <volkerarmin@googlemail.com> 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 haven't looked into it but.
You could perhaps reduce the amplification by looking for trends that
maximise response sizes such as the 100x amp against spamhaus of late,
but you would be fighting against the wind and only buying time.
Rate limiting may work but bear in mind that so many servers could be
used that attacks maybe ongoing and you wouldn't notice, again you may
be able to make attackers need to be subtler or go to more effort like
for spam but you are not going to eradicate it.
Really you would need some sort of network of dns servers communicating
about who they are hurting as thankfully there is often a single
victim, but really it would be better if the IETF had listened to the
dangers and even now simply redesigned DNSSEC.
As for tcp I used to have all my OpenBSD clients resolvers using the tcp
option in resolv.conf but I haven't noticed another OS's resolver with
that option. There are decent protections against syn floods but I
assume you are wanting random clients to connect.
next prev parent reply other threads:[~2013-03-28 20:51 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 [this message]
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
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=20130328205151.7d03b413@kc-sys.chadwicks.me.uk \
--to=ma1l1ists@yahoo.co.uk \
--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