system If you're having trouble deploying an Express app, this guide can help. vercel.com/guides/using-express-with-vercel You can also ask v0 for suggestions tailored to your own project setup.
Archkish79 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?
Archkish79 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: community.vercel.com/t/my-production-custom-domain-is-stuck-on-an-obsolete-heroku-ip/48009 The explicit A record is visible in my Vercel dashboard but is still not being published. @amyegan, could this please be escalated to the domains/DNS team?
Amy Egan It looks like you got it working. Both URLs seem to go to the same site at the moment. Do you still need help with this?
Eldargvideo 8087 Vercel’s managed apex ALIAS is serving a stale flatten. Your proof that hitting 216.198.79.1 / 64.29.17.1 serves the right deploy is the diagnosis. Put explicit A records to those two IPs at the registrar (keep MX/TXT), or move DNS off Vercel nameservers and CNAME www + ALIAS apex to cname.vercel-dns.com.
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Tools 9165 My custom domain bhc.itwos.co.site shows an error stating it's "linked to another Vercel account." I've confirmed via direct DNS lookup (nslookup -type=TXT) that the required TXT verification record is correctly live and has the correct value, and this has been the case for over 24 hours. Can anyone tell me what account this might be conflicting with, or how to get this manually cleared/released?
Tools 9165 support in something that can help me solve the issue with been a couple of days. I’ve been trying to get this done.
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Jacob Paris I can confirm dpdns is on the official Public Suffix List, I'll check with our domains team to see if we can get our internal list updated to include it
Amy Egan Did you buy the domain from a different account? I don't see the domain purchase associated with the account you're using here. I see that it is using Vercel nameservers but is not currently assigned to a Vercel project.
Reyesmtz69 8391 Hi Amy, yes, I understand what you’re seeing now. I purchased solarshieldllc.com directly through Vercel on August 23, 2026 for $11.25, but it may have been purchased under a different Vercel account than the one I’m currently using. I have the Vercel receipt showing the purchase. My goal is to get the domain associated with the Vercel account/project I’m using now. Can you please help me determine which Vercel account currently owns the domain and what I need to do to transfer/associate it with my current account and project?
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Abrahamhpalma Update: I also ran the HTTP-01 validation test for www.cozumelopina.mx using Let's Debug, as recommended in Vercel's domain troubleshooting documentation. The result is “All OK! — No issues were found with www.cozumelopina.mx.” I also verified that an HTTP request to /.well-known/acme-challenge/test reaches Vercel successfully (Server: Vercel), and there are no restrictive CAA records or stale _acme-challenge DNS records. At this point DNS and HTTP-01 validation appear to be working correctly, but Vercel continues showing the previous “Failed To Generate Cert” / NXDOMAIN error. Could the certi
Abrahamhpalma UPDATE — SOLVED ✅ I’m posting the final solution in case someone else runs into the same issue. In our case, the original “Failed To Generate Cert” error was caused by inconsistent DNS responses from our DNS provider’s authoritative nameservers. Some nameservers returned the correct CNAME for www, while others returned NXDOMAIN. Our DNS provider eventually corrected the authoritative DNS issue. After that, we verified that: www.cozumelopina.mx resolved publicly to the correct Vercel CNAME. Google Public DNS (8.8.8.8) resolved it correctly. An HTTP request to /.well-known/acme-challenge/test su
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Amy Egan You should have an option to "Restore Original Nameservers" on the domain management page. Sharing docs for outline of exact steps: vercel.com/docs/domains/managing-nameservers#restore-original-nameservers What do you see in the nameservers section for your domain?
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Lauraborgenicht Dotcom @moderators Could you please delete this entire topic? It's my own post but it publicly ties my production domain to SSL details I'd rather not have indexed, and I'm past the window to edit or delete it myself. Much appreciated.
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Ryu Hi Sergio, The key clue is that sergiomjsp.com and www.sergiomjsp.com are resolving to different places. A redirect from the root domain to www only helps after the browser reaches Vercel, so it will not fix ERR_SSL_PROTOCOL_ERROR if your affected network is still resolving the root domain to the wrong IP. I’d compare the authoritative Vercel DNS answer with public DNS and the resolver on the affected network: If the Vercel nameservers return the expected Vercel edge values but your home Wi-Fi/router still returns 18.204.152.241, then this is probably stale or rewritten DNS on that network, no