Help Center
platform

Domain parking & nameservers on globNIC

How to enable globNIC parking, which nameservers to set at your registrar, and how it connects to your member listing.

Updated 2026-04-26

What "parking" means on globNIC

  • Your listing in globNIC is the product record (price, status, lead capture, AI content). The public for-sale experience is served on /parking/{yourdomain} (for example: https://globnic.com/parking/example.com).
  • Nameserver (NS) verification points DNS for your domain to globNIC so we can host your parking page, issue HTTPS, and (when applicable) your custom DNS zone. The in-app copy uses ns1.globnic.com and ns2.globnic.com as the only two values to paste at the registrar.
  • If the domain is not in the database, visitors can still see a zero-touch unclaimed page when traffic hits globNIC via DNS; your full experience (offers, AI, analytics) still requires a member listing and a successful verification path below.

globNIC’s verification UI and API support exactly three methods: NS (nameservers), TXT (token at _globnic-verify), and CNAME (to parking.globnic.com). There is no separate “HTML file” or “meta tag” verification path in the current product.

Prerequisites

  • A domain you control at a registrar (or DNS host that allows custom nameservers where required).
  • The domain added under Member → Domains (or Bulk add), then opened on /member/domains/{domain}/verify.

If you cannot change nameservers (Cloudflare, etc.)

  • TXT: Add a TXT record. Host/Name: _globnic-verify (some UIs need the full name _globnic-verify.{domain}). Value: the verification token shown on the verify page (also returned by GET /api/member/domains/verify?domain=...). Click Verify Now after saving.
  • CNAME: Add CNAME for the root (often @ or the bare domain) pointing to parking.globnic.com. On Cloudflare, turn the record to DNS only (grey cloud), not proxied, per in-app guidance. Then verify.
  • Cloudflare API shortcut: On the same verify page, Using Cloudflare? Auto-Configure DNS calls POST /api/member/domains/cloudflare-dns with a one-time Edit zone DNS API token. The token is not stored; you still run verification after propagation.

How this maps to public URLs

  • Parking route: The app uses /parking/[domain] with dynamic rendering; metadata and canonical rules are defined in code (parking may canonicalize to /asset/{domain} for SEO).
  • Unlisted / not-in-DB visits get a generic landing (zero-touch) with no asset row created—designed to avoid junk inventory from random DNS hits.

Domains that are hidden or soft-deleted in the member database will not render the full member parking experience—those paths intentionally 404 in the server page logic.

Related