Skip to main content
Question

DNS Proxy - turn off?

  • June 21, 2026
  • 3 replies
  • 33 views
drthommcf

Hi everyone,

I am attempting to link a custom domain to a site built on Figma, but we are running into errors during the setup process.

Our systems administrator manages our DNS independently through custom nameservers (DNS Made Easy). We have already configured the DNS records based on the provided values (A record pointing to the server IP, TXT record for site verification, and a CNAME pointing to sites.figma.net).

However, we are hitting the following roadblocks:

  1. Incomplete Server Configuration: When a browser attempts to connect to the domain, it successfully reaches the server IP address provided by Figma, but the server responds that it doesn’t recognise or know anything about the domain. It appears the host is not yet correctly configured to respond to our domain traffic.

  2. Missing DNS Proxy Toggle: Our administrator suspects that a backend DNS Proxy (Cloudflare intercept) might be toggled on automatically for our domain and CNAME configuration. According to the documentation, this needs to be set to "DNS only" for custom verification to complete cleanly. However, there is currently no user-facing toggle within our Figma site admin panel to turn this off.

Has anyone using an independent, custom DNS provider run into this same error? Is there a way to request that Figma support manually disable the DNS proxying for our custom domain on the backend?

Thanks for any insights or guidance!

3 replies

Tom Reem
Figmate
  • Tom Reem
  • Figmate
  • June 21, 2026

Hey ​@drthommcf, welcome to the Figma Forum! Thanks for the thorough writeup — I took a closer look and I think I know what may be happening.

A quick clarification on the DNS Proxy question: The requirement to set proxy status to "DNS only" applies specifically to those who manage their domain's DNS directly through Cloudflare as their DNS provider. Since you're using DNS Made Easy, that is likely why there’s no Cloudflare proxy toggle on your end. Your DNS Made Easy records pointing to sites.figma.net should be fine on that front.

The more likely cause for the server not recognizing your domain is that domain verification or SSL certificate provisioning hasn't fully completed on Figma's side yet. There's a bit more on what can cause delays in the troubleshooting section of this Figma Learn article: Manage a custom domain for your site → Troubleshoot the domain connection.

That said, since the backend configuration is something Product Support can check directly, I'd like to open a ticket — and a couple of details would help us move quickly:

  1. What is the exact error message the server is returning?
  2. What is the specific URL/domain you're trying to configure (if you’re able to share it)?

Once I have that info, I'll get a ticket opened so the team can look at your domain's verification and SSL status on our end. Let me know! 🙏🏻

drthommcf
  • drthommcf
  • Author
  • New Member
  • June 21, 2026

Thanks Tom!

 

What is happening is that a browser attempt to connect to our apex domain: centralpaediatrics.com.au gets to the server IP address and the server is responding that it doesn't know anything about this domain and cannot direct the browser to the website.  The server has to be configured to respond to our domain.

 According to our administrator, “the web server IP that is flagging the error as pertaining to cloudflare.  Its saying the IP address you've given me is a cloudflare server which if setup correctly for your domain, will filter requests for your website against a DDOS database before allowing the content to be backfed/redirected to the requesting web client.  But at the moment it doesn't know about your domain.”

    Tom Reem
    Figmate
    • Tom Reem
    • Figmate
    • June 23, 2026

    Hello again, ​@drthommcf — thanks for following up with those details from your administrator. That's helpful context.

    Since this appears to be a server-side configuration issue on the Cloudflare layer, our Product Support team will need to look into it directly to confirm specifics. I've opened a ticket on your behalf and your case number is: 1978109.

    Please keep an eye on the inbox tied to your Figma account for next steps. If anything else comes up, I’ll keep watch here as well! 🙏🏻

    Terms & ConditionsAccessibility statement