External Domain Connection lets you use a domain you already own (with any registrar) inside lemlist without transferring it. You keep ownership and billing at your current registrar/IT team, then simply update your domain’s nameservers (NS) to lemlist so we can manage the DNS zone and power a fully automated email infrastructure.
Learning objective
By the end of this tutorial, you’ll know how to add an external domain, verify ownership, switch nameservers safely, and understand what lemlist checks before the domain becomes active for mailbox creation.
Why this matters
Many teams can’t transfer domains due to IT policies, internal approval processes, or centralized domain ownership requirements. External Domain Connection removes that friction while still giving you automated mailbox setup and centralized DNS management for outreach.
Prerequisites
You have admin access to update DNS at your current registrar (or can ask your IT team to do it).
The domain is already registered and active.
Important: This flow currently supports Google setup only.
Core lesson — Step-by-step workflow
Phase 1: Start the external domain connection
Go to Domain Settings and start the flow
In lemlist, open Settings, then go to Buy domains & emails and click Add external domain. This is where you connect a domain you already own (kept at your current registrar) to lemlist’s email infrastructure.
Enter your domain name
In the Add external domain modal, type the domain you want to connect (for example, example.com) and click Continue.
Phase 2: Verify domain ownership (TXT verification)
After you submit your domain, lemlist checks whether the domain exists and is already registered (WHOIS verification).
If the domain is not registered: you’ll be redirected to the domain purchase flow.
If the domain is registered: lemlist asks you to add a TXT record in your current DNS provider to prove ownership.
How verification checks run:
When you click DNS added
Automatically every 5 minutes for the first 1 hour
Then every 30 minutes
A manual recheck is available
7-day deadline: If the domain isn’t validated within 7 days, lemlist removes the domain and notifies you.
Phase 3: Prepare for the nameserver (NS) switch
Once the TXT record is verified, your domain appears in the list with the status:
Status: Pending NS changes
You’ll be asked to update your nameservers to lemlist:
ns0.dom.scw.cloudns1.dom.scw.cloud
What to expect at this stage:
A “waiting for NS update” notice while lemlist detects the change.
A disruption warning because changing nameservers can impact any services currently relying on your existing DNS zone (website, email, subdomains, verification records, etc.).
Best practice to avoid downtime: lemlist lets you configure your DNS zone inside lemlist before switching NS. Do this first so that when you flip nameservers, essential records (website, redirects, verification, etc.) are already in place.
Phase 4: NS detection and ongoing verification
After you update the nameservers at your registrar, lemlist will detect the change:
Automatic NS checks run every 1 hour
You can use a manual Detect NS changes action
lemlist also verifies twice daily that NS remains correctly connected
7-day deadline: If the nameserver change isn’t completed within 7 days, the domain is removed and you’ll receive an email notification.
Phase 5: Domain becomes active (ready for mailboxes)
Once lemlist detects the correct nameservers, your domain becomes Active:
✅ Domain is fully active in lemlist
✅ You can create mailboxes
✅ Email infrastructure and DNS management are handled inside lemlist
Practical application (recommended rollout plan)
Use a dedicated outreach domain (e.g., getexample.com) rather than your primary corporate domain.
Configure DNS in lemlist first (mirror any critical web/subdomain records you still need) before switching nameservers.
Plan the NS switch during a low-traffic window if the domain currently serves a website or active services.
Troubleshooting & common pitfalls
Issue: TXT verification never completes
Root cause: TXT record is missing, added to the wrong hostname, or DNS hasn’t propagated yet.
Fix:
Confirm the TXT record matches exactly what lemlist provided (no extra spaces/quotes unless required by your DNS provider).
Ensure it’s added to the correct host (often
@for the root domain, depending on your registrar UI).Wait for propagation, then click DNS added to recheck.
Issue: Domain is “Pending NS changes” even after updating nameservers
Root cause: Nameserver change can take time to propagate, or one NS value is incorrect.
Fix:
Double-check both nameservers are set exactly to:
ns0.dom.scw.cloudandns1.dom.scw.cloud.Use the manual Detect NS changes option and allow up to an hour for the next automated check.
Issue: Website or existing services stop working after NS switch
Root cause: Your previous DNS zone records (A/AAAA/CNAME/MX/TXT) were not recreated in lemlist before the nameserver cutover.
Fix:
Before switching NS, copy critical DNS records into lemlist’s DNS zone.
If you already switched and something broke, recreate the missing records in lemlist as soon as possible.
Issue: Domain disappears after a few days
Root cause: The domain wasn’t verified (TXT) or the NS switch wasn’t completed within the 7-day window.
Fix: Re-add the domain and complete the pending step promptly; involve your IT team early if approvals are needed.