Parking page not showing — fixes & checks

Quick diagnosis table

| Symptom | Most likely cause | What to do | |--------|-------------------|------------| | Browser says not secure or certificate error | DNS not yet pointing to globNIC or local cache | Re-check nameservers or CNAME; wait for propagation; try another network or device | | 404 on /parking/{domain} | Domain hidden, deleted, or invalid hostname in the URL | Restore listing; fix typo; un-hide in member UI | | Generic “may be for sale” page, not your full listing | Zero-touch path — domain not in the Asset table | Add/import the domain in member area and verify | | Stuck “pending” / Verify never succeeds | Wrong TXT/CNAME/NS values or propagation delay | Re-copy from /member/domains/{domain}/verify; wait; use bulk verify for many domains | | “DNS backend temporarily unavailable” in Bulk DNS | PowerDNS or network transient error | API returns 503; wait 1–2 minutes and retry (per server message) |

1) Confirm the public URL and DB state

• URL pattern: The product serves parking at https://globnic.com/parking/{domain} (replace {domain} with your real FQDN, lowercased).
• If you expect the full AI-rich, lead-capture, buy-now experience:
  • The domain must exist as a non-deleted, non-hidden asset in globNIC. If you only pointed DNS and never added the name in the member dashboard, you may get the Unclaimed / zero-touch experience instead of your priced listing.
• If you get 404: The server route returns notFound when the domain fails strict validation, or when a DB-backed asset is hidden or has deletedAt set.

2) DNS propagation and resolver lag

• NS method: At the registrar, only ns1.globnic.com and ns2.globnic.com should remain (two entries). The member UI copy states ~15 minutes common propagation, up to 48 hours worst case.
• TXT method: Name _globnic-verify, value = the token from the verify page / GET /api/member/domains/verify. Propagation: often 2–5 minutes in-app; allow up to 48 hours on slow TLDs or resellers.
• CNAME method: Target parking.globnic.com at the root (@ or equivalent). If you use Cloudflare, the UI requires DNS only (no orange-cloud proxy) for CNAME-based verification and parking alignment.

Verification from your side (no guesswork):

• Query public resolvers (e.g. 1.1.1.1, 8.8.8.8) for NS, TXT, or CNAME as appropriate and compare to the values in the app.
• If the verify API still reports mismatch / pending_propagation after a correct change, wait and retry — POST /api/member/domains/verify and POST /api/member/domains/verify-bulk re-query live DNS; bulk verify processes in batches of 20 and may show “already verified” for finished domains.

3) SSL / HTTPS expectations

• The DnsSetupGuide (member UI) states automatic SSL and HTTPS for nameserver-based parking. If HTTPS fails while HTTP works, typical causes are not globNIC’s button state but:
  • Name/CNAME/NS still points at the old host
  • Ad blocker or corporate SSL inspection
  • Client clock wrong
• If everything is correct but a brand-new zone is still lining up, NS verification in code can complete while parking readiness finishes in the background; the bulk verify path can return success with a note that parking activation is syncing. Wait a few minutes and reload Verify or re-run Bulk Verify if needed.

4) Member-side listing status and visibility

• After verification, listing status and name server status are updated in the database (e.g. Listed when verification succeeds, depending on flow).
• If you hid a domain in the product or moved it to trash, the public parking page for that name will not render the in-depth member experience (404 in code for hidden/deleted).

5) Bulk and automation tips

• Many domains, same fix: GET /api/member/domains/verify-bulk lists pending domains; the UI at /member/domains/verify-bulk lets you select names and run NS, TXT, or CNAME verification. Batch size in the client is 20 per API call. See Bulk tools.
• Cloudflare users: use the edit zone DNS token flow in-app for TXT or CNAME to avoid manual copy mistakes, then verify after 1–2 minutes.

Still stuck?

• Open a support ticket and include: domain name, method (NS/TXT/CNAME), registrar or DNS host, and screenshots of the DNS panel showing the exact host/type/value rows (redact account IDs if needed).