Newb here - SSL cert provisioning stuck with 'bad dns' but DNS is fully verified healthy"

Support
1

Ticket #1050195

Site: coolbrookfitness
Domain: coolbrookfitness.com
Plan: Pro
Setup: Netlify DNS (nameservers transferred from GoDaddy ~24 hrs ago)

SSL cert provisioning fails with “bad dns for custom domain.” However, every external check confirms DNS is healthy:

  • Both coolbrookfitness.com and www.coolbrookfitness.com show “Netlify DNS” with green checks in Domain Management
  • DNS records inside Netlify: clean NETLIFY aliases for root + www → coolbrookfitness.netlify.app
  • dig returns valid Netlify nameservers + correct A records (52.x, 13.x)
  • dnschecker.org confirms propagation worldwide
  • http://coolbrookfitness.com returns 200 OK from Netlify
  • letsdebug.net confirms “All OK” for HTTP-01 challenge — Let’s Encrypt would issue the cert if asked
  • No AAAA records, no CAA records, no DNSSEC

Per Netlify docs, “if not provisioned within 24 hours, DNS misconfiguration likely exists” — but DNS is verifiably correct externally. This looks like internal Netlify validation state.

Opened a support ticket via email yesterday — no response yet. Been over 24 hours

Site is HTTPS-down for ~24 hrs; browser warnings (“attackers may be trying to steal your information”) are blocking real users.

Could a staff member check the backend cert state and manually re-issue please?