Verification for two separate subdomains in two separate vercel accounts

Help
1

Hello, I am working on helping two separate subdivisions of my organization configure vercel applications on subdomains of our root domain.

Currently we have:

sub-a.our-root-domain.com configured with a vercel account, and have a corresponding TXT record with valuevc-domain-verify=sub-a.our-root-domain.com. It is working properly.

We want to set up a separate sub-b.our-root-domain.com to another vercel account, managed by another team. However, when we go to add this domain, it promps us to verify our root domain instead of this subdomain. It is asking us to create a TXT record with a value vc-domain-verify=our-root-domain.com.

This domain is registered with another Vercel account. Verify DNS ownership to claim it.
Add the following TXT record to your DNS configuration for our-root-domain.com, then click “Verify & Claim” to complete the ownership transfer.

Why is it asking us to verify the root domain instead of the subdomain?

To clarify, I have no problem making a TXT record on _vercel.our-root-domain.com here. But I do not want to validate our entire apex domain and give permissions for it to this account–this account should only operate on the subdomain.

Is there a way to have two separate subdomains verified on two separate vercel accounts, without giving one “ownership” of the apex domain?

2

The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points.

You can also use v0 to narrow down the possibilities.

3

Unfortunately I have searched the forums and read the troubleshooting guide, and most of the issues people seem to have are with not having ability to edit the root DNS zone. I don’t have this problem, but a separate one.

4

It asks you to verify the root to make sure you have control of the domain. It’s to prevent someone from using a domain or subdomain they don’t actually own