Project hostname returns NXDOMAIN and Cloudflare gets HTTP 530

[dds-1709]

Hi, I’m having a DNS resolution issue with a Supabase project.

Project name: suite-atendimento
Project ref: wzzkxjcwrcpxijjwwuke
Region: sa-east-1

Project URL:
https://wzzkxjcwrcpxijjwwuke.supabase.co

The Supabase dashboard shows the project and Data API normally, but the project hostname does not resolve.

Direct browser access returns:
DNS_PROBE_FINISHED_NXDOMAIN

Requests from Cloudflare Pages Functions return:
HTTP 530

I already opened a Supabase support ticket:
SU-444246

I have confirmed that the project URL configured in Cloudflare matches the Project Ref shown in Supabase.

Has anyone seen a Supabase project hostname lose DNS resolution like this? Is there anything project-side that can be checked, or does this require Supabase to reprovision the DNS record?

[kaminagakur4]

It needs Supabase, and there's nothing project-side left to check. NXDOMAIN from Google, Cloudflare, Quad9 and OpenDNS is expected given what you're seeing, but the part that settles it is asking the authority directly: dig wzzkxjcwrcpxijjwwuke.supabase.co @christina.ns.cloudflare.com (and @neil.ns.cloudflare.com) also returns NXDOMAIN, and those two are the authoritative nameservers for supabase.co, so this isn't caching or propagation. The record does not exist. Two controls make it conclusive: made-up refs return NXDOMAIN at the authority too, so there's no wildcard on *.supabase.co and every project has its own record; and a project in another thread here that's been down for days with a full disk and a database that won't start still resolves fine, which means DNS provisioning is independent of project health. That rules out anything inside your project as the cause, and it's why pause/resume can't fix it. Your Cloudflare 530 is the same fact rather than a second problem, since their docs define it as Cloudflare being "unable to resolve the origin hostname". For SU-444246, the sentence worth adding is that the record is absent at the authoritative nameservers, which points at their DNS provisioning rather than at your project.

[blueocean2014]

I am experiencing the same issue with my Supabase project.

Project ref: nmzowasvtqzkvqhhamb
Project name: 支援経過作成支援アプリ開発
Region: ap-south-1

The Supabase dashboard shows the project as Healthy, and the Data API URL is shown correctly.

However, the project hostname does not resolve:

https://nmzowasvtqzkvqhhamb.supabase.co

I tested DNS resolution directly using both Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1).

Both return:
Non-existent domain / NXDOMAIN

Because of this, my web application cannot connect to Supabase Authentication and login fails with:
"Failed to fetch"

I would like to keep this existing project and its users. I do not want to create a new project.

Could you please check the DNS provisioning for this project and restore the project hostname?

[GaryAustin1]

You need to file a support ticket. This will not get resolved from Github.