Site name: stunning-taffy-84fa1a.netlify.app
Custom domains: mobilorent.co.kr (primary) + www.mobilorent.co.kr
DNS type: Netlify DNS
Registrar: Cafe24 (Korea) — nameservers changed to dns1-4.p02.nsone.net on Sept 17, 2026
Problem:
The HTTPS panel now shows “DNS verification was successful” and offers the
“Provision certificate” button. But clicking it immediately fails with:
“We could not provision a Let’s Encrypt certificate for your custom domain”
and the panel reverts to the “Verify DNS configuration” state.
So DNS verification passes, but the actual certificate issuance step fails.
This has been happening for 4 days.
Everything on my side checks out:
- Let’s Debug (https://letsdebug.net), http-01 method:
mobilorent.co.kr → All OK, no issues found
www.mobilorent.co.kr → All OK, no issues found - Domain management lists ONLY mobilorent.co.kr and www.mobilorent.co.kr,
both marked “Netlify DNS” with a green check. No extra domain aliases. - Public DNS (Google Public DNS, verified 2026-09-21):
NS delegation at the .kr registry: dns1-4.p02.nsone.net (correct)
mobilorent.co.kr A → 18.208.88.157, 98.84.224.111
www.mobilorent.co.kr A → 18.208.88.157, 98.84.224.111
stunning-taffy-84fa1a.netlify.app A → 18.208.88.157, 98.84.224.111
(identical, so both apex and www point to this site)
No CAA record, no AAAA records, no DS record (DNSSEC is not enabled) - https://mobilorent.co.kr currently serves the shared *.netlify.app
certificate (hostname mismatch), i.e. no certificate has ever been issued.
One thing that looks odd: the authoritative SOA for the zone returns
“dns1.p01.nsone.net. domains+netlify.netlify.com.” while the NS delegation
points to the p02 pool. Is there a duplicate or stale Netlify DNS zone for
this domain on your side?
Also, I have retried many times over the past days, so the Let’s Encrypt
failed-validation rate limit may now be in effect for this hostname.
Could you please inspect the zone and reset the certificate provisioning?
Thank you.