Project hostname returns NXDOMAIN from authoritative DNS — project is Healthy

[oyeleketemitope787-sys]

Hello Supabase team,

My project temmy-smart-classroom is showing Healthy in the Supabase dashboard, but its public hostname does not resolve.

Project reference: jozdlxxhjjublqhtiwpy
Region: Southeast Asia (Singapore)
Project URL: https://jozdlxxhjjublqhtiwpy.supabase.co

The dashboard shows the project as Healthy and the Data API is enabled.

I tested DNS resolution using:

Local DNS: 10.247.111.35 → NXDOMAIN
Google DNS: 8.8.8.8 → NXDOMAIN
Cloudflare DNS: 1.1.1.1 → NXDOMAIN
Authoritative nameserver: christina.ns.cloudflare.com → NXDOMAIN

I also restarted the project and confirmed that it returned to Healthy, but the hostname still returns NXDOMAIN.

Could you please check whether the DNS/API Gateway record for this project was provisioned correctly and, if necessary, re-provision the project's public DNS record?

Thank you.

[amasen02]

When authoritative Cloudflare nameservers (christina.ns.cloudflare.com) return NXDOMAIN for <ref>.supabase.co while the project shows HEALTHY in the dashboard, the project's compute instance was provisioned successfully, but the control plane's edge-DNS registration step into the supabase.co zone failed or timed out during creation.

Restarting the project from the dashboard only reboots the Postgres VM/container; it does not re-run the edge DNS provisioning worker in Supabase's control plane.

Here is how you can unblock access right now and how to trigger a re-provision:

---

1. Immediate Database Access via Shared Pooler (Bypasses .supabase.co DNS)

The shared Supabase connection poolers do not depend on your individual <ref>.supabase.co hostname. Since your project is in Southeast Asia (Singapore) (ap-southeast-1), the regional pooler endpoint is:

• Host: aws-0-ap-southeast-1.pooler.supabase.com
• Port: 6543 (Transaction mode) or 5432 (Session mode)
• User: postgres.jozdlxxhjjublqhtiwpy
• Database: postgres

Connection string format:

postgresql://postgres.jozdlxxhjjublqhtiwpy:[YOUR-PASSWORD]@aws-0-ap-southeast-1.pooler.supabase.com:6543/postgres

This resolves immediately to AWS ELBs and routes queries directly to your healthy database, allowing you to access and inspect your data without waiting for the API gateway DNS.

---

2. How to Force the Control Plane to Re-provision Edge DNS

Because a standard restart skips edge configuration, try a full Pause and Resume cycle:

1. Go to Project Settings → General.
2. Scroll to the bottom and click Pause project.
3. Wait until the dashboard indicates the project is fully PAUSED.
4. Click Resume project.

Unlike a simple container reboot, resuming a paused project runs the full provisioning pipeline, which registers edge ingress rules and pushes the CNAME to Cloudflare.

---

3. Submitting the Support Request

GitHub Discussions are community-monitored, and community members cannot modify Cloudflare zone records for supabase.co. If a full pause/resume cycle does not write the record, submit a ticket directly at:

👉 supabase.help

Select Issue Type: Database / Connectivity issue and include your reference jozdlxxhjjublqhtiwpy. Support can trigger the internal DNS reconciliation job for the project reference.

[oyeleketemitope787-sys]

Update: I completed the recommended full Pause → Resume cycle. Supabase confirmed that the project was successfully restored and is now showing Healthy. However, the public hostname still returns DNS_PROBE_FINISHED_NXDOMAIN.

I also previously confirmed NXDOMAIN from local DNS, Google DNS (8.8.8.8), Cloudflare DNS (1.1.1.1), and the authoritative nameserver (christina.ns.cloudflare.com).

Therefore, the Pause → Resume cycle did not resolve the issue.

Could Supabase Support please check and re-provision/reconcile the edge-DNS registration for project reference jozdlxxhjjublqhtiwpy?

Thank you.

[amasen02]

Thanks for testing the pause/resume cycle and confirming. Since the automated provisioning pipeline didn't push the Cloudflare record, this confirms an edge sync reconciliation lock on the project ref jozdlxxhjjublqhtiwpy.

Because Supabase staff do not triage infrastructure provisioning directly from GitHub Discussions, definitely head over to https://supabase.help (or click Help / Support in the top-right corner of your Supabase dashboard) and file a ticket with reference jozdlxxhjjublqhtiwpy. Support engineers have direct access to run the internal DNS reconciliation job.

In the meantime, the direct regional pooler (aws-0-ap-southeast-1.pooler.supabase.com:6543) remains fully accessible for your database queries/migrations while the edge API hostname is being linked by support.

[oyeleketemitope787-sys]

Thank you, Ama. I have already submitted a Supabase Support request for this issue under ticket *SU-464321*. The project has completed a full Pause → Resume cycle, but the hostname *jozdlxxhjjublqhtiwpy.supabase.co <http://jozdlxxhjjublqhtiwpy.supabase.co>* still returns *DNS_PROBE_FINISHED_NXDOMAIN*. I am currently waiting for Supabase Support to check/re-provision the edge-DNS registration. I will update this discussion once Support responds.

…

On Sat, Sep 5, 2026 at 12:32 PM Ama Senevirathne ***@***.***> wrote: Thanks for testing the pause/resume cycle and confirming. Since the automated provisioning pipeline didn't push the Cloudflare record, this confirms an edge sync reconciliation lock on the project ref jozdlxxhjjublqhtiwpy. Because Supabase staff do not triage infrastructure provisioning directly from GitHub Discussions, definitely head over to *https://supabase.help <https://supabase.help>* (or click *Help / Support* in the top-right corner of your Supabase dashboard) and file a ticket with reference jozdlxxhjjublqhtiwpy. Support engineers have direct access to run the internal DNS reconciliation job. In the meantime, the direct regional pooler ( aws-0-ap-southeast-1.pooler.supabase.com:6543) remains fully accessible for your database queries/migrations while the edge API hostname is being linked by support. — Reply to this email directly, view it on GitHub <#50029?email_source=notifications&email_token=CNMLLOSTAZ6HQSATENJ5UE35NPFQRA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGAYTOOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18301791>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CNMLLOWCMAPPQ7TYWJQVSET5NPFQRAVCNFSNUABIKJSXA33TNF2G64TZHMZDCNBVHA3TCOJTHNCGS43DOVZXG2LPNY5TCMBXGUZTAMJRUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CNMLLOV4X6DL35ERZ2SAF2T5NPFQRA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGAYTOOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/CNMLLOSBBWCK65SY6RMTCT35NPFQRA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGAYTOOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>