My domain still goes to Vercel after removing from account

Help
1

I removed talesofmurder.com from all Vercel projects and deleted it from my account’s domain dashboard over 7 days ago.

My DNS is fully correct:

  • talesofmurder.com → 76.76.21.21
  • www.talesofmurder.com → sites.ludicrous.cloud

But I’m still seeing this error from Vercel’s CDN:

makefile

CopyEdit

404: DEPLOYMENT_NOT_FOUND  
Code: NOT_FOUND
  • The domain is not attached to any Vercel project.
  • The domain is deleted from the dashboard.
  • I no longer use Vercel at all.

I’ve verified DNS via dig, dnschecker.org, and other tools.

There is no support option unless I pay. There is no purge tool. The “community” login system blocked me for days.

This has broken my production domain for over a week. I have no way to purge Vercel’s edge cache or stop your CDN from hijacking traffic to my domain.

I need a human to purge talesofmurder.com from Vercel’s edge system immediately.

This is not a browser cache issue — this is Vercel’s CDN still intercepting traffic after total removal.

Please escalate or forward this to someone who can manually release the domain from your system.

2

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.

4

The problem is … I DON’T WANT VERCEL IN THE LOOP. I AM TRYING TO POINT THAT URL TO A DIFFERENT PLACE BUT VERCEL IS HIJACKING IT.

5

You need to change the A record to direct talesofmurder.com to wherever you’re hosting the new site. The current value 76.76.21.21 sends visitors to Vercel, the system tries to locate the project and can’t find one using that domain, then you see the 404 DEPLOYMENT_NOT_FOUND error

CleanShot 2025-07-29 at 19.51.22
CleanShot 2025-07-29 at 19.51.22781×318 14.4 KB

The A record needs to be something other than 76.76.21.21 if you’d like it to point somewhere other than Vercel. I hope that makes sense!

6

I’m so sorry. I’m a gibbering idiot. I could have sworn that was to my new deployment host not vercel. I should’ve double checked then verified instead of assuming.

I’m so sorry. I’ll delete this issue.

Rich

7

No worries! This isn’t the first time DNS has caused frustration, and it won’t be the last :smile:

I’m glad there was an easy solution this time

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.