@eve I was considering asking this question over support email but figured the community would get value from your answer.
We were anticipating upgrading to Bubble’s
production plan to gain the ability to easily push Parent App updates to SubApps. We’ve since realized that doing this may require setting up a unique
A record for each of our customers (each subapp). That would mean that if we wanted to host these customers at
customerC.saas.com, then we would have to create the following records in our DNS:
Is this correct?
If so, that’s a bit troubling because that would mean we’d essentially be broadcasting our customer list to the world via publicly visible DNS records. That’s not okay for several reasons.
So my ultimate question is, "Is there a way for us to route customer subdomains to their respective subapps without having to create a publicly visible record of each subdomain we support?