When your Portail ZAPP instance is hosted by its support server, it can be served under your organization's domain name, for example support.example.com, instead of only its technical name. You enter the domain in the instance; the support server checks the DNS, issues the certificate and routes the traffic.
The Custom domain page (/licensing/custom-domain, Administration menu, administrators) is offered only when the instance is attached online to its support server (Licenses page, automatic mode) and the server offers the feature. Otherwise, the page explains why the feature is not available.
Add a domain
- Enter the domain name, without
https://, port or path. One domain at a time. - The page shows the exact DNS record to create at your domain's DNS provider: its type (
CNAMEorA), name and value. - Create the record, then click Check now. DNS propagation can take several hours: you can come back later, the check carries on by itself.
A bare domain (no subdomain, for example example.com) needs an A record, not a CNAME.
Before sending anything, the instance refuses an invalid name, an IP address, localhost or the technical name itself. The support server refuses a domain already used by another instance, or reserved.
Statuses
| Status | What happens |
|---|---|
| Waiting for DNS | The record shown is not visible yet. Create it, then check. |
| Activating | DNS verified: the certificate and routing are in progress. The page is updated at the next tracking run (within 5 minutes). |
| Active | The domain serves the instance. |
| Failed | The cause is shown (DNS not found or different, certificate, routing), with the server detail. Fix it, then Try again. |
| Removing | The domain is being removed. |
On activation
- The instance sets the new name as its public address (
App:BaseUrl) by itself: email links and absolute addresses use it. It does so only when the support server reports the domain active, never on the entry alone. - The technical name stays active: the instance also answers under that name.
- Users must sign in again on the new domain: a session is bound to the host name. The old name remains usable.
- External sign-in: the page lists each configured sign-in provider (Microsoft 365, Google Workspace, OpenID Connect) with the exact redirect address to register with it for the new domain, for example
https://support.example.com/auth/login/m365/callbackin the Entra ID application. Register it in addition to the current one, before activation. - External integrations: update those that call the instance by its address (webhooks, connectors, saved links).
While a domain is managed by this page, the public address is read-only in the configuration (/configuration), with a link to this page.
Your own address takes precedence (WEBBASE-3869). If you entered another public address in the configuration while it could be changed (before the request, in manual mode, while the support server was unavailable), the instance keeps it: it replaces it neither on activation nor on removal, and the key stays editable. The page says so. What counts is who wrote the value, not the value itself (WEBBASE-3872): even the technical name typed again in the configuration stays your value. To hand it back to the custom domain, click Hand over to the custom domain in the banner: the instance immediately writes its own value (the domain if it is active, otherwise the technical name, keeping the base path) and the key becomes read-only again. The action is recorded in the audit log. An address entered in advance that is exactly the requested domain is not ākeptā: the instance adopts it on activation.
Remove the domain
In the Remove the domain card, type the domain to confirm. The instance immediately restores its technical name as public address and the support server removes the routing. Users signed in through the custom domain will have to sign in again under the technical name.
History
Each request, activation, failure and removal is recorded in the audit log with its author (the administrator who removed the domain, or the instance if the support server removed it), and so is āHand over to the custom domainā.