When adding an existing domain, I used to be able to expand the “Invalid Configuration” message and click a link to automatically add the new CNAME to my Cloudflare DNS. When I clicked the link, it took me to a confirmation page on Cloudflare’s site. After confirming, it returned to the project domains setting page.
Now there are only manual instructions.
It seems this was “Domain Connect,” but it no longer works. When I add a new domain, I now see errors in the dev console:
GET https://vercel.com/api/front-domains/domain-connect/status?domain=test-cf2.leftium.com 400 (Bad Request)
Ignored request error CustomFetchError: Unexpected response: text/plain Domain connect record not found
Apparently this is because this command no longer returns a response
dig TXT _domainconnect.test-cf2.leftium.com +short
There is a response for the parent domain:
dig TXT _domainconnect.leftium.com +short
"api.cloudflare.com/client/v4/dns/domainconnect"
The Domain Connect spec says providers should fall back to the parent domain when a subdomain lookup fails, but Vercel appears not to be doing that fallback for subdomains
Did Vercel use to fall back to the parent domain? I was unable to figure out how to configure Cloudflare to return the _domainconnect record for a CNAME that doesn’t exist yet.
The workaround is to manually add the CNAME at Cloudflare, but it would be nice to be able to automatically add the records, again.