Mendlark / Guides

Custom domain not working on Vercel, Netlify or Lovable: how to fix it

You bought a domain, connected it, and now it says Invalid Configuration, shows a certificate warning, or still loads the registrar's parking page. Nearly always this is a DNS record that's missing, wrong or clashing. Here's how to sort it in order.

1. Look up what DNS actually says

Use a free checker like dnschecker.org, or in a terminal run dig yourapp.com +short and dig www.yourapp.com +short. Compare the answers with what your host's domain settings page asks for. That page tells you the exact record; trust it over old blog posts.

2. Set the root and www records correctly

  • Root (yourapp.com, host @): an A record to the IP your host shows.
  • www: a CNAME to the target your host shows (for example cname.vercel-dns.com or yoursite.netlify.app).

Add both domains in the host's dashboard and set one to redirect to the other.

3. Delete the records that clash

Registrars add default records: a parking A record, an old CNAME, or an AAAA (IPv6) record. If an old A or AAAA record sits next to the new one, some visitors get the parking page. Delete everything on @ and www except the records your host asked for.

4. Nameservers: pick one place for DNS

If you switched nameservers to your host (or to Cloudflare), records you edit at the registrar are ignored. Check with dig NS yourapp.com +short and edit DNS wherever those nameservers point.

5. SSL certificate stuck or "not secure"

The host can only issue a certificate once DNS points to it. After fixing records, wait up to an hour, then use the host's Refresh or Renew certificate button. On Cloudflare, set the proxy to DNS only (grey cloud) until the certificate is issued, then SSL mode to Full (strict). A CAA record that only allows another certificate issuer will also block it.

6. Then update the app's own settings

A new domain breaks logins that still point to the old URL. Update Supabase Site URL and Redirect URLs, Google OAuth origins, Stripe webhook and success URLs, and any hard-coded URLs in env variables.

Quick checklist

  • Root A record and www CNAME match the host's settings page
  • Old parking, AAAA and duplicate records deleted
  • Records edited where the nameservers point
  • Certificate issued (Cloudflare proxy off until then)
  • Auth, OAuth and Stripe URLs updated to the new domain

Still stuck?

Mendlark fixes this kind of problem for a fixed €49 (launch price, normally €79). We agree the problem first, test the fix and send it as a pull request, so nothing changes in your app until you merge it. If we can't fix it, you don't pay. Get the €49 fix, or start with a free scan.

Not sure what else is wrong? Paste your app link into the free instant check and get a plain-English list of problems in seconds.