Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

While troubleshooting a network timeout/connectivity WinHTTP issue, I temporarily added a host file entry for:

(The server has no internet connection and the firewall was causing some extended timeouts -- I wanted to temporarily set it to a local address for it to fail immediately).

For some reason though, even after flushing DNS cache, ping attempts still go to the actual IP.

This got me to thinking: Are there certain FQDNs which Windows 2008 absolutely will not acknowledge host file entries for? Perhaps for malware/virus protection?

share|improve this question
Are you running a through a proxy server>? – AliGibbs Jul 13 '12 at 15:46
@AliGibbs Nope. That's the strange part. – Mike B Jul 13 '12 at 15:50
Just tried it on one of my Windows 2008 Servers- exactly the same behaviour- same with - very strange. – AliGibbs Jul 13 '12 at 15:53
up vote 7 down vote accepted

This has been "known" for quite a few years actually.

if you look in the dnsapi.dll (in system32) you'll see a string of hosts.

There's a



I don't believe Microsoft ever commented on it, but I guess the intent was to prevent malware and other tools from adding entries to the hosts file.

share|improve this answer
That's exactly what I needed to know. Thank you! – Mike B Jul 13 '12 at 16:25

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.