Domain Still Resolving to Vercel After Deletion and DNS Change

Hello Vercel Support Team,

I am writing to request your help with a persistent DNS issue for my domain, rapdisc.com .

The Problem: My domain, rapdisc.com (and its subdomain streamer.rapdisc.com ), is still resolving to a Vercel “404: DEPLOYMENT_NOT_FOUND” error page, even though I have completely migrated away from your platform.

What I Have Already Done:

  1. I have deleted the associated project for rapdisc.com from my Vercel dashboard several days ago.
  2. I have updated the DNS records at my domain registrar (GoDaddy) to point to my new server. The A record for rapdisc.com now correctly points to my new IP address: 144.91.121.209 .
  3. I have confirmed via external tools like dnschecker.org that the new A record has propagated globally. The world sees the correct IP address.
  4. I have cleared all local and browser caches on my end.

Despite all these steps, traffic to my domain is still being intercepted and routed to your servers, resulting in the 404 error. This indicates that the domain is still tied to your platform in some way, likely due to a persistent caching or configuration issue on your end.

My Request: Could you please investigate and completely purge and release the domain rapdisc.com from all your systems? This includes any internal routing rules, DNS caches, or platform configurations that may still be associated with it.

Thank you for your time and assistance in resolving this critical issue.

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.

1 Like

I’m experiencing the same issue.

1 Like

Same here.

What is the solution to this. How can we reach Vercel support, without paying for a plan?!

I am frustrated.

I could solve it by deleting the DNS Zone of my domain in the Vercel settings (see screenshot).

Also I needed to setup the A and CNAME Records correctly in the DNS settings of my domain provider, so that they don’t point to Vercel anymore, but to the server of my new deployment.