I need help resolving a stuck custom-domain/certificate state for Netlify project `splendorous-douhua-d9942a`.
Current Netlify domain state:
- `shewhospeaksspirit.org`: Primary domain; pending DNS verification. This legacy domain is intentionally not served by Netlify and its external DNS must not be changed.
- `www.shewhospeaksspirit.org`: Redirect binding; pending DNS verification.
- `shewhospeaksspirit.com` and `www.shewhospeaksspirit.com`: Domain aliases. Their public DNS is correctly routed to Netlify.
The approved desired change is to make `shewhospeaksspirit.com` the primary domain, remove only the two `.org` bindings from this Netlify project, and issue automatic certificates for the .com apex and www.
Public DNS and routing evidence:
- `shewhospeaksspirit.com` resolves to `A 75.2.60.5` and returns the deployed Netlify site over HTTP with `200 OK`.
- `www.shewhospeaksspirit.com` resolves by `CNAME splendorous-douhua-d9942a.netlify.app` and also returns the deployed Netlify site over HTTP with `200 OK`.
- Strict HTTPS fails for both .com names because the served certificate has no matching subject alternative name.
The domain-management page reports **DNS verification failed** specifically because `shewhospeaksspirit.org` is not served by Netlify. When I select **Set as primary domain** for `shewhospeaksspirit.com`, Netlify accepts the action but enters a certificate-provisioning lock: “We’re provisioning a certificate for your site, you cannot change custom domains until that process completes.” After the job settles, `.org` is still primary and the same .org DNS-verification error returns. This has been retried after waiting with the same result.
Could Netlify please clear the stuck certificate job or otherwise make `shewhospeaksspirit.com` the primary domain, remove only `shewhospeaksspirit.org` and `www.shewhospeaksspirit.org` from project `splendorous-douhua-d9942a`, and trigger automatic TLS issuance for the .com apex and www names?
Please do **not** change external `.org` DNS. No account credentials, DNS-zone secrets, or unrelated site details are included or needed.