Fix Vercel custom-domain DNS: when this repair path applies
Match the DNS record required by the Vercel project and remove conflicting records for the same hostname. Use these steps when Vercel cannot verify or serve the custom domain, but first run the embedded diagnostic so the TLS, certificate and HTTPS evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.
Find the authoritative setting before editing
Vercel Project Settings > Domains together with the DNS provider that publishes the domain records. For Fix Vercel custom-domain DNS, confirm the active nameservers and exact service owner before changing check project domain state. A DNS-looking screen at vercel has no public effect when another provider is authoritative for the zone.
Evidence to save for Fix Vercel custom-domain DNS
Record the current public state for check project domain state, inspect apex and www DNS, remove conflicts. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.
- Check project domain state — Verify check project domain state from the public Internet and compare it with the value the responsible provider says should be live.
- Inspect apex and www DNS — Verify inspect apex and www DNS from the public Internet and compare it with the value the responsible provider says should be live.
- Remove conflicts — Verify remove conflicts from the public Internet and compare it with the value the responsible provider says should be live.
- Wait for validation and certificate provisioning — Test the hostname actually requested, its certificate dates and SAN coverage, and the TLS handshake. Root and www can serve different certificates.
Repair steps in vercel
Match the DNS record required by the Vercel project and remove conflicting records for the same hostname.
- 1. Check project domain state. After this step, check the public value tied to check project domain state before changing another unrelated setting.
- 2. Inspect apex and www DNS. After this step, check the public value tied to inspect apex and www dns before changing another unrelated setting.
- 3. Remove conflicts. After this step, check the public value tied to remove conflicts before changing another unrelated setting.
- 4. Wait for validation and certificate provisioning. After this step, check the public value tied to wait for validation and certificate provisioning before changing another unrelated setting.
Why this order matters for vercel
The sequence begins with the provider/authority decision, then moves through check project domain state, inspect apex and www DNS, remove conflicts. That keeps the change scoped to the failed TLS, certificate and HTTPS path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.
Verify Fix Vercel custom-domain DNS
HTTPS should complete for the exact hostname, the certificate should be valid for that hostname, and root/www should follow the intended canonical redirect without a TLS error. Compare the same check project domain state and inspect apex and www DNS evidence used before the change; a repair is complete when the public result agrees, not merely when the vercel interface reports that a save succeeded.
If vercel and the public result disagree
Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting check project domain state value to force validation.
Mistakes to avoid for this repair
Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Fix Vercel custom-domain DNS should change only the settings required by this diagnosis.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.