Domain shows “Invalid Configuration” despite correct A and CNAME

Help
1

Hey everyone,

I’ve been trying to connect my custom domain fatbikezone.be (registered via GoDaddy) to my Vercel project. I followed all the official documentation, and here’s what I’ve done so far:

:white_check_mark: Current DNS Setup (checked via DNSChecker + dig):

  • A-record: @ → 76.76.21.21 (Vercel root domain IP)
  • CNAME: www → 6c3389894277e92b.vercel-dns-017.com.

No AAAA-records, no conflicting entries.

:test_tube: What I tried:

  • Waited more than 24 hours for propagation
  • Flushed DNS locally (ipconfig /flushdns)
  • Removed domain from Vercel and re-added it
  • Verified DNS using dig and online tools
  • No CAA record exists that blocks Let’s Encrypt
  • No _acme-challenge TXT record found either

:cross_mark: Problem

Despite everything being set up as documented, Vercel keeps showing “Invalid Configuration” under the domain section for both fatbikezone.be and www.fatbikezone.be. No SSL is issued either.

:information_source: Project Info:

  • Hosted on Vercel (Free Plan)
  • Static site, deployed via GitHub
  • Custom domain configured under project > settings > domains

:red_question_mark:Expected

  • Domain to show “Valid Configuration”
  • SSL certificate to be issued automatically
  • Site reachable via https://fatbikezone.be

:thinking: Any ideas what else I can try?

Would love to hear if anyone ran into a similar issue or if Vercel support needs to force something on their end. Thanks a lot in advance!

4

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

5

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!

6

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

image
image1090×1306 93.6 KB

7

Thanks for the reply!

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

CopyEdit

ns1.vercel-dns.com  
ns2.vercel-dns.com

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

makefile

CopyEdit

A: 76.76.21.21  
CNAME: 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

8

Hi, It should work now.

9

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