> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/cname-and-ssl.md). # CNAME & SSL The **CNAME & SSL** tab allows you to associate custom domains with a CDN Resource, configure the SSL certificate used for HTTPS connections, define supported TLS versions, and verify that your DNS configuration correctly points to the assigned Medianova hostname. Before configuring HTTPS, ensure that your custom domain is configured with the required CNAME record and that an appropriate SSL certificate is available in your organization. {% hint style="info" %} If you need to create a new SSL certificate, use the **SSL / TLS** page before configuring this resource. For certificate creation and management, see [**Upload and Manage SSL Certificates**](/products/security/ssl-tls-encryption/upload-and-manage-ssl-certificates.md). {% endhint %} ## Add a Custom Domain (CNAME) {% stepper %} {% step %} ### Open the CDN Resource Navigate to **CDN → CDN Resources**, then open the resource you want to configure. {% endstep %} {% step %} ### Open the CNAME & SSL Tab
Select the **CNAME & SSL** tab. {% endstep %} {% step %} ### Add a Custom Domain Enter the hostname that users will use to access your content. Example: ``` cdn.example.com ``` Click **Submit** to save the configuration. {% endstep %} {% step %} ### Configure DNS Create a CNAME record with your DNS provider that points your custom domain to the hostname assigned to your CDN Resource. Example: ``` cdn.example.com CNAME your-resource.mncdn.com ``` After DNS propagation completes, requests to your custom domain are routed through the associated CDN Resource. {% endstep %} {% endstepper %} ## Configure the SSL Certificate {% stepper %} {% step %} ### Select an SSL Certificate Choose the SSL certificate that will secure HTTPS connections for this resource. Available options may include: * **Shared SSL** * **SNI** * **Custom SNI** * **Disabled** {% hint style="info" %} Certificates created from the **SSL / TLS** page become available after they have been successfully issued. {% endhint %} {% endstep %} {% step %} ### Save the Configuration Click **Submit** to apply the selected certificate. The selected certificate is used for HTTPS connections to every configured custom domain. {% endstep %} {% endstepper %} ## Configure Supported TLS Versions Select the TLS versions that clients are allowed to use. For most deployments, enable: * TLS 1.2 * TLS 1.3 Click **Submit** to save your changes. ## CNAME Verification After the required DNS mapping is configured, Medianova verifies that the configured domain correctly resolves to the assigned CDN Resource. For resource types that use custom domains, this verification is performed against the configured CNAME record. Verification status is displayed throughout the Control Panel to help identify DNS configuration issues before production traffic is served. ### Verification Status
StatusDescription
CNAME verifiedAll configured domains correctly point to the assigned CDN hostname.
Some CNAMEs incorrectSome configured domains are correctly configured, while one or more domains are missing or point to an incorrect target.
Not verifiedThe required DNS mapping is missing or incorrect for the configured domain or domains.
When multiple domains are configured, Medianova verifies each domain independently. The displayed status reflects the overall DNS verification result. ### CDN Resources List The **CDN URL / CNAME** column displays the current verification status for each resource. Hover over the verification badge to view the DNS verification result for each configured custom domain.
### Resource Overview If one or more custom domains require attention, the **Overview** page displays an **Action needed** panel describing the affected domains. The panel includes: * Host * Target * Current DNS status * Copy-to-clipboard actions * **Check now** * **Instructions** After the required DNS record has been configured and successfully verified, the notification is automatically removed.
### During Resource Creation Depending on the selected **resource type** and **SSL configuration**, the Create CDN workflow displays the DNS configuration required before the resource is activated. If displayed, the guidance includes the required host name and target hostname needed to configure the CNAME record.
## Verify the Configuration {% hint style="success" %} Use **Check now** from the **Overview** page to trigger a new DNS verification immediately, or wait for the automatic background verification. {% endhint %} ### Verify DNS Resolution Run: ```bash nslookup cdn.example.com ``` The hostname should resolve to the assigned Medianova hostname. ### Verify HTTPS Run: ```bash curl -Iv https://cdn.example.com ``` Verify that: * the HTTPS connection succeeds; * the expected SSL certificate is presented; * the negotiated TLS version matches your configuration. ## Troubleshooting ### DNS changes are not visible DNS propagation depends on your DNS provider and configured TTL values. It may take several minutes before updated records become visible globally. #### CNAME verification failed Verify that: * the required DNS mapping points to the hostname assigned to the CDN Resource; * the DNS change has propagated; * the resource is enabled; * the selected SSL configuration and resource type are correctly configured. For resource types that use custom domains, verify that the CNAME record points to the assigned CDN hostname. For Dynamic Resources, verify that the configured Website URL resolves correctly to the assigned CDN Resource. After correcting the DNS configuration, use **Check now** or wait for the next automatic verification. ### HTTPS certificate does not match the domain Verify that the selected certificate covers every configured custom domain through its Common Name (CN) or Subject Alternative Names (SANs). ### Free SSL certificate is unavailable If you recently requested a Free SSL certificate, DNS validation may still be in progress. Complete DNS validation from the **SSL / TLS** page before selecting the certificate for this resource. ## Related Concepts * [Upload and Manage SSL Certificates](/products/security/ssl-tls-encryption/upload-and-manage-ssl-certificates.md) * [Use Free SSL Certificates](/products/security/ssl-tls-encryption/use-free-ssl-certificates.md) * [SSL / TLS Encryption](/products/security/ssl-tls-encryption.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/cname-and-ssl.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.