Reserved names
Two different things get reserved
Subdomains of the platform domain. Your site is given
yoursite.businessdash.us, which means site slugs and platform infrastructure
share one namespace. Some labels in that namespace already mean something, so
they cannot become a site address.
Hostnames you try to connect. A few hostnames are refused when you add them, because connecting them would mean claiming something that is not yours.
Reserved subdomains
A single label in front of the platform domain is only treated as a site address when the label is not one of these:
| Group | Labels |
|---|---|
| The product itself | app, www, api, portal, admin, dashboard |
| Sign-in | auth, login, signup |
mail, email, smtp, webmail | |
| Assets | cdn, static, assets, media, img, images, files |
| Documentation and support | docs, documentation, developer, dev, blog, status, help, support |
| Template demos | demos |
| Infrastructure | ns1, ns2, ftp |
Each of these already resolves somewhere. docs and its aliases redirect to
the documentation you are reading; demos serves template marketplace demos
on their own origin so a demo session can never share an origin with a real
dashboard session; app is the prefix for your own app surface, which is
app.yoursite.businessdash.us. Handing any of them to a site would mean two
different things answering at one address.
This only applies to the platform domain. On a domain you own, the namespace
is yours: mail.yourdomain.com and app.yourdomain.com are yours to use
however you like.
Hostnames you cannot connect
| You try to connect | Why it is refused |
|---|---|
| The platform domain itself | It is not yours to claim. Connect a domain you control |
app.yoursite.businessdash.us | The app surface is provisioned automatically and has no DNS for you to configure |
| A single-label name | A hostname needs at least two labels — example.com, not example |
| A hostname attached to another site | A hostname is a global claim; one address cannot serve two sites |
| A hostname inside its detach cooldown | See Connecting a domain you own |
Why a hostname is claimed globally rather than per workspace
Connected hostnames are unique across the whole platform, not just within your
workspace. That is stricter than it has to be for your own convenience, and it
is the only version that is safe: DNS is global, so if two workspaces could
both hold example.com, whichever one the lookup happened to find first would
serve the pages. Making the claim exclusive means the answer is never a
coin toss.