custom-domainlisted

# Custom Domain Pointing a domain at a site is four minutes of real work wrapped in up to twenty-four hours of waiting, and the waiting is where people break things. The DNS is usually right long before the host admits it. Someone who doesn't know that will "fix" correct records three times, enable a proxy setting that stops the host verifying the domain at all, and end up further from working than when they started. So the job here is mostly about **order and patience**, plus one category of failure that is genuinely nasty: settings elsewhere in the stack that were keyed to the old address and now silently refuse to work. The site loads fine. Login doesn't. Nothing logs an error that says why. ## The core mindset **The host tells you the records. Never guess them.** Every platform has its own values and they change. Add the domain in the host's dashboard first and copy what it gives you. **Verify DNS yourself before you believe any dashboard.** `dig` against two public resolvers is ground truth. A host saying "not detected" while `dig` returns the right answer means *wait*, not *change something*. **Assume something else in the stack knows the old URL.** Auth providers, captcha keys, OAuth apps, CORS allowlists, webhooks, email templates, CSP headers. Each keeps its own list of "domains I trust". Phase 3 is the one people skip and it is the one that produces "the site works but I can't log in". **Don't move the canonical URL until HTTPS actually serves.** Telling sear