full-disclosure - Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

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]

Date: Fri Apr 14 05:04:14 2006
From: nick at virus-l.demon.co.uk (Nick FitzGerald)
Subject: Microsoft DNS resolver: deliberately sabotaged
	hosts-file lookup

John Doe wrote:

> I don't even get the same IP address for that. I have 64.4.52.189 .
> I tried to change it in the host files with the same results. Next I will
> block that IP in my firewall and see what happens.

Think load-balancing, dynaminc content distribution hosting, etc.

Ahhhh...

So, the exception is not that the IP is hard-coded, but that the DNS 
resolver skips looking in hosts for that _domain_ and necessarily does 
a network DNS lookup...

Regards,

Nick FitzGerald