---
title: Creating a Certificate
description: "You can easily create a certificate in your **Flumotion Smart Multi CDN** account, and it will automatically be used across your CDN accounts. In addition, the certificate will be automatically renewed and updated when needed. To create a certificate in…"
url: "https://www.flumotion.com/docs/multiCDN/creating-a-certificate/"
updated: "2026-08-27"
category: Guides / Certificates
---

# Creating a Certificate

You can easily create a certificate in your **Flumotion Smart Multi CDN** account, and it will automatically be used across your CDN accounts. In addition, the certificate will be automatically renewed and updated when needed.

To create a certificate in your account:

1. [Sign in](https://manage.ioriver.io/login) to your **Flumotion Smart Multi CDN** account.
2. Select the **TLS Certificates** tab.
3. Click the **Create Certificate** button.Specify the name of the certificate. Click **Next**.
4. Specify the domains you would like to use. You can add multiple domains or, alternatively, specify a wildcard domain such as `*.example.com`. Click **Next**.
5. You should now be presented with the DNS challenge required to create your certificate. Add a CNAME record to your DNS configuration. For more information, see **DNS Challenge** below. Click **Close**.

Once the certificate is created, it will remain in **Pending** state until the DNS challenge is resolved. The certificate will automatically become **Valid** once the challenge has been successfully resolved. Until then, the certificate cannot be used within a service.

This process usually takes a couple of minutes, depending on DNS propagation time. If it takes longer, refer to the **Troubleshooting a Pending Certificate** section below.

### DNS Challenge

A DNS challenge is required to verify that you are the owner of the domain.

For example, if you are trying to create a certificate for `test.example.com`, you will be required to add a CNAME entry similar to the following:

**Name:**
`_acme-challenge.test.example.com`

**Value:**
`b7ae09e7-77fd-41f5-9f9b-3eaf26e5a66e.test.example.com.ioriver-acme.com`

### Troubleshooting a Pending Certificate

If your certificate remains in **Pending** state for an extended period, you can verify that the DNS challenge has been configured correctly by running the **nslookup** command.

For the example above:

```
nslookup _acme-challenge.test.example.com
```

You should see an output similar to the following:

```
Non-authoritative answer:

_acme-challenge.test.example.com    canonical name = b7ae09e7-77fd-41f5-9f9b-3eaf26e5a66e.test.example.com.ioriver-acme.com
```

If you don't see a similar output, double-check your DNS configuration or allow additional time for the DNS changes to propagate.