# 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="https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2FOTcjFTAbWzpRMpngW8pE%2Fimage.png?alt=media&#x26;token=833fa895-b26a-4178-a843-90d10912c151" 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.
