- Shipped
- September 23, 2026 at 2:48 PM UTC
- Author
- Kamo
- Commit
- b5301c9
Every white-label org points a fixed set of labels at Kamo and computers was not one of them, so an org could follow /setup/dns to the letter and still have a Hosted Computer nobody could open. The link is built from that host; a link to a host with no record is a browser tab that opens and closes before any request leaves the machine, with nothing logged anywhere in Kamo and the computer itself healthy and awake throughout. Four lists move together or not at all. DomainAliasContractTest asserts exact equality between KnownAliases, SSL_PROBE_LABELS and its own mirror of the studio catalog, because the failure they guard against is silent: a label the studio requires but verify-dns never emits a status for falls through to "pending", so the card sits at "awaiting DNS" forever no matter what the customer's zone actually says. That is what happened to `media` for four months in 2026. Required like every other label rather than only for orgs holding the app. The record is what makes Hosted Computers work the day it is switched on, and an org sent back to its registrar months later, for one record, is an org whose first computer does not open. THE LINK NOW USES THE ORG'S OWN HOST buildLink takes the organization and builds https://computers.<its live domain>, via OrgLinkHosts.liveRootDomain — the same helper the borrower portal uses, and for the same reason: a domain that is configured but not yet verified would send a member to a host that does not resolve. Unlike the borrower portal, falling back to the platform host is CORRECT here rather than a broken link. One gateway serves every tenant and the machine is chosen by the signed token, never by the hostname, so an org with no live domain still gets a working computer — it simply opens on computers.kamocrm.com until its own domain is live.