Custom domain stuck on "doesn't appear to be served by Netlify" - DNS verified correct, no obvious config issue

Hi, I’m trying to connect my custom domain (leohealth.co) to my Netlify project (incandescent-palmier-82c2c7.netlify.app) using external DNS at Dynadot, but DNS verification keeps failing with “leohealth.co doesn’t appear to be served by Netlify.”

DNS is correctly configured and fully propagated:

  • A record: leohealth.co75.2.60.5

  • CNAME: www.leohealth.coincandescent-palmier-82c2c7.netlify.app

  • Nameservers: Dynadot defaults (ns1.dyna-ns.net, ns2.dyna-ns.net)

dig from Google (8.8.8.8), Cloudflare (1.1.1.1), and Dynadot’s authoritative nameservers all return the correct records. dnschecker.org confirms global propagation. The Netlify project is live and serving content correctly at incandescent-palmier-82c2c7.netlify.app.

Things I’ve tried:

  • Initially set up Netlify DNS for leohealth.co, then deleted that DNS zone to switch to external DNS

  • Removed and re-added both leohealth.co and www.leohealth.co to the project

  • Confirmed there is no current Netlify DNS zone for leohealth.co at the team level

  • Clicked “Verify DNS configuration” multiple times over several hours

I’d prefer to keep DNS at my registrar (Dynadot) rather than switch to Netlify DNS. Could there be a stale backend state blocking verification / any advice overall?

Thanks!

Hey @nikis :wave:,
Thanks for reaching out!

We’ve gone ahead and created a support ticket for you, so our team can follow up with you directly via email from the help desk. Our Support crew will be in touch with you by email soon.

Great news: these days anyone can reach out to Netlify Support. First, you can try getting an answer using Ask Netlify, our helpful AI search tool. If your question isn’t answered there, you can submit a ticket using the support form, and we’ll take it from there.

We’re keeping the community around for swapping ideas, sharing tips and tricks, and talking shop with other folks building on the platform — but for support issues, tickets are the way to go.

Thanks for being here, and keep an eye out for that email from us!