I have a CNAME record configured in the DNS Records panel:
Name: mail
Type: CNAME
Value: webmail-oxcs.networksolutionsemail.com.
TTL: 60
This record displays correctly in the dashboard, but querying it — even directly against your authoritative nameservers (ns1.vercel-dns.com / ns2.vercel-dns.com) — does not return the CNAME. Instead it returns A records pointing to Vercel’s own infrastructure:
dig @ns1.vercel-dns.comns1.vercel-dns.com mail.manhattanprovisionsny.com A
→ 64.29.17.65
→ 64.29.17.1
Querying for the CNAME record directly returns no answer:
dig @ns1.vercel-dns.com mail.manhattanprovisionsny.com CNAME
→ NXDOMAIN / no CNAME in answer section
As a result, any client hitting mail.manhattanprovisionsny.com (used for Network Solutions webmail login) gets routed to Vercel’s edge network and receives a 404: DEPLOYMENT_NOT_FOUND error, since no project is configured for that hostname.
What I’ve already tried:
Confirmed the record is present and correctly formatted in the DNS Records panel
Tested from incognito browser and a separate network to rule out local caching
Confirmed via direct queries to your nameservers that the override happens at the authoritative level, not a propagation delay
Question for support:
Is there a wildcard ALIAS record or CDN-level routing rule on this domain (I see a locked * ALIAS to cname.vercel-dns.com, auto-managed) that’s taking precedence over the explicit mail CNAME? If so, how do I exclude mail.manhattanprovisionsny.com from that routing so it resolves via the CNAME as configured?-- Questions that get answered the fastest are the ones with relevant info included in the original post. Be sure to include all detail needed to let others see and understand the problem! →
There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.
A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.