Vercel treats .v.ua domains as subdomains instead of public suffixes

Help
1

Hi everyone,

I’ve noticed a possible issue with how Vercel handles domains in the .v.ua zone.

When trying to add a domain like example.v.ua, the system seems to treat it as a subdomain of v.ua instead of recognizing it as its own domain.

However, v.ua is actually a public second-level domain zone under .ua, similar to zones like .com.ua, .org.ua, etc. Domains such as:

  • example.v.ua
  • site.v.ua

are independent domains registered within the v.ua zone, not subdomains of a single root domain.

Because of this behavior, it becomes difficult to properly verify or configure such domains in Vercel, since the platform assumes v.ua itself is the main domain rather than a domain zone.

Has anyone else encountered this issue? And is there a recommended workaround?

It would be great if Vercel could treat domains ending in .v.ua as full domains rather than subdomains, so they can be connected to projects without problems.

Thanks!

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.