Custom Domain Onboarding Uses Live DNS Reads Before Storefront Cutover
A successful DNS write is too early to confirm a tenant's hostname is ready, since customers can later edit records and invalidate a stored flag. The recommended approach drives the onboarding UI from a live record read combined with domain verification status, cached briefly with a visible check time. Record presence alone is not treated as verification, and storefront readiness is kept separate from email authentication such as DMARC. The article illustrates this with a sample tenant, using narrowly worded states like awaiting records, awaiting verification, or check unavailable. It also notes that cache lifetime governs how often the application re-queries the API, not how quickly DNS changes propagate.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in