full-disclosure - AW: 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>] [day] [month] [year] [list]

Message-ID: <DF79BE12AF8DD344B107D0D03621E5750ED9BA@kermit.corp.hansenet.com>
From: vogt at hansenet.com (vogt@...senet.com)
Subject: AW: DDos counter measures

> 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.

Is it necessary to add windowsupdate.microsoft.com to this? So far, all
analysis indicated that it attacks windowsupdate.com, the old legacy
site.
Or did I miss something?


best regards / mit freundlichen Gruessen,

Tom Vogt
Hansenet Webfarm Security