@sudonim email me your account and I will enable it for you: jdorfman at maxcdn dot com
Awesome. Thanks for your help.
How does a www cname open their system to ddos attacks?
@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.
Thanks for the clarification. So there is nothing inherent in the www cname itself, it was just that customers signing up and looking to mirror their entire site on a www cname were already being ddosed.
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."