Vercel nameservers serving stale GoDaddy A records

Help
,
1

Hi team,

I’m experiencing a critical DNS issue where Vercel’s authoritative nameservers are serving incorrect A records for my domain foliofox.com.

I have already:

  • removed the domain from my project
  • deleted the DNS zone from Vercel DNS
  • deleted the domain from the team-level DNS
  • switched nameservers back to GoDaddy
  • waited for delegation to fully reset
  • switched nameservers again to Vercel
  • re-added the domain to my project

Despite this full reset, Vercel’s authoritative nameservers still return A records that do not exist in my dashboard and do not point to my project.

Authoritative DNS responses (direct from ns1/ns2):

dig A foliofox.com @ns1.vercel-dns.com
→ 64.29.17.1
→ 216.198.79.65

dig A foliofox.com @ns2.vercel-dns.com
→ 64.29.17.1
→ 64.29.17.65

The dashboard zone is correct, but the authoritative servers are serving a different and clearly stale set of A records.

Request

Please purge and rebuild the authoritative DNS zone for foliofox.com inside Vercel’s internal DNS system.

Right now, the zone shown in my dashboard and the zone served by ns1/ns2 are not the same zone, which I cannot fix on my side.

Thank you!

SOLVED

Nevermind, I think it solved itself after more than 48 hours. You can close this.

1 Like
2

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.

You can also use v0 to narrow down the possibilities.

5

From the original poster:

Nevermind, I think it solved itself after more than 48 hours. You can close this.

1 Like