Vultr DocsLatest Content

How to Configure Custom Domain for Vultr CDN Pull Zones

Updated on April 3, 2025

Custom domain functionality in Vultr CDN Pull Zones allows you to serve your content using your own domain name, providing a branded experience and enhancing your site's credibility. By setting up a custom domain, you can ensure that your content is accessed through a personalized URL, which can improve user trust and engagement. This feature enables you to integrate your content delivery seamlessly with your existing domain infrastructure.

Note
To use a custom domain (or vanity domain) with your Vultr CDN Pull Zone, you need to create a CNAME DNS record for your domain through your domain provider. This CNAME record should point to the default CDN domain that is automatically generated when you create your Vultr CDN Pull Zone subscription. After setting up the CNAME record, make sure that the DNS changes have propagated successfully before configuring your custom domain in the Vultr CDN settings.

Follow this guide to configure a custom domain for Vultr CDN Pull Zones on your Vultr account using the Vultr Customer Portal or API.

  • Vultr Customer Portal
  • Vultr API
  1. Navigate to Products, click CDN, and then click Pull Zones.
  2. Click your target CDN Pull Zone subscription to open its management page.
  3. Click Custom Domain.
  4. Provide the Custom Domain.
  5. Upload Domain-validated Certificate(SSL/TLS) and Private Key files if the Origin URL uses HTTPS origin scheme.
  6. Click Update Custom Domain.

  1. Send a GET request to the List CDN Pull Zones endpoint and note the target Pull Zone subscription's ID.

    console 
    $ curl "https://api.vultr.com/v2/cdns/pull-zones" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"

  2. Send a PUT request to the Update CDN Pull Zone endpoint to update the custom domain.

    Note
    The API request below is for configuring a custom domain with an HTTPS origin scheme. For HTTPS, you are required to provide a Domain-validated SSL/TLS certificate and the corresponding Private Key. For HTTP, these certificates are not needed.
    console 
    $ curl "https://api.vultr.com/v2/cdns/pull-zones/{pullzone-id}" \
    -X PUT \
    -H "Authorization: Bearer ${VULTR_API_KEY}" \
    -H "Content-Type: application/json" \
    --data '{
        "vanity_domain": "{custom_vanity_domain}",
        "ssl_cert": "{BASE64_ENCODED_SSL_CERT_CONTENT}",
        "ssl_cert_key": "{BASE64_ENCODED_SSL_KEY_CONTENT}"
    }'

Comments

No comments yet.