Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

By mistake typed while trying to visit and landed to localhost. The url resolves to localhost somehow, even with google's DNS server.

Just for curiosity sake, does any one have any idea why resolves to localhost?

C:\Windows\System32>nslookup Server: Address:

Non-authoritative answer: Name: Address:

C:\Windows\System32>nslookup Server: Address:

* can't find Non-existent domain


share|improve this question

closed as not a real question by voretaq7 Nov 6 '12 at 20:14

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

DNS admins can set the records up however they like. Perhaps the admin wanted to set to for testing purposes. In a past job I set quit to resolve to a CNAME of because nslookup in interactive mode doesn't accept quit as a command to quit the program, and that was just a pointed reminder. – cjc Nov 6 '12 at 20:08
@Faisal: you were trying to browse but you looked at, which resolves to – petrus Nov 6 '12 at 20:29
up vote 5 down vote accepted

Because the owner of the domain name set it up that way.

share|improve this answer
That makes sense. Thanks. – Faisal Nov 6 '12 at 20:27

It resolves to localhost because the DNS admin for domain created an A record pointing to

share|improve this answer

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