0

By mistake typed www.nanog.com while trying to visit http://www.nanog.org/ and landed to localhost. The url www.nanog.com resolves to localhost somehow, even with google's DNS server.

Just for curiosity sake, does any one have any idea why www.nanog.com resolves to localhost?

C:\Windows\System32>nslookup www.nanog.com 8.8.8.8 Server: google-public-dns-a.google.com Address: 8.8.8.8

Non-authoritative answer: Name: www.nanog.com Address: 127.0.0.1

C:\Windows\System32>nslookup www.nonexistingwebsite.com 8.8.8.8 Server: google-public-dns-a.google.com Address: 8.8.8.8

*** google-public-dns-a.google.com can't find www.nonexistingwebsite.com: Non-existent domain

C:\Windows\System32>

Faisal
  • 225
  • 1
  • 2
  • 6
  • 1
    DNS admins can set the records up however they like. Perhaps the admin wanted to set www.nanog.com to 127.0.0.1 for testing purposes. In a past job I set `quit` to resolve to a CNAME of `type.exit.you.fool` 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 06 '12 at 20:08
  • @Faisal: you were trying to browse www.nanog.org but you looked at www.nanog.com, which resolves to 127.0.0.1. – petrus Nov 06 '12 at 20:29

2 Answers2

5

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

Michael Hampton
  • 244,070
  • 43
  • 506
  • 972
2

It resolves to localhost because the DNS admin for nanog.com domain created an A record pointing to 127.0.0.1

kernelpanic
  • 1,276
  • 1
  • 10
  • 30