What causes "Vercel Domain Not Verifying (Invalid Configuration)"?

Wrong or missing A/CNAME record at the DNS provider Old records (other A records, AAAA, parking pages) conflicting Domain name typed into the record Name field (www.example.com instead of www) Domain already linked to another Vercel account or team CAA records not allowing Let's Encrypt Proxy (e.g. Cloudflare orange cloud) blocking /.well-known/acme-challenge Nameserver changes still propagating (up to 24-48 hours)

How do I fix "Vercel Domain Not Verifying (Invalid Configuration)"?

1. Copy the exact DNS values from Vercel: Open project Settings > Domains and read the record shown for your domain Apex (example.com): add the A record value shown (commonly 76.76.21.21) Subdomain (www): add the CNAME value shown, including any trailing dot Use only the prefix (www) in the Name field 2. Remove conflicting records and verify: Delete old A, AAAA and CNAME records for the same name Run dig a example.com and dig cname www.example.com Compare with the values in Settings > Domains 3. Verify a domain used by another account: If you see 'Another Vercel account is using this domain', add the TXT record Vercel shows Or transfer the domain from the other account if you have access 4. Unblock SSL issuance: If you have CAA records, add 0 issue "letsencrypt.org" With Cloudflare, set the record to DNS only (grey cloud) until the certificate is issued Remove stale _acme-challenge TXT records left by an old host

Try or Bye

Browse all analyzed products with real user feedback patterns.

Vercel Domain Not Verifying (Invalid Configuration)

Ongoing Web Updated October 21, 2026

Quick answer

'Invalid Configuration' means your DNS does not yet match what Vercel expects. Add the exact A record (apex) or CNAME (subdomain) shown in Settings > Domains, delete old conflicting records, and wait for propagation; a TXT record is needed if another Vercel account uses the domain.

Most likely fix: Copy the exact DNS values from Vercel.

Symptoms

Domain shows 'Invalid Configuration' or 'Pending Verification' in Settings > Domains, SSL certificate is not issued, or the .vercel.app URL works while the custom domain does not.

Why it happens

Wrong or missing A/CNAME record at the DNS provider
Old records (other A records, AAAA, parking pages) conflicting
Domain name typed into the record Name field (www.example.com instead of www)
Domain already linked to another Vercel account or team
CAA records not allowing Let's Encrypt
Proxy (e.g. Cloudflare orange cloud) blocking /.well-known/acme-challenge
Nameserver changes still propagating (up to 24-48 hours)

How to fix it

Try these in order — the most common fix is first.

1. Copy the exact DNS values from Vercel
1. Open project Settings > Domains and read the record shown for your domain
2. Apex (example.com): add the A record value shown (commonly 76.76.21.21)
3. Subdomain (www): add the CNAME value shown, including any trailing dot
4. Use only the prefix (www) in the Name field
2. Remove conflicting records and verify
1. Delete old A, AAAA and CNAME records for the same name
2. Run dig a example.com and dig cname www.example.com
3. Compare with the values in Settings > Domains
3. Verify a domain used by another account
1. If you see 'Another Vercel account is using this domain', add the TXT record Vercel shows
2. Or transfer the domain from the other account if you have access
4. Unblock SSL issuance
1. If you have CAA records, add 0 issue "letsencrypt.org"
2. With Cloudflare, set the record to DNS only (grey cloud) until the certificate is issued
3. Remove stale _acme-challenge TXT records left by an old host

This guide also covers

vercel domain not verifying
vercel invalid configuration domain
vercel custom domain not working
vercel dns not working
vercel domain pending verification

Still not working?

If Vercel keeps failing, you're not alone. See every Vercel problem users report or the alternatives people switch to.

Other Vercel errors