4 ms·
Current MaxCDN customer here. I'm really excited about this. I host multiple sites on Cloudfront but assets for a rails app on Maxcdn. I wanted to consolidate
by sudonim 14y ago
Current MaxCDN customer here. I'm really excited about this. I host multiple sites on Cloudfront but assets for a rails app on Maxcdn. I wanted to consolidate about a month ago. When I asked MaxCDN support why I couldn't use www, they just said no and that I should move to netdna (their other brand) to do it.
From the blog post:
"Note: MaxCDN does not automatically allow you to create a www CNAME in order to protect their system from DDoS attacks. To enable this functionality, email MaxCDN directly and mention this blog post."
I'm going to ask again and see if I can test against the experience of deploying to cloudfront. One of the things now with cloudfront is it often takes a bit of time to expire the cache.
Edit: Here's the response I received 5 mins ago from support after asking for this...
"Thanks for emailing us and I do apologize for the delayed response. I will need to escalate this to our support engineers for verification since we don't allow the use of "www" as part of custom domains for security purpose and also this needs higher level of access."
- jdorfman 14y ago@sudonim email me your account and I will enable it for you: jdorfman at maxcdn dot com
- sudonim 14y agoAwesome. Thanks for your help.
- byoung2 14y agoHow does a www cname open their system to ddos attacks?
- jdorfman 14y ago@byoung2 when we had www enabled by default, a lot of DDoS targets would sign up and point their attacks to our network effecting all of our customers. Once we disabled it, the DDoS attacks went from 1 a day to 1 every 6 months or so.