Slashdot Mirror
Google DNS Glitch Caused Outage
An anonymous reader writes "Google suffered a pretty long outage saturday evening, due to some DNS glitches, according to company spokesperson. All Google services were down for a while, including Gmail and Google AdSense. There seems to be a DNS hijack, as some screen grabs show that Google.com was redirecting to another site, SoGoSearch.com. "
Are people really this dependant on google that when there is an outage, people really flip out?
I mean, there are other search engines.
Other email services.
Other mapping things.
Seriously, what were people doing a couple years ago? If your life is that in tuned to google, maybe its time to 'log off' (and pardon the cliche).
...or perhaps we reject Microsoft because we disagree with its corporate goals, and find its products to be substandard, while agreeing with Google's, and find its offering to be exactly what we want?
We who were living are now dying
With a little patience
In fact, I think they registered com.net, and simply created a wildcard DNS result for anything under that, which points to their search page.
.net to google.com, and ended up at *.com.net.
.net was appended, but left the original URL in the location bar.
As the parent says, it is common behaviour for browsers to try appending common TLD's to the end of an URL that is not found verbatim. When Google went away, the browser appended
A bug that people seem to be ignoring is that whatever browser is shown in the screenshot did not show the correct URL after the
What does SPF have anything to do with this?
If your domain is high-jacked due to a fault with the security of your domain registrar, then yes, you have bigger problems than any anti-spam solution.
This is not the purpose of SPF
If you read spf.pobox.com You can learn that SPF is merely designed to be a system which can eliminate domains being spoofed in the from field of spam messages.
If someone is using one of my domains (logicx.net) to send spam; I can reduce the affect of such a joe-job attack by having a published SPF record; such that receiving systems can verify if the email came from a logicx.net mail server, and reject it appropriately.
SPF and PGP have entirely different authentication approaches. I'd go so far as to say that PGP is more integrity checking.
SPF is a verification that mail for a particular domain came from an appropriate server -- with the goal of disposing false emails (spam, spoofs, etc.)
This is not at all a system to verify users on that particular email system.
This is where PGP steps in -- It is used to verify the integrity of the email -- that it came from a particular user, and came unaltered.
Finally, where has it been verified that their was a breach of their DNS system?
All of the screenshots have now been confirmed to be a firefox situation where when DNS failed it resolved www.google.com.net -- which resolved to the people who own com.net
May this post be indexed by spiders, and archived for all to see as my Internet epitaph.