Multiple domains stuck on Invalid configuration despite correct DNS settings

Help
,
1

I’m having trouble getting multiple domains to verify in Vercel and would appreciate a check from your side.

Domains:

  • trvl8r.com
  • www.trvl8r.com
  • wolfkrowit.com
  • www.wolfkrowit.com

DNS provider: Afrihost
Project(s): Production deployment(s)

Current DNS Configuration

This configuration has been unchanged and stable for approximately 48 hours.

trvl8r.com

Apex (trvl8r.com)

  • A record → 216.198.79.1

www.trvl8r.com

  • CNAME → 7a11ac745c460906.vercel-dns-017.com

wolfkrowit.com

Apex (wolfkrowit.com)

  • A record → 216.198.79.1

www.wolfkrowit.com

  • CNAME → 78ca2e50b666b4d8.vercel-dns-017.com

For both domains there are:

  • no additional A records at the apex
  • no A records at www
  • no wildcard records
  • no AAAA records

Email-related records (MX / TXT for SPF, DKIM, DMARC) are present where applicable but unchanged and should not affect domain verification.

What I’ve Already Checked / Tried

  • DNS values exactly match what Vercel currently recommends
  • DNS has been stable for ~48 hours
  • Public DNS checkers resolve the correct A and CNAME records
  • Removed and re-added the domains in Vercel
  • Reconfirmed the CNAME values (no typos)
  • Connected apex and www hosts directly to the production deployment(s) (no redirects enforced yet)

All of the above domains still show this error in the Vercel dashboard:

Error: Invalid configuration

Additional Context

I also went through the Vercel AI support flow, which indicated that there is no issue with the DNS configuration and recommended opening a support ticket for further investigation.

At this point, it looks like the DNS itself is correct, but Vercel may not be seeing the updated records during validation.

If possible, could you please:

  1. Re-run domain verification for the above domains, or
  2. Check whether cached or stale DNS results are being used during validation?

Happy to provide any additional information if needed.

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.

7

I found the issue. one of the NS used was proper flaky, spewing all sorts of errors on a DNSviz analysis, so I just removed it and boom! instant validation :slight_smile:

8

Thanks for coming back to share what worked for you and building out our community base :slightly_smiling_face: