Why a domain already connected to Vercel can’t be added to Super.so, and how using a subdomain or removing it fixes the issue.
If your root domain is already connected to Vercel, then there are some different steps to go through in order to connect to Super. Subdomains connected to Vercel can also cause a problem connecting to Super. For example, leaving the root domain or subdomain on Vercel will prevent it from being connected to Super, even if the DNS settings are correct.
Super.so is hosted on Vercel internally. That means when you connect a custom domain to Super, Super is essentially creating a Vercel deployment on their own Vercel account, not yours.
- Conflict with root domains: Vercel does not allow the same root domain to be used in two separate Vercel accounts at the same time. So:
- If your domain is currently connected to your Vercel project, Super cannot add the same root domain to their Vercel project.
- This is not about DNS, it’s a restriction on Vercel itself.
- Implication for users:
- If you want
example.comon Super.so, andexample.comis already in your own Vercel account, you must remove it from your Vercel account first. - After removal, Super can connect it on their side.
- Workarounds:
- Use a subdomain instead (e.g.,
app.example.com), subdomains can usually be pointed to Super without touching the root domain in Vercel. - Transfer DNS control to another host. In some cases, this helps, but the main blocker is Vercel’s domain registration within your account, not the DNS itself.
Connecting Vercel Subdomain to Super.so
Subdomains are easier: You can connect subdomains (like www.example.com or app.example.com) to Super.so without removing the root domain from Vercel. Only the root (example.com) usually requires full removal if Vercel is managing it.