3. The attack uses multiple ip ranges, which make it hard to ban all of it.
If the attack isn't showing in cloudflare, it means they have your ip address. If they have your ip address, there is no way you will be able to stop the attack, even firewalls will be completely useless (what they did to BaB was DDoS using spoofed syn packets with cloudflare ip addresses, which allow it to bypass the firewalls) and once it hits a single machine, it will overload it in sheer volume.
The only defense that is going to work is obscurity. You need to change your ip address, and then completely hide it, make sure there's no way for the attacker to know what it is. Make sure that you don't have any DNS entries pointing to the real server etc.
If the attacker doesn't know your real ip address, then they'll be forced to go a) Go through CF b) by a layer 7 attack. (Also, ignore the idiots who tell you about "CloudFlare resolvers" and what not, if you configure the service right no one can find your ip address. I for a long time had a 1 BTC open bounty on anyone who could name a bustabit ip address, and it was never claimed)
The attack is showing on cloudflare. And the attacker does not have our server's ip, ive set the server to 'only' accept request from cloudflare ips found at http://cloudflare.com/ips-v4 and https://www.cloudflare.com/ips-v6
I've been in contact with cloudflare guys, and they have acknowledge that the attack is targeted on www and blog servers. So having that said, im assuming, that the attack does go tru them.
Also as far as i can understand from the logs, the attack is specifically either a HTTP GET or HTTP POST requests that is targeted at https://www.moneypot.com and https://blog.moneypot.com and not their real ip addresses. Last week MP IP address was revealed due to a * A record present on our DNS records, and this has been removed and our IP are now changed.
If there's any other recommendation you can think of, do let me know.
Thanks
uni