Vercel DNS returns wrong IP and SSL fails for sacredkriti.com

My domain sacredkriti.com uses Vercel nameservers (ns1.vercel-dns.com and ns2.vercel-dns.com), is assigned to my sacred-kriti project, shows “Valid Configuration,” and has valid managed SSL certificates.

However, both authoritative Vercel nameservers return 18.204.152.241 for sacredkriti.com and www.sacredkriti.com. That address serves a Heroku/Express 204 response over HTTP, and HTTPS fails during the TLS handshake with “tlsv1 alert protocol version.”

The locked Vercel ALIAS records in the dashboard point to vercel-dns-017.com targets. I also added an explicit apex A record for 76.76.21.21, but it is visible only in the dashboard and is not being published by either authoritative Vercel nameserver.

Please refresh or rebuild the domain’s DNS zone/ALIAS flattening and edge SSL routing.

If you're having trouble deploying an Express app, this guide can help.

https://vercel.com/guides/using-express-with-vercel

You can also ask v0 for suggestions tailored to your own project setup.

This is not an Express application or an Express deployment issue. My project is a React/Vite static site hosted on Vercel.

The Express/Heroku response is coming from the incorrect IP address (18.204.152.241) currently returned by Vercel’s authoritative DNS servers. That response is evidence of the DNS routing problem, not part of my application.

Could a Vercel team member please inspect the DNS zone and managed ALIAS/SSL routing for sacredkriti.com?

Following up after 24 hours: this issue is still active. Both Vercel authoritative nameservers continue to return 18.204.152.241, and HTTPS still fails.

This appears identical to this recent report: https://community.vercel.com/t/my-production-custom-domain-is-stuck-on-an-obsolete-heroku-ip/48009

Vercel Community

My production custom domain is stuck on an obsolete Heroku IP

My production custom domain is stuck on an obsolete Heroku IP even though the Vercel deployment and dashboard configuration are correct. Domain:...

The explicit A record is visible in my Vercel dashboard but is still not being published. , could this please be escalated to the domains/DNS team?