Supabase project active but API hostname returns NXDOMAIN

[martimoro01-cloud]

Hi, my Supabase project is active, but its API hostname does not resolve.

Project ref: dhxezxwslrbuszavzdi

URL: https://dhxezxwslrbuszavzdi.supabase.co

Google Public DNS returns NXDOMAIN (Status 3).

The database is running, the Data API is enabled, and the dashboard shows the correct project URL. The issue occurs on different networks and devices.

This is blocking my Vercel application's migration.

Support ticket: SU-537272

Is there a way to restore DNS resolution without recreating the project or losing the migrated data?

Thanks!

[GaryAustin1]

It does look like your project is not on the net from a public check of the url.
If you have tried restart project from general settings and that does not work then you'll have to wait on support to resolve it.

You can use CLI to migrate to another instance if in a hurry, but somewhat painful if you have files in storage. https://supabase.com/docs/guides/platform/migrating-within-supabase

[VictorPimentaDev]

Look at the ref closely. dhxezxwslrbuszavzdi is 19 characters. Supabase project refs are 20 lowercase letters, so a character is missing and that hostname simply does not exist, which is exactly what NXDOMAIN means.

Copy the URL straight from Project Settings → Data API (or Settings → General for the ref) instead of retyping it, then check:

dig +short <your-20-char-ref>.supabase.co

You should get IPs back. If your Vercel env vars were pasted by hand, fix NEXT_PUBLIC_SUPABASE_URL / SUPABASE_URL there too and redeploy, since env vars are baked in at build time.

If the ref in the dashboard really is that same 19 character string, then it is a support case and SU-537272 is the right place, but I would bet on a copy error first.

[fedyfsgerana]

Hi,

The first thing I would check is the project reference itself. The project ref in your post (dhxezxwslrbuszavzdi) appears to contain only 19 characters, while Supabase project references are normally 20 characters long.

Please copy the Project URL directly from Dashboard → Project Settings → API and compare it with the hostname you are testing. Avoid typing the project reference manually.

If the reference is correct, I would suggest checking the hostname against both Google Public DNS and Cloudflare DNS:

nslookup dhxezxwslrbuszavzdi.supabase.co 8.8.8.8

nslookup dhxezxwslrbuszavzdi.supabase.co 1.1.1.1

Also, verify that the project is not paused. If it is already active and the correct hostname still returns NXDOMAIN from both resolvers, this likely requires investigation by Supabase support.

Since you already have ticket SU-537272, I would share these DNS results with the support team and ask them to verify the DNS record and API hostname provisioning for the existing project.

I would avoid recreating the project until Supabase support has investigated the issue, especially since you want to preserve your existing database and migrated data.

Hope this helps!