If you're in the rare situation of using GoDaddy DNS but don't use them as a registrar, then you're in luck. Simply sign up with a new DNS provider. They will give you their DNS servers which you need to set as the DNS servers that are authoritative for your domain. Then sign into your registrar and change the authoritative DNS servers for your domain. There will be a propagation delay but once it's done you're all set.
If you are in the extremely common situation of having registered your domain through GoDaddy and also use their DNS service, then you have a problem because to move to another DNS provider you need to sign into GoDaddy.com to make the change I've described above i.e. change which DNS provider is authoritative for your domain. You can't do this until GoDaddy.com is back online. So what I suggest is that you sign up for a new DNS provider and then keep checking GoDaddy.com. As soon as it comes back online, sign in and make the change to your new provider as quick as you can.
Other data:
Whois requests for godaddy domains are currently failing because whois.godaddy.com is offline due to name resolution failure.
Godaddy's twitter feed is a good source of updates, although they are claiming to be making progress and all my godaddy DNS hosted domains are still offline, so it seems to be more marketing speak than real data: https://twitter.com/godaddy
As mentioned, Anonymous seems to be behind it as three tweets on their twitter account seem to indicate: https://twitter.com/AnonOpsLegion
I don't think the scale of this attack is fully understood yet. According to the CBC, GoDaddy hosts over 5 million websites (not sure if that's DNS, registrar, etc) so expect this to be big news and potentially the next political football.
"If you're in the rare situation of using GoDaddy DNS but don't use them as a registrar, then you're in luck. Simply sign up with a new DNS provider."
Assumes of course that people have their zone file to refer to. Which they should. Even if you don't know what a zone file is it's probably a good idea to at the very least make a screen grab of the information where the info is shown at your registrar. Or just use dig from the command line (see my comment further down for syntax).
General question here about upstream outages that can take down your site, e.g. DNS outage, AWS zone outage, etc.
What to tell your customers when an upstream service provider experiences an outage? I mean, if you're running ifttt.com your users might be savvy enough to understand that a DNS outage isn't your fault; but pinterest.com or whatever (painting with broad strokes here, forgive me) might not have a user base that would understand that events out of your control have made your site inaccessible.
How do you reassure your customers? What's the proper tone to take?
Good question. I believe in explaining as clearly as possible, but ultimately in taking responsibility. You chose the provider, decided on the level of risk you're comfortable with, and that ultimately failed. It was that choice that got in the way of your users.
If you can point to ways you'll improve the service in the future as a result of the outage, all the better.
When we had a large DoS attack at Posterous, I wrote two posts, one as soon as possible (http://blog.posterous.com/todays-outage-and-changes-for-cust...), and the next as a bit of a post-mortem (http://blog.posterous.com/moving-forward). Both explained that there were many factors beyond our control, but that the responsibility was ultimately ours, and we were working to learn from the event and improve our services as a result.
They weren't perfect posts, but I think they went a long way toward being open and honest with our users in the midst of a major negative event.
At the risk of professing an attitude that I generally dislike: there's no proper tone to take other than full responsibility. Like Steve Jobs said, when you're the janitor, reasons matter.
Once you're a service provider -- whether your services in turn rely on other services or not -- reasons stop mattering. As a practical matter, you and I know that there's no way you can build a fully scalable, fully redundant infrastructure from the ground-up in your first week. Hell, if you ever build that kind of infrastructure at all, you'll be way ahead of most companies.
But, that's the kind of infrastructure you should be working towards building, all the time. You should have a clear roadmap for ensuring data integrity, then dealing with security, then dealing with redundancy, and finally high availability.
If your service falls over for any reason, ultimately it's because you haven't done something on your roadmap yet. There's no way to explain that to your customers that doesn't sound like you're trying to pass the fault on to someone else -- because that's exactly what you're doing.
So just 'fess up to your customers: "one of the services that our business relies on had some serious technical problems that affected us today, but we recognize that ultimately it's our responsibility to make sure that our service is always available to you. We're constantly working on our infrastructure to make it more reliable, but we clearly still have more work to do. We will be changing some of our priorities so that this won't be a problem in the future. Thank you for sticking with us." (And then do it, otherwise this will backfire on you the next time you have an outage of similar cause.)
As an aside: I generally take a softer stance towards user responsibilities -- of course everyone should have backups, but Joe Schmoe just doesn't have time for that -- but a much harder stance towards businesses. Once you accept money from someone, you put yourself into a position of absolute responsibility for whatever it is that people rely on you for. If you can't guarantee the availability of your service or the safety of their data, then you shouldn't be taking their money.
I don't think there's a tone you can take that will make non-technical users understand that it's "not your fault". To the non-technical user your site is just down and, potentially, a service they're paying for is unavailable.
I'd argue that such an outage _is_ your fault. If you're worried about Customer perceptions as a result of outages of third-party services your site relies on then, I'd argue, you need to have redundancy in your choice of third-party services. If it's important enough to worry about it should be important enough to spend some money on and do something about. If that drives up your costs then your product's cost, to your Customers, needs to reflect that.
It looks like the root of the problem is that their DNS servers are unresponsive or offline. Web sites and mail whose DNS is hosted on GoDaddy appear to look "down" because they cannot resolve.
Good push for anyone to switch to DNSMadeEasy or Amazon Route53 if you're currently caught in this.
I'm one of those people you call "stupid", who "deserves what I get". This is my first time posting here. I've used GD for years. Sure, they try to upsell me, but being in sales, I don't have a problem with giving them a firm "no thanks". If you do, that's your problem, not theirs. They're a business, for goodness sake. Realize that.
And not only my sites are now down, but all the sites I maintain for clients. If some individual (or group) has done this intentionally, then these people are responsible for taking hundreds, maybe thousands of small businesses off line today. They're cutting into their sales, hurting their bottom lines, and if it continues for too long, will probably lead to people being laid off.
So you can sit on your techie high horses and think you're oh so smart, but the fact is, these are real business people doing real business and criminals are hurting them. So you come down on the honest people for signing contracts and paying their bills on time?
Agreed. I've been out of work more than 6 months. Right as my family was packing to move to the closest bridge, I got a call from a company to setup their servers and finish their web app. With so much on my plate and no time to do it, I picked the easy and fast route. Use GoDaddy for cheap fast DNS and deal with it later. I brought our servers online this morning. Database and all. I was getting congrats and thank yours from the whole office. Now I might lose the job I just got. Thanks guys. Perhaps you can tell my kids.
I'd imagine from their POV, when you continue doing business with a company they find morally reprehensible, you're no longer "honest people". If their end goal is killing GoDaddy, these collateral losses might be worth it. Also, it might have a positive side-effect of people associating more risk with dealing with shady companies.
Does anybody have a guide on how to migrate away from GoDaddy without downtime? And what would you recommend instead? We currently host a bunch of domains and use their DNS servers.
If you are only using them for DNS (and assuming their DNS works again) you can simply setup the new dns somewhere but not switch the DNS at your registrar. Until the dns is working at the new dns provider (and you would query it to find that out).
Example:
1) setup amixdomain.com at, say, zoneedit.com (not recommending them just using as an example).
2) Wait a bit, say several hours then use a dns utility like the one at kloth.net to query the two zoneedit.com dns servers directly. If both of them answer for your domain you are in good shape. I don't know what the lag is until zoneedit reloads their dns. It could be in a minute or it could take longer (which is why you can just wait).
Or you can use the OSX (or equivalent on other platforms) dig tool from the command line as follows, using ycombinator.com as an example:
Edit: What I meant to say was "if you have a mac open a terminal session and use dig" sorry for seeming to implying that dig is an OSX tool.
dig @NS1.EASYDNS.COM ycombinator.com 'A'
yc's servers are, so I picked one. You want to query all the dns servers:
Name Server: NS1.EASYDNS.COM
Name Server: NS2.EASYDNS.COM
Name Server: NS3.EASYDNS.ORG
Name Server: NS6.EASYDNS.NET
Name Server: REMOTE1.EASYDNS.COM
Name Server: REMOTE2.EASYDNS.COM
3) After the dns is active at zoneedit.com change the dns to the nameservers zoneedit.com gives you (change at your current registrar). You should have no downtime (since the old and new nameservers are answering with the same results.
Well, you're already in the midst of downtime, so you have a head start.
Aside from that, focus on two concepts: TTL and overlap.
1) On your old host, lower the TTL of all your records to something quite low, like 30 seconds. This will increase the burden on your nameservers, since records will only be cached that long, but it will make you more nimble as you make substantial changes.
2) Migrate your records over to the new provider. This can be a bit tedious for more complex zones, but rather straight-forward for many. Change your nameserver on your local machine to point to your new DNS host, just to test in a "real-world" scenario.
Then go to your registrar and flip the switch.
Switching DNS providers is much less prone to downtime than changing web hosts, since the records themselves aren't changing much -- just where to find them.
If you're switching registrars, the principal is similar, setting the TTL quite low during the transition to help you make changes more quickly should something go wrong.
Moving DNS servers can usually be done with no downtime. All you need to do is copy your current dns records to a new provider and then change the name servers. Keep your old DNS configuration up at least for a few days.
Gradually clients will switch over to the new DNS servers, but as long as both servers resolve to the same IP you should be fine.
DNS services cost money, either in staffing or recurring charges, so it really depends on your budget. Neustar is a nice DNS provider ($50+/mo).
Generally you'll want to set up your new DNS, turn down the refresh on your existing DNS domains, wait $old_refresh or so, then change your primary/secondaries listed at your registrar to point at your new DNS.
I do use a domain registrar for domain registering, and a DNS hoster for DNS hosting. From my - limited - experience it's not a good idea to have this with one service provider (registrars have not 100% uptime, DNS hosters are limited with domains or expensive)
We've been migrating people to internet.bs
Once you pay for the transfer, you can set up all the DNS records, so when everything transfers over it is already configured.
> implying this isn't just a random fake account
> implying there is a spokesperson for Anonymous
> implying there is a trace of credibility to this claim
This thread demonstrates that HN needs a comment collapse button a la reddit. The first comment thread, mostly useless, is taking most of the page, and no way to collapse it.
I'm assuming they're adding the Verisign DDoS protection service, but this change should make EVERY single Godaddy client very, very, very nervous (from the current whois):
Status Alert: Hey, all. We're aware of the trouble people are having with our site. We're working on it.
That understates things by several orders of magnitude. It's not just their site that is down, it's their domain name servers, so most websites that bought their domain from GoDaddy are unreachable (unless you are working off of cached domain data).
I don't use GoDaddy, nor do I particularly like them, so this doesn't really affect me or my business directly.
But I got a call earlier today from my less tech-savvy buddy who was freaking out because his GoDaddy website was down. Yea it is probably "his fault" for choosing them, and he probably "deserves it".
Still, not everyone is born a leet computer hacker, and sometimes this is the only way people will learn, so I'm trying not to be too hard on people for that.
I just got an email from GoDaddy beginning: 'Todays Lesson -...'. I thought this might go into their service being down, backups or failover protection.
But no, it carried on to: 'Today's Lesson - SAVINGS! 20% OFF*'
Literally just transferred all of my domain names and DNS hosting away from GoDaddy last night. Should have done it after the SOPA fiasco - glad I didn't wait until today!
GoDaddy has been providing me with excellent customer support for a decade. I'm not sure what the hate is all about.
Sure, they didn't take my side in the SOPA debate, but I'd rather live in a world where everyone is entitled to their opinion.
I'm also not comfortable with a group calling themselves "Hackers" giving my profession a foul name by activities like this. This is like bombing a nation which doesn't have same views as yours. Hackers, they are not. Shameful.
My experience with GoDaddy has been nothing but negative.
The latest being a SSL certificate I purchased 9 months ago. They auto renewed the certificate at full price 90 days in advance, without any warning whatsoever. Partially my fault for not opting out (but I was unaware that I ever opted in). Most services that auto-renew give you a warning prior to the imminent date.
When I asked for a refund, I was told I could only get in store credit. In store credit for a virtual good that hasn't been activated/used and arguably charged without my consent? Joke of a company.
[+] [-] mmaunder|13 years ago|reply
If you're in the rare situation of using GoDaddy DNS but don't use them as a registrar, then you're in luck. Simply sign up with a new DNS provider. They will give you their DNS servers which you need to set as the DNS servers that are authoritative for your domain. Then sign into your registrar and change the authoritative DNS servers for your domain. There will be a propagation delay but once it's done you're all set.
If you are in the extremely common situation of having registered your domain through GoDaddy and also use their DNS service, then you have a problem because to move to another DNS provider you need to sign into GoDaddy.com to make the change I've described above i.e. change which DNS provider is authoritative for your domain. You can't do this until GoDaddy.com is back online. So what I suggest is that you sign up for a new DNS provider and then keep checking GoDaddy.com. As soon as it comes back online, sign in and make the change to your new provider as quick as you can.
Other data:
Whois requests for godaddy domains are currently failing because whois.godaddy.com is offline due to name resolution failure.
Godaddy's twitter feed is a good source of updates, although they are claiming to be making progress and all my godaddy DNS hosted domains are still offline, so it seems to be more marketing speak than real data: https://twitter.com/godaddy
As mentioned, Anonymous seems to be behind it as three tweets on their twitter account seem to indicate: https://twitter.com/AnonOpsLegion
I don't think the scale of this attack is fully understood yet. According to the CBC, GoDaddy hosts over 5 million websites (not sure if that's DNS, registrar, etc) so expect this to be big news and potentially the next political football.
Edit: And finally, http://www.downforeveryoneorjustme.com/ is down for everyone because it's over quota. Via Reddit which is also covering this: http://www.reddit.com/r/technology/comments/znvwk/godaddycom...
[+] [-] baseh|13 years ago|reply
We need a new site: http://www.is-downforeveryoneorjustme-downforeveryoneorjustm...
Sorry for the useless comment
[+] [-] larrys|13 years ago|reply
Assumes of course that people have their zone file to refer to. Which they should. Even if you don't know what a zone file is it's probably a good idea to at the very least make a screen grab of the information where the info is shown at your registrar. Or just use dig from the command line (see my comment further down for syntax).
[+] [-] etagwerker|13 years ago|reply
You actually can. You will have to modify your /etc/hosts file, go to your GoDaddy account and change to a new DNS service (name servers)
I followed the instructions in this post and I solved the GoDaddy hell for my sites:
http://davewasmer.tumblr.com/post/31283249223/migrating-from...
[+] [-] RandallBrown|13 years ago|reply
[+] [-] robomartin|13 years ago|reply
[+] [-] mattdeboard|13 years ago|reply
What to tell your customers when an upstream service provider experiences an outage? I mean, if you're running ifttt.com your users might be savvy enough to understand that a DNS outage isn't your fault; but pinterest.com or whatever (painting with broad strokes here, forgive me) might not have a user base that would understand that events out of your control have made your site inaccessible.
How do you reassure your customers? What's the proper tone to take?
[+] [-] whafro|13 years ago|reply
If you can point to ways you'll improve the service in the future as a result of the outage, all the better.
When we had a large DoS attack at Posterous, I wrote two posts, one as soon as possible (http://blog.posterous.com/todays-outage-and-changes-for-cust...), and the next as a bit of a post-mortem (http://blog.posterous.com/moving-forward). Both explained that there were many factors beyond our control, but that the responsibility was ultimately ours, and we were working to learn from the event and improve our services as a result.
They weren't perfect posts, but I think they went a long way toward being open and honest with our users in the midst of a major negative event.
[+] [-] thaumaturgy|13 years ago|reply
Once you're a service provider -- whether your services in turn rely on other services or not -- reasons stop mattering. As a practical matter, you and I know that there's no way you can build a fully scalable, fully redundant infrastructure from the ground-up in your first week. Hell, if you ever build that kind of infrastructure at all, you'll be way ahead of most companies.
But, that's the kind of infrastructure you should be working towards building, all the time. You should have a clear roadmap for ensuring data integrity, then dealing with security, then dealing with redundancy, and finally high availability.
If your service falls over for any reason, ultimately it's because you haven't done something on your roadmap yet. There's no way to explain that to your customers that doesn't sound like you're trying to pass the fault on to someone else -- because that's exactly what you're doing.
So just 'fess up to your customers: "one of the services that our business relies on had some serious technical problems that affected us today, but we recognize that ultimately it's our responsibility to make sure that our service is always available to you. We're constantly working on our infrastructure to make it more reliable, but we clearly still have more work to do. We will be changing some of our priorities so that this won't be a problem in the future. Thank you for sticking with us." (And then do it, otherwise this will backfire on you the next time you have an outage of similar cause.)
As an aside: I generally take a softer stance towards user responsibilities -- of course everyone should have backups, but Joe Schmoe just doesn't have time for that -- but a much harder stance towards businesses. Once you accept money from someone, you put yourself into a position of absolute responsibility for whatever it is that people rely on you for. If you can't guarantee the availability of your service or the safety of their data, then you shouldn't be taking their money.
[+] [-] EvanAnderson|13 years ago|reply
I'd argue that such an outage _is_ your fault. If you're worried about Customer perceptions as a result of outages of third-party services your site relies on then, I'd argue, you need to have redundancy in your choice of third-party services. If it's important enough to worry about it should be important enough to spend some money on and do something about. If that drives up your costs then your product's cost, to your Customers, needs to reflect that.
[+] [-] KrisJordan|13 years ago|reply
Good push for anyone to switch to DNSMadeEasy or Amazon Route53 if you're currently caught in this.
Update: It appears Anonymous is behind this https://twitter.com/AnonOpsLegion/status/245218636187443200
[+] [-] 16s|13 years ago|reply
[+] [-] executive|13 years ago|reply
[+] [-] ApsoFacto|13 years ago|reply
And not only my sites are now down, but all the sites I maintain for clients. If some individual (or group) has done this intentionally, then these people are responsible for taking hundreds, maybe thousands of small businesses off line today. They're cutting into their sales, hurting their bottom lines, and if it continues for too long, will probably lead to people being laid off.
So you can sit on your techie high horses and think you're oh so smart, but the fact is, these are real business people doing real business and criminals are hurting them. So you come down on the honest people for signing contracts and paying their bills on time?
Seriously?
[+] [-] brokndodge|13 years ago|reply
[+] [-] Peaker|13 years ago|reply
[+] [-] amix|13 years ago|reply
[+] [-] larrys|13 years ago|reply
Example:
1) setup amixdomain.com at, say, zoneedit.com (not recommending them just using as an example).
2) Wait a bit, say several hours then use a dns utility like the one at kloth.net to query the two zoneedit.com dns servers directly. If both of them answer for your domain you are in good shape. I don't know what the lag is until zoneedit reloads their dns. It could be in a minute or it could take longer (which is why you can just wait).
Or you can use the OSX (or equivalent on other platforms) dig tool from the command line as follows, using ycombinator.com as an example:
Edit: What I meant to say was "if you have a mac open a terminal session and use dig" sorry for seeming to implying that dig is an OSX tool.
dig @NS1.EASYDNS.COM ycombinator.com 'A'
yc's servers are, so I picked one. You want to query all the dns servers:
3) After the dns is active at zoneedit.com change the dns to the nameservers zoneedit.com gives you (change at your current registrar). You should have no downtime (since the old and new nameservers are answering with the same results.[+] [-] whafro|13 years ago|reply
Aside from that, focus on two concepts: TTL and overlap.
1) On your old host, lower the TTL of all your records to something quite low, like 30 seconds. This will increase the burden on your nameservers, since records will only be cached that long, but it will make you more nimble as you make substantial changes.
2) Migrate your records over to the new provider. This can be a bit tedious for more complex zones, but rather straight-forward for many. Change your nameserver on your local machine to point to your new DNS host, just to test in a "real-world" scenario.
Then go to your registrar and flip the switch.
Switching DNS providers is much less prone to downtime than changing web hosts, since the records themselves aren't changing much -- just where to find them.
If you're switching registrars, the principal is similar, setting the TTL quite low during the transition to help you make changes more quickly should something go wrong.
[+] [-] vasco|13 years ago|reply
[1] (Affiliate) http://www.namecheap.com?aff=37912
[2] (Non-Affiliate) http://www.namecheap.com
[3] http://www.namecheap.com/support/knowledgebase/article.aspx/...
[+] [-] datasage|13 years ago|reply
Gradually clients will switch over to the new DNS servers, but as long as both servers resolve to the same IP you should be fine.
[+] [-] remi|13 years ago|reply
[+] [-] stickfigure|13 years ago|reply
[+] [-] rhizome|13 years ago|reply
Generally you'll want to set up your new DNS, turn down the refresh on your existing DNS domains, wait $old_refresh or so, then change your primary/secondaries listed at your registrar to point at your new DNS.
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] Uchikoma|13 years ago|reply
For DNS hosting I'm currently happy with
http://www.dnsmadeeasy.com/
[+] [-] fang0654|13 years ago|reply
[+] [-] dshankar|13 years ago|reply
[+] [-] larrys|13 years ago|reply
Godaddy's dns:
Name Server: CNS1.SECURESERVER.NET
A typical customer of godaddy's dns servers:Name Server: NS07.DOMAINCONTROL.COM
[+] [-] debacle|13 years ago|reply
[+] [-] mikegirouard|13 years ago|reply
I'm reminded of the Romney records[1] and more recently the Apple device IDs[2] stories.
[1]: http://news.ycombinator.com/item?id=4480301 [2]: http://news.ycombinator.org/item?id=4500479
[+] [-] codesuela|13 years ago|reply
[+] [-] azarias|13 years ago|reply
[+] [-] nord|13 years ago|reply
[+] [-] druiid|13 years ago|reply
[+] [-] semenko|13 years ago|reply
The GoDaddy status page proudly announces "No issues to report": http://support.godaddy.com/system-alerts/
During last week's GoDaddy mail outage, they had no status info posted, even hours after reports on NANOG/Outages: http://comments.gmane.org/gmane.org.operators.isotf.outages/...
[+] [-] autotravis|13 years ago|reply
[+] [-] fhars|13 years ago|reply
[+] [-] Bill_Dimm|13 years ago|reply
Status Alert: Hey, all. We're aware of the trouble people are having with our site. We're working on it.
That understates things by several orders of magnitude. It's not just their site that is down, it's their domain name servers, so most websites that bought their domain from GoDaddy are unreachable (unless you are working off of cached domain data).
[+] [-] bwhalley|13 years ago|reply
Most people who buy from GoDaddy probably host their DNS there as well though.
[+] [-] mckilljoy|13 years ago|reply
But I got a call earlier today from my less tech-savvy buddy who was freaking out because his GoDaddy website was down. Yea it is probably "his fault" for choosing them, and he probably "deserves it".
Still, not everyone is born a leet computer hacker, and sometimes this is the only way people will learn, so I'm trying not to be too hard on people for that.
[+] [-] ajennings|13 years ago|reply
3. Change DNS providers.
[+] [-] dollar|13 years ago|reply
GODADDY.COM.VATAXIDERMIST.COM GODADDY.COM.THEYOUNGCONS.COM GODADDY.COM.THEVILLAGEAT63RDSTREET.COM GODADDY.COM.THEFOREXTHIEF.COM GODADDY.COM.THECOTTONWIFE.COM GODADDY.COM.TEST.CHUMCHUM.NET GODADDY.COM.STAGEDOORPRODUCTIONS.COM GODADDY.COM.SKATEONGRANDROLLERRINK.COM GODADDY.COM.SHOPCOULSDON.COM GODADDY.COM.SHIRLEEMCGARRY.COM GODADDY.COM.SETHPAPA.COM GODADDY.COM.SANGRAALBODYWORK.COM GODADDY.COM.RESPECTED.BY.WWW.DNDIALOG.COM GODADDY.COM.REMEDIASERVICES.COM GODADDY.COM.QUINTAFLORIDA.COM GODADDY.COM.QHSSE.COM GODADDY.COM.PISSEDOFFPEOPLEOFAMERICA.COM GODADDY.COM.MYANHOMEINSPECTION.COM GODADDY.COM.MUTTLANDMEADOWS.COM GODADDY.COM.MICHALPOE.COM GODADDY.COM.MERCHANTSSTORES.COM GODADDY.COM.LOVE8PLANET.COM GODADDY.COM.LEVIATHANCOMPUTERS.NET GODADDY.COM.LANDLCONNECTION.COM GODADDY.COM.KARLAADAMS.COM GODADDY.COM.JESSICABOAL.COM GODADDY.COM.IXCANADESIGNS.COM GODADDY.COM.INDYMETROWOMAN.COM GODADDY.COM.GGONYA.NET GODADDY.COM.GDDAS.COM GODADDY.COM.FLORIDASURETY.COM GODADDY.COM.FLETCHERANDFLETCHERPHOTOGRAPHY.COM GODADDY.COM.EZGRAPHICSLOGOS.COM GODADDY.COM.ERICAMDESIGNS.COM GODADDY.COM.EAGLEEYEHOMEMONITORING.COM GODADDY.COM.CLIFFYCELLS.COM GODADDY.COM.CAKEMUFFIN.COM GODADDY.COM.BERNADETTEHAROLD.COM GODADDY.COM.BANGALORESRESTAURANTS.COM GODADDY.COM.AUTHORMARIONBROWN.COM GODADDY.COM.AND.ALEX.FUCKED.BY.WWW.DNDIALOG.COM GODADDY.COM.ANALOGANIMALRECORDS.COM GODADDY.COM.ALEXANDREAREINA.COM GODADDY.COM.AIPOS.NET GODADDY.COM.1BEAUTYPRO.COM GODADDY.COM
[+] [-] CD1212|13 years ago|reply
But no, it carried on to: 'Today's Lesson - SAVINGS! 20% OFF*'
[+] [-] maerek|13 years ago|reply
[+] [-] crisnoble|13 years ago|reply
[+] [-] arihant|13 years ago|reply
Sure, they didn't take my side in the SOPA debate, but I'd rather live in a world where everyone is entitled to their opinion.
I'm also not comfortable with a group calling themselves "Hackers" giving my profession a foul name by activities like this. This is like bombing a nation which doesn't have same views as yours. Hackers, they are not. Shameful.
[+] [-] CaveTech|13 years ago|reply
When I asked for a refund, I was told I could only get in store credit. In store credit for a virtual good that hasn't been activated/used and arguably charged without my consent? Joke of a company.
[+] [-] chucknelson|13 years ago|reply
http://5by5.tv/partners/hover
[+] [-] orienwu|13 years ago|reply
http://www.webhostingtalk.com/showthread.php?t=1190617