Hi Vercel team,
Two custom domains on my project dichevre-web are stuck on “Invalid Configuration”:
pre.dichevre.com(Preview/develop branch)www.dichevre.com(Production)dichevre.comapex (redirects to www)
DNS configuration is correct per Vercel’s instructions:
CNAME pre → 56febd3bb9ae2059.vercel-dns-017.com. (Cloudflare, Proxy disabled)
CNAME www → 56febd3bb9ae2059.vercel-dns-017.com. (Cloudflare, Proxy disabled)
A dichevre.com → 76.76.21.21 (old apex IP, currently set)
TXT _vercel records present for all three.
Verification via dig confirms correct resolution:
- www.dichevre.com → 56febd3bb9ae2059.vercel-dns-017.com → 216.150.1.129, 216.150.16.129
- pre.dichevre.com → 56febd3bb9ae2059.vercel-dns-017.com → 216.150.16.193, 216.150.1.193
Vercel UI shows “Remove the following conflicting DNS records” listing the same IPs that the CNAME resolves to internally (216.150.x.x), which are NOT records in my DNS provider — they appear to be the resolved targets of the vercel-dns-017.com CNAME.
I’ve already tried:
- Removing and re-adding the domains in Vercel (didn’t fix)
- Waiting 30+ minutes for propagation (no change)
- Verifying no conflicting A records exist in Cloudflare (confirmed clean)
Could you please force a server-side refresh of the domain verification? This appears similar to the case resolved by Amy Egan in DNS Change Required
Thanks!