My site is rk-interior-construction-gurugram.netlify.app, with rkinteriorconstruction.in and www.rkinteriorconstruction.in assigned to it.
Netlify DNS is in use. The registrar has all four assigned dns1–dns4.p06.nsone.net nameservers, and public lookups return them consistently. Both hostnames resolve. I found no blocking DS, CAA, or AAAA records. Let’s Debug reports “All OK”: Let's Debug
Under Domain management → HTTPS, DNS verification was successful, but no Let’s Encrypt certificate has been issued after about two days. Could a Netlify team member check the provisioning state and retrigger it if
needed?
Update: The HTTPS status has changed from “Waiting on DNS propagation” to “We could not provision a Let’s Encrypt certificate for your custom domain.” I have attached a screenshot of the new error.
DNS verification previously succeeded. The Netlify nameservers and public records remain as described above, and Let’s Debug found no issues. Could a Netlify team member inspect the failed provisioning attempt and advise what is blocking issuance or retrigger it?
Your setup looks right, with Netlify DNS delegated with all four dns1–dns4.p06.nsone.net nameservers, both hostnames resolving, no DS/CAA/AAAA blockers, plus Let’s Debug clean.
Before providing two things to check below, wanted to let you know that if this is still failing, the best place to go is to open a support ticket. That is the only place Netlify staff can read the actual errors and clear a stuck record or a stale domain lock. It’s not something that can be resolved here.
Two things I would check, since both produce exactly this “DNS verification succeeded, certificate failed” state and neither shows up in Let’s Debug:
- Duplicate domain assignment. If
rkinteriorconstruction.in or www.rkinteriorconstruction.in is still attached to another Netlify project — including an old test site or one in a different team, issuance will keep failing. Remove it everywhere except rk-interior-construction-gurugram.
- Records inside the Netlify DNS zone. Make sure there are no leftover A or CNAME records for the apex or
www in the zone itself; they can shadow the ACME challenge. The apex should be a Netlify-managed record, with www as a CNAME to your project (or vice versa if www is your primary domain).
- Then go to Domain management → HTTPS and click Renew certificate to force a fresh attempt.
