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

My x64 windows 2003 box is not resolving names in the hosts file in system32\drivers\etc. I have been testing with nslookup with no luck.

There was not a syswow64\drivers\etc\hosts so I created one and entered the same hosts also with no luck. Should I reboot to get this one to work?

I've done the ipconfig /flushdns and /registerdns a few times with no luck.

share|improve this question
nslookup communicates directly with your DNS server, so it would not look at your hosts file. You'd want to use ping or some other application that uses the normal methods to resolve a hostname and lets you know what IP it got. – DerfK Nov 2 '10 at 14:40
aaah you are correct. I thought by changing the server used to it would work, but with some testing that doesn't appear to be the case – Dave Nov 2 '10 at 15:29
up vote 2 down vote accepted

forgive me if the response is to basic. It is quite unusual that this is not working and it appears you have taken all of the right steps. Something as simple as the hosts file should just work when entries are being added to this file.

Take a look at Microsoft KB article are there any other uncommented out lines in the hosts file aside from the ip and host to resolve?

share|improve this answer
Thanks I re-created the hosts file and it works now. Can't believe something so simple escaped me for that long. – Dave Nov 2 '10 at 15:32

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.