Skip to main content
CurateOneWiki
Open CurateOne

My custom domain isn’t connecting

DNS can take up to 48 hours — verify the exact records, watch the live status in the domain panel, and know the one error that needs action.

Updated 2026-07-16

01Give DNS time

DNS propagation can take up to 48 hours, though it’s usually far quicker. If you added your records recently, the most likely fix is simply waiting.

02Verify the exact records

The domain panel in /deployments shows precisely what your domain needs: an A record for an apex domain (example.com), a CNAME for a subdomain (www.example.com). Compare what’s at your registrar against what the panel shows, character for character.

TipCopy the record values straight from the domain panel rather than retyping them — a stray character or the wrong record type is the most common culprit.

03Watch the live status

You don’t need external DNS checkers — the domain panel polls resolution live and shows the current state. When your records are seen, the status moves forward and SSL is provisioned automatically.

04“Domain already in use”

If your domain is already attached to another account with our hosting provider, the panel shows an actionable error explaining exactly that. Follow the steps in the error — this case doesn’t resolve by waiting.

Related articles

Connect a custom domainPoint your own domain at your CurateOne site — guided DNS records, live status polling, and automatic SSL.My subdomain shows “launching soon”Provisioning runs three checks before your URL goes live — here’s what they are and what to do if one lingers.