[Love Calm Quiet]

Being accustomed to typing: legacy... to go to MacNN legacy version, I accidentally hit return after only "leg" ...
which resolved to leg.com and to Welcome to LEG.COM
...which displayed the home page of my LocalHost (Apache) on iMac w/ 10.6.3

Something bizarre about my system? or about "LEG.com"?

PS: if I type leg.com into whois I discover that it IS a registered domain. But my Mac wants it to be my LocalHost
:/

EDIT: PPS: If I google "leg.com" then, yes, "www.leg.com" is first result returned. But clicking on the link takes me to localhost.
The mystery is killing me.

[ghporter]

Your DNS cache is apparently "goobered." For 10.5 and later, you open Terminal and enter:

Code:
sudo dscacheutil -flushcache

While this fix is very simple sounding, it will work 100% if it's just your DNS cache (which, by the way, is global to your machine). For a short time, your initial web page requests will take a little longer as the machine has to retrieve DNS data for each URL, but the cache will fill again quite quickly.

[Oisín]

Originally Posted by Love Calm Quiet 

Being accustomed to typing: legacy... to go to MacNN legacy version, I accidentally hit return after only "leg" ...
which resolved to leg.com and to Welcome to LEG.COM
...which displayed the home page of my LocalHost (Apache) on iMac w/ 10.6.3

Something bizarre about my system? or about "LEG.com"?

PS: if I type leg.com into whois I discover that it IS a registered domain. But my Mac wants it to be my LocalHost
:/

EDIT: PPS: If I google "leg.com" then, yes, "www.leg.com" is first result returned. But clicking on the link takes me to localhost.
The mystery is killing me.

That’s quite odd, really—going to leg.com takes me to my default Apache page, too (and in Danish, too). So I’m guessing it’s not just your DNS cache that’s messed up.

Looks more like perhaps the actual index page on leg.com contains a redirect to localhost.

[Spheric Harlot]

Works fine on the iPhone. It's a domainsquatter site.

[ghporter]

Yup, "Godaddy" has it. Perhaps there is some sort of "let's not waste our customers' time with Godaddy sites" thing with your ISPs...

[Love Calm Quiet]

Interesting possibilities, guys.

FWIW: Further info. Two of three Macs and 1 Dell here experience this same phenomenon... so it can't be ISP. Something about DNS cache (or Apache?)...

[ I'm waiting for other ideas before I dabble in clearing DNS cache ]

[Simon]

What DNS are you using?

Does the behavior change if you switch to Google Public DNS? 8.8.8.8, 8.8.4.4

[Love Calm Quiet]

Actually, on *this* iMac I've got listed:
4.2.2.1
4.2.2.2
8.8.8.8
8.8.4.4
[ BTW: are they attempted in the order listed - and does it hurt to have more than the (usual?) two? ]

[Simon]

I'd remove all the others and try just Google's. You can also use OpenDNS' at 208.67.222.222, 208.67.220.220.

[Love Calm Quiet]

Thanks for the OpenDNS suggestion, Simon.

Interestingly, even stripping down to just google's (& restart) changed nothing.

[Love Calm Quiet]

Okay, have now tried GHPorter's suggestion of
>> sudo dscacheutil -flushcache
And restarted
And tried the OpenDNS settings.

No changes.

Only other clue: the two machines (one Intel, one PPC) that keep offering LocalHost instead of leg.com have had first LAMP and then MacPorts installs
...any possible relation?

[Oisín]

Originally Posted by Love Calm Quiet 

FWIW: Further info. Two of three Macs and 1 Dell here experience this same phenomenon... so it can't be ISP. Something about DNS cache (or Apache?)...

Just to confirm that it’s not the ISP: I have three different networks available here, through two different ISPs; and two Macs (a Mac Pro and a MacBook). The MacBook resolves leg.com to the domainsquatter site on all three networks, and the Mac Pro resolves it to localhost on all three. One network uses Google’s DNS servers, the other two use identical ones (don’t know which, they both begin in 81.88).

Neither machine has had anything ‘special’, like LAMP or MacPorts, installed. In fact, I think their installs are pretty identical, as far as apps and plugins and things go. The OS is different, though: the MacBook is on 10.5.8 while the Mac Pro is on 10.6.3.

[Love Calm Quiet]

Thank you, thank you, Oisin...
So good to find out I didn't just get slipped some peyote.

For me also, the phenomenon crosses System versions:
Resolving to LocalHost: iMac 10.6.3, PowerBook 10.5.8
Resolving correctly to domain-squatted Leg.com: MacBook 10.5.8 & Dell/XP

[ghporter]

Very odd stuff, Love. I'm completely out of ideas here.

[Love Calm Quiet]

@ghp: Thanks for dedicating the cpu cycles to it.
It's not really a worry to me personally.
But it does seem rather unsettling that such a phenomenon can occur inexplicably on occasional systems with no readily apparent pattern/explanation.
Anybody have any street cred with apple to submit such - or suggest how I should (when there's not even a crash)?
I can't even describe it as a Safari problem, since I can get it on FF, Chrome, Camino, whatever.

[Love Calm Quiet]

However,
A ping to leg.com gives:
64 bytes from 68.178.232.143: icmp_seq=3 ttl=110 time=77.941 ms

But a ping to localhost gives:
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.063 ms

So it appears that terminal goes somewhere OTHER than localhost.

Oh, but putting 68.178.232.143 in the browser gives me a "sorry site not available" rather than localhost

::clueless here::

[Oisín]

Well, it would very likely, since 68.178.232.143 is probably just the IP address of the server that hosts leg.com, but also hosts other sites. Without a URL, it won’t know which folder (=domain) to forward you to, and the root directory of the server is not defined as any site at all, so it’s unavailable.

A whois for the IP gives:

Code:
NAVAHOST.ABOUTDOTS.COM
NS1.TUNED2ME.COM
NS2.TUNED2ME.COM

[Spheric Harlot]

Originally Posted by ghporter 

Very odd stuff, Love. I'm completely out of ideas here.

That's alright, Honey.