Parked Domain high
Domain Shows a Registrar Parked Page (Nameservers Not Pointed)
The domain resolves to the registrar's parking page because nameservers still point at registrar defaults instead of your host.
What you see
"Future home of something quite cool." "This domain is parked free, courtesy of <Registrar>." "Welcome — this site is under construction."
What’s actually happening
You typed the domain expecting your site and got a generic "future home" or sponsored-links page from the registrar. Email to the domain also bounces or vanishes because MX never resolves to your mail host. dig NS yourdomain.com returns the registrar's default nameservers (e.g. ns1.registrar-servers.com), not the ones your hosting/DNS provider gave you.
Common causes
- Nameservers at the registrar were never changed from the registrar's defaults to the host's
- A registrar-side process (renewal, security hold, account change) reverted nameservers to defaults
- DNS records were added at the host, but the domain's authoritative DNS is still the registrar's parking zone
- Domain was just registered and the host's nameservers haven't been entered yet
- Privacy/parking add-on re-enabled itself and re-pointed the nameservers
How to fix it
- Read the actual nameserversRun dig NS yourdomain.com +short. If they're the registrar's defaults rather than the pair your host gave you (e.g. ns1.yourhost.net / ns2.yourhost.net), the records you edited live in the wrong place and are being ignored.
- Set nameservers to your DNS host at the registrarIn the registrar dashboard, find the domain's Nameservers / DNS setting and switch from "registrar default / parking" to "custom" — then enter your host's nameservers exactly. This is the change that actually moves authority off the parking zone.
- Decide where DNS records should liveIf you point nameservers at your host, recreate A/CNAME/MX/TXT records there. If you'd rather keep DNS at the registrar, leave the registrar nameservers but turn off parking and add the records in the registrar's DNS editor. Don't split the two — records only matter at whoever holds the NS.
- Disable any parking or "for-sale" add-onLook for a Parking, CashParking, or domain-marketplace toggle in the registrar account and switch it off so it can't re-point nameservers back to the parking servers.
- Wait for propagation, then verify end to endAllow up to 24-48h for the old NS TTL to expire. Confirm with dig NS and by loading the site; check mail with dig MX yourdomain.com to make sure email resolves to your mail host again.
Stop it recurring
After moving a domain to a new host, confirm dig NS returns the host's nameservers — not the registrar defaults — and disable any parking add-on that can revert them.
Related errors