# How to create the CNAME records for free SSL

**URL:** <https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321>\
**Category:** HTTPS and SSL\
**Created:** [October 13, 2020, 10:00pm UTC](https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321 "2020-10-13T22:00:00Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Admin](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/admin/32/36437_2.png) [@Admin](https://forum.infinityfree.com/u/Admin)\
**Post date:** [October 13, 2020, 10:00pm UTC](https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321/1 "2020-10-13T22:00:00Z")

</div>

To get a free SSL certificate from InfinityFree, you need to setup some DNS CNAME records on your domain name. This article describes how to do that. Like videos better? Check out the bottom of this article.

## Where do I set up the CNAME records?

The CNAME records should be set up with the DNS hosting provider of your domain name.

Most people will be using the InfinityFree nameservers `ns1.infinityfree.com` and `ns2.infinityfree.com`, or the `byet.org` nameservers. This means you can add the records to the control panel of the hosting account hosting this domain name. The records can be added to the “CNAME Records” section.

If your domain name is using different nameservers, you’ll need to add the CNAME records to the nameservers of that provider. So, if your domain name is using Cloudflare nameservers, you need to setup the CNAME records at Cloudflare.

## Which records do I need to add?

You can find the DNS CNAME records to add in the client area.

1. Login to the [client area](https://dash.infinityfree.com).
2. Go to the “Free SSL Certificates” section.
3. Create a new SSL certificate order, or click Manage next to the one you have already created.
4. On the SSL certificate page you’ll see one or two CNAME records: one for **\_acme-challenge**.example.com and sometimes one for **\_acme-challenge.www**.example.com, each with their own Destination. These are the records you need to add.

You should keep this browser tab open, because you’ll need these records later.

## Where can I configure my CNAME records?

The CNAME records should be set up with the DNS hosting provider of your domain name.

Most people will be using the InfinityFree nameservers `ns1.infinityfree.com` and `ns2.infinityfree.com`. This means you can add the records to the control panel of the hosting account hosting this domain name. The records can be added to the “CNAME Records” section.

**If you’re using third party nameservers, like Cloudflare,** you need to add the DNS records through the interface of your nameserver provider. Please check with your DNS provider to learn how to do this.

## How should I set up the CNAME records?

_These instructions are for the CNAME Records section in the InfinityFree control panel. If you’re using other nameservers, the instructions may be different._

In the CNAME Records section in the control panel, you will need to create the one or two CNAME records as shown in the client area.

For each of the CNAME records in the client area, do the following:

1. Copy the value of the Record Name row, and paste it to the Record Name field in the control panel.
2. Select the right domain name from the Domains dropdown in the control panel.
3. Copy the value of the Destination row, and paste it to the Destination field in the control panel.
4. Click the Add button.

### Note about using subdomains

If you want to add SSL to a subdomain of your own domain, the information in the client area isn’t entirely correct. The client area will say to select the subdomain (e.g. [blog.example.com](http://blog.example.com)) but the control panel only shows the base domain (e.g. [example.com](http://example.com)).

So fix this, you can add the subdomain to the Record Name field. So if the client area says that the Record Name is `_acme-challenge.www` and the domain is `blog.example.com`, you can also create these with the record name `_acme-challenge.www.blog` and domain `example.com`.

## I have added the CNAME records, what’s next?

It will take a few hours for the DNS changes to be fully rolled out.

During this rollout, the client area may say the DNS records are Ready, or may do so intermittently.

Once the client area detects the CNAME record, it will say the domain is Ready and the Request Certificate button will be enabled. At this time, you can try to request the certificate, but it can fail with error messages saying the domain name could not be valid. If that happens, simply try again later.

## I’ve received my SSL certificate, should I delete the CNAME records?

You’re always free to delete the CNAME records. Deleting the CNAME records will not break any SSL certificates that have already been issued.

However, we recommend that you keep the CNAME record. The same CNAME record will be used when you want to renew your certificate. So by leaving it in place, you’ll be able to renew the certificate quickly and easily if your current certificate is due to expire.

## Video Tutorial

[![](https://infinityfree-forum-uploads.s3.dualstack.eu-central-1.amazonaws.com/original/3X/4/1/4186ac4ac3864009d0a66b02cdc36638f170ee86.jpeg "Add CNAME records with InfinityFree") ](https://www.youtube.com/watch?v=B59aD1adfG8)

---

<div class="post-metadata">

**Author:** ![anon70553301](https://forum.infinityfree.com/letter_avatar/anon70553301/32/6_449c533f586939b6e5f246632a46421f.png) [@anon70553301](https://forum.infinityfree.com/u/anon70553301)\
**Post date:** [December 27, 2021, 8:06am UTC](https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321/2 "2021-12-27T08:06:49Z")

</div>

> [@Admin](#):
>
> On this page, you’ll see one CNAME record, with a destination ending at `comodoca.com`. This is the CNAME record you need to add.

but mine is not [comodoca.com](http://comodoca.com) instead it is [sectigo.com](http://sectigo.com)

what should I do? @jaikrishna.t @FlutterHoney

---

<div class="post-metadata">

**Author:** ![FlutterHoney](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/flutterhoney/32/17560_2.png) [@FlutterHoney](https://forum.infinityfree.com/u/FlutterHoney)\
**Post date:** [December 27, 2021, 8:11am UTC](https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321/3 "2021-12-27T08:11:26Z")

</div>

Perhaps outdated and admin forgot to update it.

---

<div class="post-metadata">

**Author:** ![Admin](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/admin/32/36437_2.png) [@Admin](https://forum.infinityfree.com/u/Admin)\
**Post date:** [December 27, 2021, 8:48am UTC](https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321/4 "2021-12-27T08:48:55Z")

</div>

I hadn’t fully realized Comodo/Sectigo changed the CNAME domain for the verifications. It’s updated now, thanks!

---

<div class="post-metadata">

**Author:** ![jaikrishna.t](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/jaikrishna.t/32/57109_2.png) [@jaikrishna.t](https://forum.infinityfree.com/u/jaikrishna.t)\
**Post date:** [December 27, 2021, 10:34am UTC](https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321/5 "2021-12-27T10:34:26Z")

</div>

They pretty much informed everyone that 3 years ago! You can find that in your reseller modules 😉 !

![image](https://forum-cdn.infinityfree.net/original/3X/1/d/1dcc6e46c3b9a991b1783f472738cb1fa65db696.jpeg)

---

<div class="post-metadata">

**Author:** ![Admin](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/admin/32/36437_2.png) [@Admin](https://forum.infinityfree.com/u/Admin)\
**Post date:** [December 27, 2021, 4:23pm UTC](https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321/6 "2021-12-27T16:23:13Z")

</div>

> [@jaikrishna.t](#):
>
> They pretty much informed everyone that 3 years ago!

Except their own developers apparently, because the domain verification using the [comodoca.com](http://comodoca.com) domain until much more recently than that.

This article was written in October last year and was accurate then.

Rebranding a big company like that takes time. Just because there are references after the name change is announced automatically mean the information is wrong.

---

<div class="post-metadata">

**Author:** ![Greenreader9](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/greenreader9/32/22847_2.png) [@Greenreader9](https://forum.infinityfree.com/u/Greenreader9)\
**Post date:** [March 18, 2022, 8:05pm UTC](https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321/8 "2022-03-18T20:05:32Z")

</div>

Split this topic on March 18, 2022, 8:05pm UTC

A post was split to a new topic: [SSL Help](https://forum.infinityfree.com/t/ssl-help/59343)

---

<div class="post-metadata">

**Author:** ![Jri-Creator](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/jri-creator/32/65654_2.png) [@Jri-Creator](https://forum.infinityfree.com/u/Jri-Creator)\
**Post date:** [May 12, 2025, 5:18pm UTC](https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321/9 "2025-05-12T17:18:36Z")

</div>

> [@Admin](#):
>
> If you’re using GoGetSSL:
> 
> 1. Click the Request SSL Certificate button, or click the Pending certificate already there.
> 2. On this page, you’ll see one CNAME record, with a destination ending at `sectigo.com`. This is the CNAME record you need to add.

GoGetSSL is deprecated. Should we update this (remove it)?

---

<div class="post-metadata">

**Author:** ![Admin](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/admin/32/36437_2.png) [@Admin](https://forum.infinityfree.com/u/Admin)\
**Post date:** [May 12, 2025, 7:45pm UTC](https://forum.infinityfree.com/t/how-to-create-the-cname-records-for-free-ssl/49321/10 "2025-05-12T19:45:08Z")

</div>

I made some quick changes to remove some of the most out of date information. The current instructions should work, but are skipping some newer changes like the automatic CNAME setup and the ability to create DNS records from the client area.
