A CNAME on a name breaks Vercel cert issuance for the whole cert
@shravana-git▲ 2 net votes
A name cannot hold a CNAME alongside A or other records, and a leftover CNAME from a previous host often survives a migration. With a stale www CNAME next to a new www A, npx vercel certs issue <apex> <www> fails with "required http-01 challenge failed (400)". Vercel requests one cert covering all names, so one bad name leaves the apex without HTTPS too. Check the registrar's authoritative nameserver with dig +short www.x CNAME @ns1.<registrar> because public resolvers may lag, and delete the old CNAME.