Project: kbeautygem-starsearch (site name showing as “idolive.ai”)
I’m trying to add starsearch.idolive.ai as the domain for this project. My root domain idolive.ai is managed elsewhere (DNS hosted outside Netlify) and is not meant to be part of this project at all — only the starsearch subdomain should point here.
Steps taken: added a CNAME for starsearch.idolive.ai pointing to kbeautygem-starsearch.netlify.app (confirmed resolving correctly via public DNS lookup). Added starsearch.idolive.ai as a domain alias in this project and set it as primary.
The problem: every time I do this, Netlify automatically reattaches the apex idolive.ai (and www.idolive.ai) as the project’s primary domain alongside it. Since idolive.ai’s real DNS doesn’t point to Netlify, that apex domain can never validate, and the bundled Let’s Encrypt certificate fails project-wide (“We could not provision a Let’s Encrypt certificate for your custom domain”). Visiting starsearch.idolive.ai on mobile confirms this with the Chrome error code ERR_CERT_COMMON_NAME_INVALID (a genuine certificate mismatch, not a caching issue).
This looks like the same issue described here: Smashr.dk stuck - "already managed by Netlify DNS on another team — idolive.ai appears to already be claimed as a Netlify DNS zone from an earlier, unrelated setup, forcing the auto-reattachment.
Could someone manually release idolive.ai from whatever zone/team it’s claimed under, so only starsearch.idolive.ai is registered to this project with its own clean certificate?
Thanks!