Description
Ensure every domain on the team's projects has DNS records that point correctly to Vercel, using the exact A or CNAME values shown in the project's Domains settings, or Vercel's nameservers. Domains should show Valid Configuration, and old or conflicting DNS records should be removed.
Rationale
Wrong or outdated DNS records can send users to an old server, cause outages, or block SSL certificate creation. Dangling records that point to services no longer in use can also be taken over by attackers. Keeping DNS records correct makes sure users always reach the right deployment securely.
Impact
Domains serve the correct project
Allows SSL certificates to be issued and renewed
Removes dangling records that could be taken over
Default Value
When a domain is added, Vercel shows the required A or CNAME records. The domain shows Invalid Configuration until the DNS records are set correctly.
Pre-Requisites
Team Owner or Member role, or Project Administrator
Access to the domain's DNS provider
Test Plan
Sign in to Vercel at https://vercel.com.
Select your team from the team switcher.
Select the project from the dashboard.
Open Settings in the sidebar and select Domains.
Check that each domain shows Valid Configuration.
Optionally, run dig <domain> in a terminal to confirm the records match the values Vercel shows.
If any domain shows Invalid Configuration, follow the implementation steps.
Implementation Steps
Sign in to Vercel at https://vercel.com.
Select your team from the team switcher.
Select the project from the dashboard.
Open Settings in the sidebar and select Domains.
Open the domain showing Invalid Configuration and note the required A or CNAME value.
Update the record at your DNS provider and remove any old or conflicting records.
Return to Domains, refresh the domain status, and confirm Valid Configuration.
Backout Plan
Restore the previous DNS records at your DNS provider.
Reference