Hi, It looks like the DNS hasn't propagated yet which is the reason you are seeing invalid config error:

• https://dnschecker.org/#A/fatbikezone.be
• https://dnschecker.org/#CNAME/www.fatbikezone.be

Hi Swarnava,

Thanks for the response!

I've already verified that the DNS records have fully propagated globally using multiple tools (including dnschecker.org) and dig. Both the A-record and CNAME are pointing correctly:

• A @ → 76.76.21.21
• CNAME www → cname.vercel-dns.com

There are no AAAA, CAA, or conflicting records. I’ve also tried:

• Flushing local DNS (ipconfig /flushdns)
• Removing and re-adding the domain to Vercel
• Waiting over 24 hours
• Checking DNS from multiple global locations

Despite this, I’m still getting “Invalid Configuration” in the Vercel dashboard, and the SSL certificate isn’t being issued.

Is it possible there’s a caching issue on Vercel’s end or that something needs to be manually triggered? I’d appreciate it if you could take a closer look.

Thanks again for your help!

Are you checking against domain fatbikezone.be ? I still see it hasn't propagated yet:

Thanks for the reply!

Just to clarify — it's been well over 48 hours since I updated the nameservers at GoDaddy to:

CopyEdit

1ns1.vercel-dns.com  2ns2.vercel-dns.com

I also confirmed via DNS Checker that both fatbikezone.be and www.fatbikezone.be resolve to:

makefile

CopyEdit

1A: 76.76.21.21  2CNAME: 6c3389894277e92b.vercel-dns-017.com

There are no conflicting A or AAAA records anymore, and I’ve flushed my DNS and re-added the domain in Vercel just to be sure. Yet, Vercel still reports “Invalid Configuration” and hasn’t issued the SSL certificate.

Is there anything else I can do to trigger the validation? Or could this require a manual refresh on your end?

Thanks in advance for looking into it

Hi, It should work now.