SSL validation stuck — CNAME confirmed on both InfinityFree nameservers

[matiasyima]

Website URL

https://fodunderground.cl

Error Message

Hello InfinityFree Support,

My SSL certificate request for fodunderground.cl is stuck at “Action Required / No CNAME found”.

Hosting account: if0_43406675

I have verified the required CNAME directly against three DNS servers:

Cloudflare (1.1.1.1): Correct

ns1.infinityfree.com: Correct

ns2.infinityfree.com: Correct

All three return:

_acme-challenge.fodunderground.cl

CNAME target:

613ad61a-3a65-4ad6-8200-50c8b1386035.acmedns.infinityfree.net

Despite this, the InfinityFree SSL dashboard still shows “No CNAME found — Not Ready” and prevents me from requesting the certificate.

I found a similar DNS detection issue reported on October 12, 2026, which was confirmed and fixed by the administrator.

Could you please check whether the SSL validation system is experiencing this issue again?

I have screenshots confirming the DNS responses from both InfinityFree nameservers.

Thank you.

Other Information

…

[Lemni]

Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.

The knowledge base article on the SSL CNAME records says the DNS changes take a few hours to roll out fully. During that time the client area may show the record as Ready only intermittently, or not at all. Once it detects the record, it says Ready and enables the Request Certificate button.

Your hosting account was only created a few hours ago, so this may just be that delay. Here’s the article:

How to create the CNAME records for free SSL

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 t…

I’m not sure that’s the cause, though. When did you add the _acme-challenge CNAME record in the control panel? And does the destination shown on the SSL certificate page right now match the one you added, character for character? That’s worth checking if you created the certificate order more than once.

[matiasyima]

@Lemni

Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.

The knowledge base article on the SSL CNAME records says the DNS changes take a few hours to roll out fully. During that time the client area may show the record as Ready only intermittently, or not at all. Once it detects the record, it says Ready and enables the Request Certificate button.

Your hosting account was only created a few hours ago, so this may just be that delay. Here’s the article:

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 t…

I’m not sure that’s the cause, though. When did you add the _acme-challenge CNAME record in the control panel? And does the destination shown on the SSL certificate page right now match the one you added, character for character? That’s worth checking if you created the certificate order more than once.

Hello, thanks for your response.

I created the SSL certificate request on November 10, 2026, at 19:58 UTC.

I added the _acme-challenge CNAME shortly afterward, approximately between 20:00 and 20:10 UTC.

I can confirm that the destination currently displayed on the SSL certificate page matches the DNS record exactly, character for character.

The expected CNAME target is:

613ad61a-3a65-4ad6-8200-50c8b1386035.acmedns.infinityfree.net

I verified it using:

• nslookup -type=CNAME _acme-challenge.fodunderground.cl 1.1.1.1

• nslookup -type=CNAME _acme-challenge.fodunderground.cl ns1.infinityfree.com

• nslookup -type=CNAME _acme-challenge.fodunderground.cl ns2.infinityfree.com

All three DNS servers return the exact expected target.

However, the InfinityFree SSL dashboard still reports:

“No CNAME found — Not Ready”

I understand DNS propagation may take several hours. I will allow more time for the validation system to update.

If it remains stuck despite the record resolving correctly from both authoritative nameservers, could an administrator investigate the DNS verification process?

Thank you.