Custom domain CNAME points to my published app domain, but routes do not open

Teable Discussions
1

Hi everyone,

I have a Teable App Builder app that is already published and working correctly on my main domain, for example:

https://maindomain.com

In my DNS provider, I also have additional domains that I want to use with the same published app. For example:

https://anotherdomain.com

For those additional domains, I created DNS records pointing them to the main working domain, for example:

anotherdomain.com → CNAME → maindomain.com

DNS seems to resolve, but when I open a route on the additional domain, for example:

https://anotherdomain.com/r/example-code

I get a Vercel error:

404: NOT_FOUND / DEPLOYMENT_NOT_FOUND

The same route works correctly on the main domain:

https://maindomain.com/r/example-code

So my understanding is that DNS is pointing to the right place, but the additional domain is not actually attached/bound to the published Teable App Builder deployment.

Where can I add these additional custom domains in Teable App Builder so they are accepted by the deployment?

Thanks!

2

Hi @Alex ,

Thanks for raising this. I can see why you’d expect another domain pointing to the published app domain to work. Right now, App Builder supports one custom domain per published app, so we’ll need to consider multi-domain support separately.

Could you share more about the business use case behind this, for example whether the extra domains are for different brands or something else? For now, the best workaround is to use a reverse proxy in front of the app’s connected custom domain.