FSD CDN set up confusion

  • Let’s say I have a WordPress site (blog.my.org) with W3 Total Cache pro, on DreamHost shared hosting. I’ve successfully gone through the FSD authorize process, including creating a DNS (hosted at DreamHost) A record blogorigin.my.org for the same IP address as blog.my.org. I see a success message at the end of the FSD authorize process, indicating I need to create a DNS CNAME record blog.my.org, for (record content): c00l93d7st62.cloudfront.net (made up of course; not a real cf distribution domain). It’s not clear to me how this is supposed to work…
    I can’t delete the DNS A record for blog.my.org in the DreamHost control panel, since I have web hosting set up on that domain. If I attempt to add a CNAME record (blog.my.org), I (understandably) see the error, “You have hosting service set up for this domain. Please deactivate that here before attempting to add a root level DNS record of this type.” Even if it would allow me to add the CNAME record, I don’t think this would work properly unless I delete the A record for blog.my.org. Maybe I’m missing something obvious (or not so obvious). I would appreciate any tips/suggestions.
    Thank you!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @regexaurus

    Thank you for reaching out and I am happy to assist you with this.
    Please check our FAQ section for more details about the FSD CDN with Cloudfront.
    I hope this helps!

    Thanks!

    Thread Starter regexaurus

    (@regexaurus)

    Right, so I had already followed that down to the success message, but the trouble is with removing the A (host) record for website/domain and creating a CNAME record for that domain, that points to the Cloudfront distribution domain. When a website is created on DreamHost shared hosting, the A record is automatically created and it can’t be deleted directly (only by removing hosting for the website/domain). DreamHost prevents creation of a CNAME with the same hostname as an existing A record…and I doubt that would work well or as desired, if I could create a CNAME record with the same hostname as an existing A record. I can create an ALIAS record, but that doesn’t work as desired. Then there is the trouble of creating an alternative hostname (as described in the FAQ) and pointing it at the same IP address as the main/original A record for the website/domain. Since this is for a DreamHost shared hosting environment, where is traffic to that IP going to be routed? I don’t think DreamHost shared hosting uses a dedicated IP per website/domain…? ?????♂? If that’s correct, they’re probably using name hints to determine how to route web traffic and the alternative hostname A record simply wouldn’t work…?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘FSD CDN set up confusion’ is closed to new replies.