# CNAME & SSL

A **CNAME record (Canonical Name record)** allows you to associate your custom domain — for example, `cdn.yourdomain.com` — with the default hostname provided by Medianova, such as `yourzonename.mncdn.com`.

Using a CNAME provides consistent brand identity, simplifies DNS management, and enables secure HTTPS delivery through the [Medianova Control Panel](https://cloud.medianova.com).

### Add a CNAME

{% stepper %}
{% step %}
**Open your CDN Resource**

From the left menu, go to **CDN → CDN Resources**, and click the resource for which you want to add a CNAME.
{% endstep %}

{% step %}
**Access the CNAME & SSL tab**

Select the **CNAME & SSL** tab from the horizontal navigation menu.\
The CNAME input field appears at the top of the tab.

<figure><img src="/files/zUKJGRNd8Al6D6eyGwbo" alt="" width="563"><figcaption><p>CNAME</p></figcaption></figure>
{% endstep %}

{% step %}
**Enter the CNAME value**

Type your custom domain (for example, `cdn.yourdomain.com`) in the input field and click **Submit**.\
The CNAME is saved and applied to your selected CDN Resource.
{% endstep %}

{% step %}
**Create the DNS mapping**

In your DNS provider’s management panel, create a **CNAME** record that points your custom domain to the Medianova CDN hostname.

**Example:**

```
cdn.yourdomain.com  CNAME  yourzonename.mncdn.com
```

After DNS propagation, requests to your domain will resolve through Medianova’s CDN edge network.
{% endstep %}
{% endstepper %}

### Configure SSL & TLS

{% stepper %}
{% step %}
**Select an SSL certificate.**

In the **SSL Certificate** section, choose one of the available options from the **Select SSL Certificate** dropdown:

* **Shared SSL** – Use Medianova’s shared certificate.
* **SNI** – Use your organization’s uploaded certificate.
* **Custom SNI** – Apply a specific SSL from your list.
* **Disabled** – Turn off HTTPS for the resource.
  {% endstep %}

{% step %}
**Apply the changes.**

Click **Submit** to save the configuration.\
The selected SSL certificate will secure all CNAMEs assigned to this resource.
{% endstep %}

{% step %}
**Configure TLS versions.**

At the bottom of the tab, enable supported **TLS versions** (recommended: **TLS 1.2** and **TLS 1.3**).\
Click **Submit** to confirm.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
For detailed SSL & TLS configuration instructions, see [**SSL & TLS Encryption**](https://clients.medianova.com/products/security/ssl-tls-encryption).
{% endhint %}

### **Verification and Troubleshooting**

* DNS propagation may take several minutes depending on your DNS provider’s TTL configuration.
* CNAMEs must be unique and not used by any other services (for example, mail or web hosting).
* If you are using a **Custom SSL**, ensure the certificate covers all configured CNAMEs (via CN or SAN fields).
* TLS 1.1 is deprecated and should remain disabled for security compliance.
* To verify your configuration, run:

  ```bash
  nslookup cdn.yourdomain.com
  ```

  The response should resolve to your Medianova CDN hostname.

### Example (HTML Integration)

When your CNAME configuration is active, you can replace original URLs in your web assets with the CDN domain:

```html
<!-- Origin URL -->
<img src="http://yourdomain.com/images/logo.jpg" alt="">

<!-- CDN URL -->
<img src="http://cdn.yourdomain.com/images/logo.jpg" alt="">
```

Your CNAME domain (for example, `cdn.yourdomain.com`) now resolves to Medianova’s edge network, serving cached content from your CDN Resource.

Your CDN Resource is now accessible through your custom domain (for example, `cdn.yourdomain.com`).\
All requests to this domain are served securely via Medianova’s edge network using the configured SSL and TLS versions.


---

# Agent Instructions: 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:

```
GET https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/cname-and-ssl.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.