AI & Agent Dev Bug Sandbox Back to Radar

DNS NXDOMAIN For Active Supabase Project Qxvnbmwhyrinsarnazkb.Supabase.Co

User reports that project hostname qxvnbmwhyrinsarnazkb.supabase.co returns NXDOMAIN from public DNS (8.8.8.8) and Chrome reports DNS_PROBE_FINISHED_NXDOMAIN, despite the project being active in the Supabase Dashboard. This indicates a missing DNS record for the project's subdomain in the supabase.co zone, likely due to a provisioning failure.

highConfidence 87%Supabase

Origin Analysis

The project's DNS record was not created or was removed in the authoritative supabase.co zone. This can occur due to an asynchronous provisioning race during project creation in the Mumbai region, or a stale dashboard state showing active while the underlying hostname was deprovisioned.

1. Open Supabase Dashboard and confirm project qxvnbmwhyrinsarnazkb is active. 2. Run `nslookup qxvnbmwhyrinsarnazkb.supabase.co 8.8.8.8` on Windows. 3. Observe output: `dns.google can't find qxvnbmwhyrinsarnazkb.supabase.co: Non-existent domain`. 4. Open Chrome and navigate to https://qxvnbmwhyrinsarnazkb.supabase.co. 5. Observe `DNS_PROBE_FINISHED_NXDOMAIN`. 6. Optionally query other resolvers (1.1.1.1, 9.9.9.9) to confirm global NXDOMAIN.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

Running this script does not fix the DNS record; it only detects. The actual fix requires Supabase internal DNS management. Attempting manual DNS changes without knowing the correct target IP/CNAME can break routing. Do not add hosts file entries as they are not scalable and will bypass CDN/SSL. Rollback: if a DNS record is manually added, ensure TTL is initially low and monitor propagation before removing any temporary workaround.