A pull CDN keeps cached copies of your site's static files on servers close to your visitors. When a visitor requests a file, the CDN serves its cached copy or fetches it from your origin. Your ArkHost service remains the origin and stays responsible for the dynamic responses of your application.
Set up the service
- Open your CDN service in the Client Area.
- Supply the HTTPS URL of your origin when asked. This is the address the CDN fetches uncached content from.
- Add a custom hostname only if you want one, for example a
cdnsubdomain of your own domain. - Create a CNAME record at your DNS provider using the exact target shown by the service in the Client Area or its activation email. Do not guess this value.
- Wait for the DNS change to propagate.
- Request or activate SSL for the hostname in the service once DNS resolves.
- Update the asset URLs in your site or application only after the hostname loads your content correctly over HTTPS.
Using another proxy in front of the hostname
If the hostname is managed behind another proxy or DNS service, configure it according to that provider's DNS and proxy requirements. Check their documentation for how their proxy mode handles CNAME targets and certificates.
Purging the cache
Purging clears cached files so the CDN fetches fresh copies from the origin. Use it after you update content that visitors should receive immediately. Purging invalidates cached files and increases requests to your origin until the cache warms up again, so purge only what you need to.
