Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Vuln-Dev
[Top] [All Lists]

Re: recursive DNS servers DDoS as a growing DDoS problem

Subject: Re: recursive DNS servers DDoS as a growing DDoS problem
Date: Tue, 21 Mar 2006 00:01:13 +0000
Michael Sierchio <kudzu@tenebras.com> writes:

Robert Story wrote:

VG> In the scenario you describe, I cannot see any actual amplification...

The amplification isn't in the number of hosts responding, but in packet 
size.
A very small DNS request packet results in a huge response packet.

Are you talking about rogue authoritative servers?  Otherwise, responses
will be limited to 512 bytes, possibly with the truncation bit set.

Unless it supports EDNS, in which case it may be persuaded to send
larger replies. BIND does currently have "you cannot be serious"
cutoff at 4096 bytes.

The reason that it is more awkward to use the method against
authoritative-only nameservers is that you have to find a large
RRset in the wild (or one that will come with large authority and/or
additional sections in the reply) and then use the authoritative 
nameservers for that RRset, not any old open recursive nameserver 
(or many of them). You cannot craft your own RRset for the purpose. 

But you can still get amplification, certainly.

-- 
Chris Thompson
Email: cet1@cam.ac.uk

<Prev in Thread] Current Thread [Next in Thread>