I am against SOPA just like everyone else; however that does not mean we don't have a duty to police our own sites. In this case, someone misusing a service caused the whole service to suffer - including paying customers. This has nothing to do with SOPA but with making sure your business runs properly, and won't affect or cast a bad light on your service.
As for the disappointment at BlueHost - they should have probably let the customer know before taking action - but other than that I think they did the right thing. As a veteran of the hosting industry, if one of your customers wordpress blog was hacked and hosting a phishing site, would you not disable the site and let the customer know right away that they need to clear things up? That's just a random example, but any sane company will protect their servers via a TOS - if they didn't I would be quite concerned about the service they are offering. Just my $0.02 on this..
I'm sorry, DNS/Registration is NOT the same as an exploited website.
There is nothing intrinsically bad about DNS that it needs to be turned off; the OP has already said they were using different hosting.
BlueHost was in no way vulnerable, and in no way needed to protect itself, as the only traffic was DNS requests. GoDaddy tries to pull the same thing with disabling DNS[1].
I feel like we need a Chris Crocker video about DNS systems this month.
As for the disappointment at BlueHost - they should have probably let the customer know before taking action - but other than that I think they did the right thing. As a veteran of the hosting industry, if one of your customers wordpress blog was hacked and hosting a phishing site, would you not disable the site and let the customer know right away that they need to clear things up? That's just a random example, but any sane company will protect their servers via a TOS - if they didn't I would be quite concerned about the service they are offering. Just my $0.02 on this..