In a log below, with pWr, he claims there is a bug in the new code .. I'm pasting his conversation below along with the info on a person who supposedly had utilized the bug.
Bob khaki is [EMAIL PROTECTED] * khaki *** Looking up microsoft.com *** Resolved microsoft.com to 207.46.197.102 /userip khaki [EMAIL PROTECTED] [0:25] <pWr> i've used it, works nicely [0:26] <pWr> not many people have it [0:26] <pWr> like 4-5 [0:26] <pWr> just letting you guys know > care to say any more about where the bug is or how it is used? [0:26] <pWr> sure [0:27] <pWr> dns ID sequencing. Every DNS packet has a 'unique' ID, it's only an int and can hold 65536 possible values. er.. what it boils down to, is if you can predict the packet ID, and send a response packet back to the querying DNS server before the real DNS server answers(ie: it's being DoS'd), it doesn't know the differance.
