We're experiencing the same issue with DNS CNAME record verification. It’s also critical for us, so we’d really appreciate any support or updates on this as soon as possible. Thanks in advance!

Hey ​@Rajshree Agarwal and ​@Patrick Michelberger, thanks for joining Figma Forum and for raising this. Checking in — are you still seeing the same issue? And if so, how long has the verification error been happening?

​@Rajshree Agarwal — firstly, I went to steora.ai and it appears to be up (🎉) — can you confirm that it is showing up as expected now as well? If not, we’ll keep digging. I noticed in your screenshot that there appears to be an SSL-related issue. Without being able to see your exact settings, it’s tough to say for sure — but this section of Figma Learn may help clarify what’s going on: Manage a custom domain for your site → Troubleshoot the domain connection.

Here’s a key snippet from that guide:

Next steps: Could you double check if you have any CAA (Certificate Authority Authorization) DNS records configured for your domain? If so, make sure they allow certificates from Google Trust Services, Let's Encrypt, and SSL.com. As an example, this can be done by adding the following DNS records:

• example.com. IN CAA 0 issue "pki.goog"
• example.com. IN CAA 0 issue "letsencrypt.org"
• example.com. IN CAA 0 issue "ssl.com"

You can also remove any CAA DNS records that aren’t from these three providers.

Also worth noting:

• Domain propagation can sometimes take a few extra hours depending on your DNS host.
• If things still haven’t updated after 48 hours, double-check that all your values are correct — Figma Sites will continue to show a ⚠️ if something’s off.

If that doesn’t clear things up and you’d like someone to take a closer look a specifics, our Technical Quality team can take a deeper dive. You can open a ticket directly and include:

1. a link to this Forum thread for context
2. a brief summary of the steps you took
3. a link to the file you’re working out of
4. edit access for support-share@figma.com on the file.

Let us know how it’s going — we’re here to help get this sorted. 🙏🏻

Hi ​@Tom Reem ,

It looks like the CNAME record still hasn’t been verified:

This process is taking quite a long time. So far, we haven’t set the A record because we’re waiting for the CNAME to be verified first — otherwise, our current application would become inaccessible.

Could you check if that’s an issue on your side, or let us know if you can already see the record?

Thanks in advance!

​​​​​​

Hey ​@Patrick Michelberger — thanks for the update, and I’m sorry to hear the verification still hasn’t gone through.

To make sure we can look into the specifics carefully, I’ve opened a ticket on your behalf with our Product Support team. When you have a moment, please check your inbox for an email from me (case number: 1443396) with the next steps.

If you reply there, we’ll be able to take a deeper dive. Really appreciate you working with us on this!

Thanks for your quick reply! I just saw the email and will reply there now. Appreciate your support!

Of course, ​@Patrick Michelberger — always happy to help! Thanks so much for your patience and for working with us to get this sorted out. 💯