Custom domains
Understand product domain registration, hosts, and DNS management.
Registering a domain associates a DNS name with your product and makes it available to features running there. It does not prove ownership or route traffic by itself. Traffic changes only when the required DNS records are published.
For a deployed service’s hostname and TLS setup, see Deployment domains.
Registration and access
Domains belong to products. The same domain cannot be registered twice within one product, but different products can register the same name. Registration has no ownership challenge, verification status, or verified timestamp.
Operation | Who | Tool |
|---|---|---|
Add a domain | Product owner or admin | |
List domains | Any product member | |
Read a domain and its hosts | Any product member | |
Remove a domain | Product owner or admin |
Despite their names, these tools operate on a product and require its ID.
Hosts and records
A host is an individual DNS name under a registered domain, such as app.example.com or _dmarc.example.com, with its required records. Each host can be claimed once per product. A collision names the current user of the host.
Host state | Meaning |
|---|---|
pending | Not yet active. |
active | Reported active by the feature using it, or by the managed DNS write. |
failed | Carries a failure reason. |
The platform does not poll DNS to establish these states. Domain removal is blocked while any host is active; when none is active, pending and failed hosts are removed with the domain.
Records are stored instructions, not DNS-validation results. An apex normally uses A and TXT; a subdomain uses CNAME and TXT. An apex managed through provider flattening may have no records listed here. Use the returned values rather than inventing addresses. ALIAS and ANAME are provider features, not record types to supply as these instructions.
External and managed DNS
Mode | Responsibility |
|---|---|
External, the default | Lepsto shows records; you publish them at your DNS provider. |
Managed | Lepsto writes and maintains records through a Cloudflare connection attached to the product. |
An owner or admin selects a connected Cloudflare account when enabling managed mode. Its zone must already exist: Lepsto does not create the zone or change nameservers. If it is missing, affected hosts fail with a domain-not-found message.
One organization may have several Cloudflare connections; each managed domain uses one. Switching back to external mode leaves previously written records in Cloudflare. Remove them yourself if they are no longer needed.
Conflicting records
Managed DNS changes only records it created or adopted for its hosts. A single conflicting address record can be adopted and pointed at the platform. Multiple conflicting records are left in place and the host fails. Records belonging to another product or domain are not removed to make room.