Subdomain verification: rmec.tech.com is blocked due to domain ownership

Support
1

Hi Netlify Support,

I’m trying to use the subdomain rmec.tech.com with my Netlify site (strong-duckanoo-1a1467), but I get the message:

“tech.com or one of its subdomains is already managed by Netlify DNS on another team.”

I do not own tech.com, but I do control rmec.tech.com via IONOS and have added a TXT record to prove ownership:

  • Subdomain: rmec.tech.com
  • TXT Value: netlify-verification=rmec-verified-by-owner

Could you please verify ownership manually and allow me to connect the subdomain?

Thank you!

URL netlify: strong-duckanoo-1a1467.netlify.app

2

Hi Heather,

I have added the requested TXT record to verify ownership of the subdomain rmec.tech.com. Below are the details:

  • Subdomain: rmec.tech.com
  • TXT Record Value: netlify-verification=rmec-verified-by-owner (replace with actual value if needed)

Could you please proceed with removing the link between rmec.tech.com and the other Netlify account so I can connect it to my site?

Thank you for your help!

Best regards

3

Hi Angelica,

Thanks for your response.

I want to clarify that I do not own the root domain tech.com, and I cannot access it. However, I do have full control over the subdomain rmec.tech.com via DNS configuration on IONOS.

According to Netlify’s own guidance and previous support resolutions, verifying control of a subdomain via a TXT record should be sufficient to allow me to connect just that subdomain — not the root domain.

I have already created the TXT record as requested:

  • Subdomain: rmec.tech.com
  • TXT Record: netlify-verification=rmec-verified-by-owner

I kindly ask that you verify the TXT record at the subdomain level and allow me to connect rmec.tech.com to my Netlify site. I understand I won’t be able to manage the full domain, and that is fine.

Please let me know if you are able to proceed with subdomain-level verification.

Best regards

4

We’ve followed up regarding this issue via email, please continue to respond in that thread.