Connecting a custom domain

By default your Lurno site lives at a Lurno web address. A custom domain lets you serve the same academy from a hostname you own, so people reach it at something like learn.yourcompany.com. The primary domain is also the address used in your branded invitation and password-reset links.

What this does

A custom domain replaces the web address people type or click to reach your academy. Lurno provisions the hostname and issues the TLS certificate for you; your only job is publishing a handful of DNS records at your own DNS provider. Whether you run a corporate training portal, a customer academy, a university site, or a school platform, the address in the browser bar is your own.

Once a domain is live you can also brand its sign-in screen — see the login-page background slots in Branding & theming.

Before you start

You need the organization-domain permission on the organization the domain belongs to.
You need access to your domain’s DNS settings, usually through your registrar or IT team.
Decide the exact hostname, for example learn.yourcompany.com. Enter it lowercase, with no https:// and no path.
A hostname can belong to only one organization. If it’s already registered elsewhere, adding it fails with “Couldn’t add the domain.” and “This hostname is already registered.”

Add your domain

Open Org settings from the sidebar and go to the Domains tab. The card is headed Domains for your organization.
Select Add. The three-step Add a domain wizard opens: Hostname, Verify, Done.
Hostname — type the hostname and select Continue. The domain is saved at that point and Lurno starts provisioning it, so nothing is lost if you close the wizard later. You’ll see “your hostname ready — copy the DNS record next”; select Next to move on.
Verify — Lurno shows the records to publish, each with a copy button, plus a Certificate status chip. Add every row at your DNS provider exactly as shown.
Select I added it, check now. If DNS hasn’t propagated yet you’ll see “We couldn’t find the record yet” with a Show me what to look for helper — that’s not a failure. Select Next to continue regardless; Lurno keeps checking on its own.
Done — optionally switch on Set as primary, then select Finish.

The certificate is issued and the domain goes live automatically once your DNS propagates, usually a few minutes later. You never handle certificates yourself, and there’s no renewal step.

Manage an existing domain

Select any hostname in the Domains list to open its drawer:

About — the hostname, its Primary badge and verified/certificate status, the DNS records to publish (re-copyable while it’s unverified), the last check time, and the last DNS error if there was one.
Settings — the Primary domain toggle and a Recheck DNS button that re-runs the lookup immediately. Both take effect as soon as you use them; there’s nothing to save.
Remove this domain — a hard delete with a confirmation. There’s no undo; re-add the hostname if you change your mind. Invitation and reset links already sent keep working until they expire.

A manual “Verified” switch also exists, but it is reserved for Lurno platform staff and is hidden from organization admins — hand-stamping a domain as verified would bypass the DNS proof. Recheck DNS is the real verification path.

Sub-organization domains

Each organization in your tree keeps its own domain list. To give a sub-organization its own hostname, switch to it in the organization switcher first, then open its Domains tab and add the domain there. See Sub-organizations & structure.

Reference

Field	What it means
Hostname	The address people will use, lowercase, no scheme or path — e.g. `learn.yourcompany.com`
Record type / name / value	The DNS entries you publish so Lurno can route traffic and prove control of the name
Certificate	Provisioning, Live, or Validation failed — check your DNS records
Verified	Set once the DNS check passes
Primary	The one hostname used in branded invitation and password-reset URLs

Troubleshooting

The Domains tab isn’t there. You don’t hold the organization-domain permission on this organization. It is a distinct permission from the one that opens the rest of Organization settings.

“We couldn’t find the record yet.” DNS takes time to propagate. Confirm every row matches exactly, with no extra characters and no stray trailing dot — some providers rewrite or strip a leading underscore. Wait a few minutes, then select Recheck DNS. You don’t have to sit on the wizard; verification also runs on its own.

The certificate says Validation failed. That’s a terminal state, not a slow one — the records are wrong, missing, or the validation window expired. Fix the records at your DNS provider and select Recheck DNS. If it still fails, remove the domain and add it again to restart provisioning.

The certificate has said Provisioning for a while. It stays there until your DNS propagates and Lurno finishes issuing. Check the About section for a last-check error before assuming it’s stuck.

“Couldn’t add the domain.” / “This hostname is already registered.” A hostname can be attached to one organization at a time. Remove it from wherever it’s registered first.

Branded invitation links still use the old address. Only the Primary domain is used for those. Open the domain’s drawer and switch on Primary domain.