HELP! My client got a DDOS Attack! Need advice

[goodnewscowboy]

Hello Francisco: Really sorry to hear bout this. Bummer!

I've never personally experienced a DDOS attack ,so  I called the web host I use to get his advice. He said that Dreamhost should be able to offer some kind of DDOS mitigation service.He seemed surprised that they weren't able to block it if it was coming in from only 20+ IP addresses.

He also said that if the attack continued, they'd probably not want the account after a certain point. He seemed surprised that they weren't able to block it if it was coming in from only 20+ IP addresses.

One of the main reasons I use him is that he's always been helpful when I've had problems. He said that he'd be willing to host you for a month to see if he could help. His company name is   TRK hosting

[goodnewscowboy]

Hey again Francisco, upon rereading your question, it looks like I went off half cocked when I answered it. I missed that you had solved the immediate problem and that you were wondering what course of action to takke if they don't stop. the attack

If someone continues deliberately attacking your site I'm thinking the only course of action is  to change your domain name. It's not a good solution so I hope someone else chimes in with a better one.

[Francisco_Meza]

Thanks there cowboy. Dreamhost still has not replied.  I think I'll keep everything tracked here just in case other people run into this DDOS problem in the future.  So far this is what has happened:

1. Dreamhost disabled our URL and we are still waiting for their response.
2. I took the Database and transfered all files to a new domain.
3. Launching a massive Adwords Campaign to make up for the loss of 3 days revenue.

The reason I decided to transfer the DB to a new domain was I don't want to be a sitting duck if Dreamhost says they can't help. I am pretty sure they can help, but I put into place my plan B just in case.  I'll keep everyone posted.

[Francisco_Meza]

Here is what dreamhost said:

" it does indeed look like you were getting attacked yet again. Unfortunately there isn't much you or myself can do in these cases..  I've disabled your domain again and will re-enable it in a week. I'm hoping that by then, the attacker has given up and moved on.  If this is not the case, I regret to say that you will need to find hosting elsewhere as we do not offer a DDoS protection service.   Please let me know if you have any questions.Thanks! Jason Y "

In conclusion dreamhost can't help.

[Francisco_Meza]

Update:

We dropped Dreamhost.com since they couldn't help. They were useless in this area.

We copied the DB and pointed the URL in GoDaddy to our new host at Amazon Cloud. Well, the DDoS attacks a still coming in. The site was up for a short while (I'm talking minutes) then refreshed the pages and the ISP says the site wasn't there anymore. Damn, this attacker is relentless. I will be enabling the Amazon Balance Loader tomorrow.  If this renders the DDoS attack ineffective, then Amazon solves it.  But I won't find out until tomorrow.

[Francisco_Meza]

Update:

Switched to Amazon Cloud and got Amazon involved.  They helped out by providing some tools. Basically we filtered the attacks by not accepting IPs who were transferring a certain amount of packets. Woot Woot! We have been up and running now for about 6 days with no problem. All I know is that the attacker had a browser with a Russian Language.  The site Ship Car Overseas survived!

[AFCarl]

It looks like you got this resolved.  We went through something similar many years ago but we were lucky because our website is for the US only.  The attack was coming in from China, Russia and several other European countries.

We simply blocked all countries except the US, Mexico and Canada in our Firewall.

You just need to identify the one common factor in the attack and filter that out through your firewall.

[Francisco_Meza]

These IP were spoofing from many countries.  They would disappear in minutes.  Anyway, we found the main IPs that were attacking.  YES YOU ARE RIGHT about identifying the one common factor.  At 1st we thought blocking IPs would work, but when that didn't work, we started blocking the 'sytle' they were using.

[GKLA]

Take a look at this option: http://www.cloudflare.com/features-security

[jaraca]

Thanks for sharing GKLA, Very useful information . Thanks you all!