Active Member

Solved

Custom Domain DNS TXT Records Issue

Forum|Forum|1 year ago
June 11, 2025
13 replies
960 views

Heyyy,

Both in Figma Make and Figma Sites, the TXT DNS Records are not getting verified quickly. The CNAME Records instantly update and sync, but the TXT doesn’t update even after 48 hours.

One of my first Figma Sites got published, but beyond that none of my other sites or Make Websites are getting laucnhed or connected to the domain due to TXT DNS Record verification delay

This topic has been closed for replies.

Best answer by Tom Reem

Hi @Imtiyaz_Ahmed — thanks for flagging this. Checking in, are you still running into trouble with the TXT setup? I’m not able to share account-specific details here in the forum, but I can see you’ve been in touch with our Technical Quality team, who can take a closer look at your domain configuration. 💯

Generally speaking, since you were able to get it working for your first site, I’d recommend double-checking how the TXT record was entered for the others. TXT record propagation can sometimes take a few extra hours depending on the DNS host. If it hasn’t updated after 48 hours, as you mentioned above, that may be a sign to review the values you entered. If anything’s off, Figma should display an ⚠️ error icon in the file.

For more detailed steps and troubleshooting, check out this Figma Learn article: Manage a custom domain for your site.

Hope this helps point things in the right direction — and keep me posted!

Tom ReemAnswer

Figmate

Hi @Imtiyaz_Ahmed — thanks for flagging this. Checking in, are you still running into trouble with the TXT setup? I’m not able to share account-specific details here in the forum, but I can see you’ve been in touch with our Technical Quality team, who can take a closer look at your domain configuration. 💯

Generally speaking, since you were able to get it working for your first site, I’d recommend double-checking how the TXT record was entered for the others. TXT record propagation can sometimes take a few extra hours depending on the DNS host. If it hasn’t updated after 48 hours, as you mentioned above, that may be a sign to review the values you entered. If anything’s off, Figma should display an ⚠️ error icon in the file.

For more detailed steps and troubleshooting, check out this Figma Learn article: Manage a custom domain for your site.

Hope this helps point things in the right direction — and keep me posted!

Imtiyaz_AhmedAuthor

Active Member

@Tom Reem Heyyyyy,

Hope you are doing fine. And yes you and the team was right. The issue was the delay in propogation of the TXT records. I changed them internally probably at the time they were getting verified, hence it caused the glitch issues.

Issue has been resolved thanks

Tom Reem

Figmate

Awesome — thanks for confirming, @Imtiyaz_Ahmed! Really appreciate you surfacing this here — helps others who might run into the same thing. Hope all’s well on your end! 💯

Imtiyaz_AhmedAuthor

Active Member

Awesome — thanks for confirming, @Imtiyaz_Ahmed! Really appreciate you surfacing this here — helps others who might run into the same thing. Hope all’s well on your end! 💯

Anytime brother, anytime! @Tom Reem Always here to help Figma be the best it can be

prasanna_mindpalace

New Participant

@Tom Reem

Can you please help resolve this issue I'm facing while trying to connect my domain to Figma Make?

Imtiyaz_AhmedAuthor

Active Member

@Tom Reem

Can you please help resolve this issue I'm facing while trying to connect my domain to Figma Make?

Hey Mate,

Might be able to help you out here. Can you explain whats the problem you are facing?

prasanna_mindpalace

New Participant

Thanks for offering your help.

I’m seeing this error. Unable to connect Figma Make with my domain. Can you tell me how to solve this?

Imtiyaz_AhmedAuthor

Active Member

Thanks for offering your help.

I’m seeing this error. Unable to connect Figma Make with my domain. Can you tell me how to solve this?

Okayy, so found the solution to the issue. The answer was present in the Figma Learn Docs

Conflicting AAAA record on apex domain: If you're connecting an apex domain—like example.com—using an A record, check whether there’s an existing AAAA (IPv6) record on the same host (@). Having both can prevent your domain from connecting properly. Remove the AAAA record from your DNS settings and try again.

So in simple words :

You have two records for your main domain (like example.com):

A record → connects your domain to an IPv4 address (the normal one).
AAAA record → connects your domain to an IPv6 address (a newer type).

The problem is that both are active right now, and they’re conflicting, your site can’t decide which one to use.

What to do:
Go to your domain’s DNS settings.
Find any record that says and delete it:
Type: AAAA
Name: @

Wait 5-10 mins, try reconnecting and it should work.

prasanna_mindpalace

New Participant

Thanks for your kind help.

It looks like my DNS settings doesn’t have AAAA type.

What shall I do?

Imtiyaz_AhmedAuthor

Active Member

Thanks for your kind help.

It looks like my DNS settings doesn’t have AAAA type.

What shall I do?

Can you give more context? Like a screenshot of your DNS setting and stuff? Its harder to understand anything like this

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO