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.
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 I’ve tried that already it isn’t helping would someone please answer my question
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?
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
Nathaniel72 Update: I ran Let's Debug (letsdebug.net) against nhlacrosse.com using their HTTP-01 API — result: {"ok":true}, no issues found. This confirms Let's Encrypt's ACME validation path works completely fine for this domain, which rules out DNS/certificate issuance as the cause (I understand Vercel's edge intercepts /.well-known/acme-challenge/* requests through a separate path from normal site routing, and that path is healthy). This means the problem is isolated specifically to Vercel's normal HTTPS/HTTP request routing for this domain — not DNS, not the certificate, not ACME validation. The domai
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
Ryu Hi Bahadurkhan10, Since the .vercel.app URL works from the affected network, I’d separate the app/deployment from the custom-domain network path. For www.nexorasystems.xyz, the apex A record is not the main thing being used. The important record is the www CNAME, and it should match the exact value shown in Vercel’s domain settings. I’d ask your friend in Michigan to run these from the affected network: If the .vercel.app URL connects but the custom domain times out, that points away from your app code and more toward DNS resolution, ISP routing, or the specific Vercel edge path used by the cu
BRIAN APEXCORE Adding another data point since this looks like the same class of bug: same symptom for us (apexcore.academy, project apex-dashboard, team apexcore1) — vercel.app works, custom domain resets during TLS handshake. In our case it is 100 percent reproducible as region-specific: every US connection fails, every Mexico connection succeeds, including a real student who used the site normally from there. We also reproduced the identical failure on a second, brand new domain pointed at the same project, so it is not a per-domain DNS misconfiguration, it looks like something at the project/edge level.
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
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
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
Ryu Hi Ale, If TLS currently fails because no certificate is presented, I’d treat that as a symptom of the cert not being issued yet, not the root cause. The thing to debug is why Vercel’s certificate validation cannot complete. For a normal non-wildcard subdomain, I’d check these from a terminal: What I’d look for: CNAME should match the exact vercel-dns-017.com target shown in the Vercel domain card. There should not also be stray A or AAAA records for the same subdomain. If CAA records exist, they need to allow Let’s Encrypt, since that is what Vercel uses for managed certs. The HTTP challenge
Ale Hey Ryu! Sorry for the late reply! 😓 Many thanks for yoy reply, in the end I managed. 🙏 Thanks for your support and also thanks for sharing your knowledge.
Amy Egan I found your case and confirmed it's assigned to the right team. They have access to specialized tools to help with account verification and recovery. It's better to use the account recovery form rather than email to ensure the team has all of the info they need to solve your case as quickly as possible. However, there is no need to open a new case now since you already have one open. Thanks for your patience while the support team works through cases that were opened before yours Note: I redacted some info from your original post to keep your account safe as these posts are public
Amy Egan Following up to confirm you're able to access your account now. It looks like the support team solved your case a couple of days after my last message, but please let me know if you're still having any trouble with it
system Hi there! I'm just a bot here to share some info that might help you before a human arrives. If your account is eligible, you can use our new self-service recovery flow: Go to vercel.com/login Choose to sign in using the email + one-time password (OTP) option. Select Use another sign-in method Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account Follow the remaining prompts to complete the recovery process If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yo