Domain: com.net
Stories and comments across the archive that link to com.net.
Comments · 8
-
Re:SoGoSearch didn't hijack
The "google" part is called a wildcard, and any "*.com.net" would go to SoGoSearch.
No, it's not a wildcard. See http://www.foo.com.net/ for an example. I tried a few names and only http://www.google.com.net/ and http://www.com.net/ seem to work. -
Re:SoGoSearch didn't hijack
The "google" part is called a wildcard, and any "*.com.net" would go to SoGoSearch.
No, it's not a wildcard. See http://www.foo.com.net/ for an example. I tried a few names and only http://www.google.com.net/ and http://www.com.net/ seem to work. -
Re:SoGoSearch didn't hijack
The "google" part is called a wildcard, and any "*.com.net" would go to SoGoSearch.
No, it's not a wildcard. See http://www.foo.com.net/ for an example. I tried a few names and only http://www.google.com.net/ and http://www.com.net/ seem to work. -
.tld.tld silliness
When the Google name servers didn't work, web browsers tried to add ".com" and ".net" to the URL. And http://www.google.com.net/ is Sogosearch, because the "com.net" domain exists and it is owned by Sogosearch.
Just like the "net.com" domain that is also registered by another company.
Culprits are:
- registrar who allows registration of .tld.tld domain names,
- web browsers that are trying to add suffixes even though the domain name of the URL already has a known suffix.
Of course the TLD namespace is a moving target, but that rule could at least be enforced with .com/.net/.org/.biz/.edu/.mil.
-
Re:FIGURES!
That was stupid things (browsers, users, whatever) redirecting users to www.google.com.net when www.google.com didn't work, supposedly.
-
Re:Whois Entries Not Indicative of a Hack
Also the Screenshots are just about BROWSER GUESSES. The screenshots show http://www.google.com.net!
You know, it's what happens when the browser can't find the given domain name (dns servers are down), that it tries www.google.com.com, then www.google.com.net and it happened to be already taken by the site in the screenshots. -
Just a DNS glitch
Lots of rumor of DNS getting poison and/or google site getting hacked. The reason benig is people thought google.com was going to SoGoSearch.com..
But apparently it was just their browser's not finding google.com and trying to go to Google.com.net
Stop flipping out! -
Re:Biggest story of the day
Google wasn't hacked, that's just your browser redirecting to google.com.net because
.com was down - it's the default behaviour for Safari, as far as I recall, isn't it? (notice how http://www.google.com.net/ is the page your screenshot shows?). The real issue is the major DNS poisoning going on, seemingly centered around gulli.com, seemingly a German hacking/cracking site (not directly linking, possible spyware risk);
Open a terminal and run a whois on any major search site you can think of - google.com, yahoo.com, altavista.com, etc - you'll get results like:
matt@site-4:~$ whois altavista.com
Whois Server Version 1.3
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net/
for detailed information.
Server Name: ALTAVISTA.COM.IS.N0T.AS.1337.AS.SEARCH.GULLI.COM
IP Address: 80.190.192.4
Registrar: KEY-SYSTEMS GMBH
Whois Server: whois.rrpproxy.net
Referral URL: http://www.key-systems.net/
So wake up Slashdot! No need for the coverup, it wasn't just your baby Google that got damaged, there's something serious going on that definately is 'News for Nerds' and you're posting stories about stem cells (admittedly fairly important) and some loser being picky about his motherboard.
Mod me and all these other posts Offtopic, but please, editor on duty, whoever you are, give us someplace to discuss this.