> 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 Configure custom domains, SSL certificates, and supported TLS versions for a CDN Resource. The **CNAME & SSL** section controls the custom domains associated with the CDN Resource, the SSL certificate used for HTTPS connections, and the TLS protocol versions supported by the resource. You can configure these settings per CDN Resource in the [Medianova Control Panel](https://cloud.medianova.com). ## Configure CNAME Use **CNAME** to associate a custom domain with the CDN Resource. {% stepper %} {% step %} ### Open CNAME & SSL Open your CDN Resource and select **CNAME & SSL**. {% endstep %} {% step %} ### Add a CNAME Under **CNAME**, enter the custom domain you want to use with the CDN Resource. For example: `cdn.example.com` Select **+** to add the domain. {% endstep %} {% step %} ### Save the Configuration Select **Save** in the pending changes bar. Review the pending changes and confirm the update. {% endstep %} {% endstepper %} ## Configure DNS After adding the custom domain, configure the corresponding CNAME record with your DNS provider. The record must point your custom domain to the hostname assigned to the CDN Resource. For example: `cdn.example.com → your-resource.mncdn.com` {% hint style="info" %} Use the DNS target assigned to your CDN Resource when creating the record. The hostname above is an example only. {% endhint %} After the DNS record propagates, Medianova can verify whether the custom domain points to the expected CDN configuration. ## Configure SSL Certificate Use **SSL Certificate** to select the SSL option used for HTTPS connections to the CDN Resource. {% stepper %} {% step %} ### Select an SSL Certificate Under **SSL Certificate**, open **Select SSL Certificate** and select the appropriate SSL option or certificate. {% endstep %} {% step %} ### Save the Configuration Select **Save** in the pending changes bar. Review the pending changes and confirm the update. {% endstep %} {% endstepper %} {% hint style="info" %} If you need to create, upload, or manage an SSL certificate, use the **SSL / TLS** section of the Control Panel. For configuration guidance, see Upload and Manage SSL Certificates. {% endhint %} ## Configure TLS Versions Use **TLS Versions** to select the TLS protocol versions supported for HTTPS connections to the CDN Resource. The available versions are: * **TLS 1.1** * **TLS 1.2** * **TLS 1.3** {% stepper %} {% step %} ### Select TLS Versions Under **TLS Versions**, select the protocol versions that the CDN Resource should support. Multiple TLS versions can be enabled. {% endstep %} {% step %} ### Save the Configuration Select **Save** in the pending changes bar. Review the pending changes and confirm the update. {% endstep %} {% endstepper %} {% hint style="warning" %} Changing the supported TLS versions can affect client compatibility. Ensure that the required client environments support at least one of the enabled versions. {% endhint %} ## CNAME Verification Medianova verifies whether configured custom domains resolve to the expected CDN configuration. When multiple custom domains are configured, each domain can be checked independently to identify DNS configuration issues. ### CDN Resources List The **CDN URL / CNAME** column in the CDN Resources list displays the current verification status. The verification information can indicate whether the configured domains point to the expected CDN hostname. ### Resource Overview If a custom domain requires attention, the resource **Overview** page can display an **Action needed** notification with the DNS configuration that requires correction. Depending on the configuration, the notification can include: * **Host** * **Target** * Current DNS status * Copy actions * **Check now** * **Instructions** After correcting the DNS record, use **Check now** when available to trigger another verification. ## Verify the Configuration After configuring the CNAME, SSL certificate, and TLS versions, verify DNS resolution and HTTPS connectivity. ### Verify DNS Resolution Run: ```bash nslookup cdn.example.com ``` This command queries DNS for the custom domain. Verify that the domain resolves through the expected CDN mapping. ### Verify HTTPS Run: ```bash curl -Iv "https://cdn.example.com" ``` This command establishes an HTTPS connection and displays connection and response details without downloading the response body. Verify that: * The HTTPS connection succeeds. * The expected SSL certificate is presented. * The negotiated TLS version is enabled for the CDN Resource. ## Troubleshooting ### CNAME Verification Fails Verify that: * The custom domain points to the DNS target assigned to the CDN Resource. * The configured hostname is correct. * The DNS change has propagated. After correcting the DNS configuration, use **Check now** when available or wait for the next verification. ### HTTPS Certificate Does Not Match the Domain Verify that the SSL certificate assigned to the CDN Resource covers the configured custom domain. If another certificate is required, manage the certificate from the **SSL / TLS** section and then select it under **SSL Certificate** for the CDN Resource. ### SSL Certificate Is Not Available If a certificate you expect to use is not available under **Select SSL Certificate**, check its current status in the **SSL / TLS** section. For newly requested certificates, complete any required validation before assigning the certificate to the CDN Resource. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` 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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.