full-disclosure - DDos counter measures

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20030815011237.GB34696@beast.magicnet.org>
From: gael at magicnet.org (Gael Martinez)
Subject: DDos counter measures

Try some other tests using no A record for windowsupdate.com in your local zone,
you will notice that the damages are even smaller doing that instead of localhost (127.0.0.1).

Gael


On Thu, Aug 14, 2003 at 08:04:54PM +0200, Laurent LEVIER wrote:
> All,
> 
> Since our IntraNet solves all its DNS queries through internal caches 
> (mandatory bottleneck), we created windowsupdate.com & 
> windowsupdate.microsoft.com zones in this bottleneck DNS. These are 
> resolving to 127.0.0.1 with DNS wildcards.
>