v0 and Vercel custom domain on Namecheap: fix Invalid Configuration
Short answer. Add the hostname at the service that publishes the site, then copy that project's records into the active DNS zone. Buying another name does not fix a verification error.
Convert your host's record to Namecheap fields
Use the records your host supplies. This formatter removes the DNS zone from a full owner name and preserves your value. Paste public DNS values only.
Use the right publishing route
For a v0 project published on Vercel, open Vercel project → Settings → Domains and add the exact hostname. Use the A or CNAME target that this project's domain settings provide. A generic cname.vercel-dns.com example is not a replacement for its current suggested target.
A domain associated with another account can require an ownership TXT record. Copy the exact name and token shown; a full _vercel.example.com owner becomes _vercel in Namecheap. Keep the record value unchanged. Registration status alone does not establish ownership.
For Invalid Configuration, compare the requested hostname and record type with public DNS, then check for conflicting records at that same owner name. Root and www are separate domain entries. Confirm Vercel accepts the domain, then test HTTPS and the intended production deployment.
Checked against the official setup instructions on 27 October 2026. Current instructions in your own project take priority.
Record exists, but the domain still fails?
Check the DNS troubleshooting sequence: active nameservers, exact owner name, duplicated domain suffix, host-required proxy mode, root versus www, then the host's binding and certificate. Keep email and unrelated records.
Open this host's connection route · All supported host routes as JSON