Supabase project shows Healthy but API hostname returns DNS_PROBE_FINISHED_NXDOMAIN

[businesssquaremark-alt]

Hello Supabase Community,

I am setting up a free Supabase project for my company's internal LMS and facing a DNS connectivity issue.

Project details:

Project name: square-mark-lms

Project status in dashboard: Healthy

Plan: Free

Region: Tokyo, Japan

Error: DNS_PROBE_FINISHED_NXDOMAIN

Issue:

My project dashboard shows Healthy, but the project API hostname does not resolve in Chrome. The same issue occurs when opening the Auth health endpoint.

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

I cannot connect my Netlify-hosted LMS to Supabase because of this issue.

What I have checked:

Confirmed that the project exists and shows Healthy in the dashboard.

Tested the project URL and Auth health endpoint in Chrome.

Confirmed that the browser reports DNS_PROBE_FINISHED_NXDOMAIN.

Could someone help me determine whether this is a project DNS/provisioning issue or a DNS resolver issue?

I want to fix the existing project without deleting or recreating it, and without losing any existing data.

Thank you.

[TheMysteriousGhost]

You're not alone, and it's not your setup. I checked from outside just now:

• duangapogbhgwrlsrbuj.supabase.co returns NXDOMAIN from Supabase's own authoritative DNS, so no browser, ISP or local DNS cache is involved, and flushing DNS won't help.
• The same thing is happening to several other projects reported here in the last few days (Project shows Healthy but Supabase API hostname returns DNS_PROBE_FINISHED_NXDOMAIN after resuming #51655, Supabase Project Healthy but API URL Returns NXDOMAIN #51752, Supabase project hostname returns NXDOMAIN despite Healthy status #51815, Production project API host not resolving in DNS (NXDOMAIN) — dashboard Healthy, SQL Editor works #51816), and the two from Oct 15 that I re-checked a minute ago are still NXDOMAIN after ~2 days. So it isn't propagation and doesn't seem to fix itself, while the status page shows everything operational.

The useful next step is a support ticket (Dashboard → Support) that links these discussions. Several projects with the identical symptom is much more likely to get escalated as a platform issue.

In the meantime, db.<ref>.supabase.co is affected too, but the shared regional pooler hostname (shown under Connect → Connection pooling, e.g. aws-0-<region>.pooler.supabase.com with user postgres.<ref>) still resolves. That lets server-side code reach the database, though not the REST/Auth APIs that the LMS frontend needs.

[kevinjosh10]

Hi @businesssquaremark-alt! This is a known DNS authoritative propagation failure affecting several newly provisioned projects.

---

Why NXDOMAIN Occurs

Even though your project containers in Tokyo (ap-northeast-1) are running and report Healthy in the dashboard, the Route53 authoritative nameservers for *.supabase.co failed to publish the DNS A record for project ref duangapogbhgwrlsrbuj. Because authoritative DNS returns NXDOMAIN, local browser cache flushing will not resolve the issue.

---

Workaround to Unblock Your LMS Immediately

While waiting for Supabase to resolve the root DNS record, you can connect directly to your database through the regional connection pooler, which uses a shared hostname that is not affected by individual project DNS outages:

1. In your Supabase Dashboard, go to Connect → Connection pooling.
2. Notice the pooler hostname:

   aws-0-ap-northeast-1.pooler.supabase.com
   

3. Use port 6543 (Transaction mode) or 5432 (Session mode) with username postgres.duangapogbhgwrlsrbuj.
4. Your backend services can connect and query the database without relying on the duangapogbhgwrlsrbuj.supabase.co hostname.

---

Resolving the API Hostname

Submit a support ticket through Supabase Dashboard → Support specifying:

• Project Ref: duangapogbhgwrlsrbuj
• Region: Tokyo (ap-northeast-1)
• Error: Authoritative DNS returns NXDOMAIN for duangapogbhgwrlsrbuj.supabase.co
  Support can trigger a manual DNS zone sync on their Route53 infrastructure without modifying your database data.