Sending email from your domain

By default Lurno sends system email — invitations, enrollment notices, reminders — from the shared send.lurno.ai address. Register a sending subdomain of your own and those same messages arrive from you, with your organization owning the DKIM signing for all its outbound mail. This is set up in Organization settings → Notification domains, not on the Integrations page.

What this does

You register a subdomain, Lurno registers it with its email provider and hands you back a set of DNS records. Once those records are live and verification passes, Lurno’s outbound mail for your organization sends from your address instead of the shared one.

You can register more than one domain, each with a different purpose — No-reply (transactional), Billing, Support, or Announcements — so different kinds of mail can come from different addresses. Lurno routes billing mail to your Billing domain and content-update mail to your Announcements domain, and everything else to No-reply. If a message’s purpose has no verified domain, it falls back to your No-reply domain before it falls back to Lurno. Start with No-reply — it carries the bulk of the mail, and it is the safety net for the others. Nothing is currently routed to the Support purpose, so registering one on its own won’t change any address your recipients see.

You do not need your own email provider account for this. Sending goes through Lurno’s shared infrastructure unless you have separately connected your own Resend account on the Integrations page, in which case the domain is registered under your account instead.

Before you start

You need permission to update the organization.
You need access to your domain’s DNS settings, or someone who can add records for you.
Decide on a subdomain, such as mail.yourdomain.com. If you type a bare root domain, Lurno warns you — “Use a subdomain, not your root domain” — and makes you acknowledge it before continuing, because deliverability problems on a root domain affect all of your mail.
Check the sidebar organization switcher. Domains belong to the organization shown there.

Register and verify a domain

Go to Organization settings and open the Notification domains tab.
Select Add domain (or Add your first domain if the list is empty). The Add a notification domain panel opens.
Fill in the form:
- Domain — the subdomain you’ll send from. Lurno may prefill a suggestion based on your organization’s website.
- Purpose — No-reply (transactional), Billing, Support, or Announcements.
- From (local part) — the part before the @. Defaults to noreply.
- Display name — optional, the name recipients see.
- Reply-to address — optional, where replies should go.
Select Register domain. Lurno registers the domain with the email provider and shows the DNS records.
Copy each record into your DNS provider exactly as shown — type, name, and value. Every row has a copy button.
Select Verify now. If DNS hasn’t propagated yet you’ll be told so, and Lurno keeps checking in the background.

You can close the panel and come back. Select the domain’s row in the list to reopen it, review its records, see when it was Last checked, and run Re-check DNS.

After it verifies

A newly verified domain goes through a warm-up period, shown as a Warming up badge counting toward 10,000 next to its status in the domain list. During warm-up, sending from that domain is capped at 100 messages an hour to protect its reputation; anything over the cap is pushed into the next hour rather than dropped, so a large invitation batch trickles out instead of failing. Warm-up clears itself automatically once the domain has sent 10,000 messages or 48 hours have passed since its first send, whichever comes first — so a low-volume domain still leaves warm-up (and its 100/hour cap) on its own after two days, not only by reaching the count.

Reference

Item	Notes
Domain	The sending subdomain, for example `mail.yourdomain.com`. A root domain triggers a warning you must acknowledge.
Purpose	No-reply (transactional) · Billing · Support · Announcements. No-reply carries most mail and backs up the others; nothing routes to Support yet. The same domain can’t be registered twice for the same purpose.
From / Display name / Reply-to	The address, sender name, and reply address recipients see.
DNS records	Generated for you. Each row shows the DNS Type (TXT, CNAME, or MX) and the provider’s role label — DKIM, SPF, or DMARC. Add all of them.
Status	Pending · Verifying · Verified · Failed.
Warming up	Shown after verification while send volume is throttled at 100/hour. Clears automatically at 10,000 sent messages or 48 hours after the first send, whichever comes first.

Troubleshooting

Verification stays pending. DNS propagation is not instant — Lurno’s own message says it can take from 15 minutes to a few hours, and it keeps re-checking in the background. If it is still pending well after that, compare each record’s name and value against what the panel shows, watching for extra spaces or a trailing dot.

A record isn’t detected. Some DNS providers append your domain to the record name automatically. If the full host doubled up — mail.yourdomain.com.yourdomain.com — enter only the portion your provider expects.

Verification failed with a reason shown. Open the domain’s row. The failure reason from the provider is displayed at the top of the panel, and Re-check DNS retries after you fix it.

“This domain is already registered for this organization with this purpose.” A domain can only be registered once per purpose. Use the existing entry, or pick a different purpose.

Registration is blocked because the API key is sending-scoped. The message tells you to ask your platform admin for a full-access key. Registering a domain needs more than send permission on the email account being used — contact Lurno if you are on the shared account, or issue a full-access key if the account is your own.

Messages still come from the Lurno address. Sending only switches over once the domain shows Verified. Note also that if you have connected your own Resend account but have no verified domain in it, mail keeps going out through the Lurno-managed account.