Current Behavior:
The wildcard domain *.unify-conference.store is showing a persistent “Invalid Configuration” error in our project’s domain settings.
This status has not changed for over 24 hours.
Any attempt to access a subdomain (e.g., test.unify-conference.store) fails to resolve to our Vercel deployment.
Expected Behavior:
The wildcard domain *.unify-conference.store should show a “Valid Configuration” status.
Any subdomain should successfully serve our production deployment without a redirect.
We have followed the standard procedure for setting up a custom domain with Vercel nameservers, but the wildcard portion is failing to validate.
Nameserver Configuration: We changed the nameservers for unify-conference.store at our domain registrar to ns1.vercel-dns.com and ns2.vercel-dns.com.
DNS Propagation Confirmation: We have used public DNS tools (like dnschecker.org) to verify that the NS records have fully propagated globally and are correctly pointing to Vercel.
Registrar Settings Confirmation: We have also confirmed that DNSSEC is disabled at our domain registrar.
Vercel Project Configuration: We added unify-conference.store, www.unify-conference.store, and *.unify-conference.store to our project. The root and www domains validated successfully, but the wildcard domain did not.
Troubleshooting Attempt 1: We waited over 24 hours for propagation, with no change in status.
Troubleshooting Attempt 2: We confirmed the Vercel DNS dashboard has a default, locked * ALIAS record. We tried adding an overriding * A record pointing to 76.76.21.21, but this did not fix the validation error. We have since removed this A record to prevent conflicts.
Troubleshooting Attempt 3: We have tried removing the *.unify-conference.store domain from the project and re-adding it, but the “Invalid Configuration” error persists.
Project URL: https://unify-conference-frontend.vercel.app
Custom Domain: unify-conference.store
Framework: React, Vite
Environment: Production
Project Settings: Using Vercel DNS via Vercel Nameservers.