This guide shows you how to configure your domain’s DNS in Namecheap so it works properly.
Learning Objective
By the end of this tutorial, you’ll know how to set the correct MX, SPF, DKIM, and DMARC records in Namecheap, then add a custom tracking domain in Lemlist and verify everything in DNS Health.
Why This Matters
These DNS records prove your emails are legitimate and authorized, which improves deliverability and protects your domain reputation. Without correct DNS authentication, your outbound emails are more likely to land in spam (or fail authentication entirely).
Prerequisites
You have access to your Namecheap account and the domain you’ll use for sending.
You already have an email provider set up (for example: Google Workspace, Microsoft 365, or Zoho Mail).
You can access your email provider’s admin panel to copy the required MX and DKIM values.
You have access to your Lemlist workspace to configure the tracking domain.
Core Lesson — Step-by-Step Workflow
Phase 1: Open your DNS settings in Namecheap
Log in to Namecheap.
Go to Domain List.
Next to your domain, click Manage.
Open the Advanced DNS tab.
All DNS configuration (MX, TXT, CNAME records) happens here.
Phase 2: Set up MX records (required for receiving email)
What MX does: MX records tell the internet which server receives email for your domain. If MX records are wrong, your inbox and provider routing may break.
In Namecheap Advanced DNS, scroll past Host Records until you find Email Settings.
Choose the correct option:
Custom MX if you use Google Workspace, Microsoft 365, Zoho, or another external email provider.
Private Email if you use Namecheap’s Private Email service.
After selecting Custom MX (or Private Email), use Add New Record to add your provider’s MX entries (including the correct priority).
Avoid “Email Forwarding”. If Email Settings is left on forwarding, your inbox won’t connect correctly to your real email provider and MX will not work as intended.
Important: You don’t invent MX values. Your email provider gives you the exact MX records to copy/paste (including priority). Examples: Google Workspace typically uses 5 MX records, Microsoft often uses 1, and Zoho commonly uses 3.
MX example patterns (for reference)
Google Workspace: multiple MX records with priorities like 1 / 5 / 10, etc. (copy exactly from Google Admin setup instructions).
Microsoft 365: typically one MX record that looks like:
<your-domain>.mail.protection.outlook.com(copy exactly from Microsoft).Zoho Mail: multiple records (for example MX1/MX2/MX3) with different priorities (copy exactly from Zoho).
Google Workspace MX records (current recommended setup)
Priority | Server |
1 | ASPMX.L.GOOGLE.COM |
5 | ALT1.ASPMX.L.GOOGLE.COM |
5 | ALT2.ASPMX.L.GOOGLE.COM |
10 | ALT3.ASPMX.L.GOOGLE.COM |
10 | ALT4.ASPMX.L.GOOGLE.COM |
If you see records like ASPMX2.GOOGLEMAIL.COM through ASPMX5.GOOGLEMAIL.COM in your DNS, remove them — these are outdated and no longer recommended by Google.
How to add/replace MX records safely in Namecheap
Use Add New Record to add each MX record (host is often
@).Namecheap requires at least one MX record at all times. If there’s an old MX record you need to remove but can’t delete yet, add the new MX record first, save it, and then delete the old one.
Phase 3: Add SPF (TXT) — authorize senders
What SPF does: SPF is a “permission list” that specifies which servers are allowed to send email from your domain. Incorrect SPF is a common reason messages land in spam.
In Namecheap, go back to Host Records, then click Add New Record.
Set:
Type: TXT
Host:
@Value: your provider’s SPF value (copy from your provider)
TTL: Automatic
Save your changes.
SPF rule: You must have only one SPF record (one TXT record that contains v=spf1). Multiple SPF records will cause SPF to fail completely.
If you previously used Email Forwarding, you may already have an SPF record—edit/replace it instead of creating a second SPF record.
If you use multiple sending systems/providers, you typically combine mechanisms into a single SPF value (rather than creating separate SPF TXT records).
Phase 4: Add DKIM (TXT) — cryptographic signature
What DKIM does: DKIM signs your outgoing emails so receiving servers can confirm the message wasn’t altered and truly came from your domain. This is critical for deliverability.
Generate DKIM inside your email provider first (Google/Microsoft/Zoho/etc.).
Return to Namecheap Host Records and click Add New Record.
Set:
Type: TXT
Host: your provider’s DKIM host/selector (for example, Google often provides something like
<selector>._domainkey)Value: the full DKIM public key provided by your email provider
TTL: Automatic
Save your changes.
Tip: DKIM values are provider-generated. Don’t try to write DKIM manually—copy/paste exactly from your provider’s admin panel.
Phase 5: Add DMARC (TXT) — policy + protection
What DMARC does: DMARC works with SPF and DKIM to tell receiving servers what to do if authentication fails, helping protect your domain reputation from spoofing.
In Namecheap Host Records, click Add New Record.
Set:
Type: TXT
Host:
_dmarcValue: a basic quarantine policy (example):
v=DMARC1; p=quarantineTTL: Automatic
Save your changes.
DMARC rule: Only one DMARC record should exist. Multiple DMARC TXT records can cause validation issues.
Best practice:p=reject is stricter, but use it only if you plan to monitor DMARC reporting and are confident all legitimate senders pass SPF/DKIM. A quarantine policy provides solid protection with less overhead.
Phase 6: Add a custom tracking domain in lemlist (CNAME + TXT)
Why this matters: A custom tracking domain improves alignment and trust for tracking links and can help reduce deliverability issues tied to mismatched tracking domains.
In Lemlist, click your profile icon in the bottom-left, then select Settings.
Open Sending settings, then click Settings next to the email address you use for sending.
In the email settings window, open Custom tracking domain.
Copy the displayed CNAME record details (Type, Host name, Value) from Lemlist.
In Namecheap → Advanced DNS → Host Records, click Add New Record and add:
Type: CNAME
Host: the hostname provided by Lemlist (example:
omega)Value: the target/value provided by Lemlist (copy/paste)
TTL: Automatic
Back in Lemlist, if prompted, use the provided option (for example Configure manually) and confirm the custom tracking subdomain matches what you created in DNS (typically:
<host>.<your-domain>).Lemlist will then show one or more TXT records. Copy them and add them in Namecheap under Host Records (Type TXT, Host/Value as provided, TTL Automatic).
Return to Lemlist and click Check setup.
Phase 7: Verify in Lemlist DNS Health
In Lemlist, go to Account Health → DNS Health.
Confirm the records show as healthy (green) once propagation completes.
DNS propagation note: DNS updates are not instant. If verification fails, wait and re-check before making more changes. Propagation can take a few minutes, and in some cases up to 72 hours.
Practical Application (Example Setup)
If your team uses Google Workspace for mailboxes and Lemlist for outreach:
Add Google’s MX records exactly as provided in Google’s setup guide.
Set a single SPF TXT record that authorizes Google (and any other legitimate senders you use).
Generate DKIM in Google Admin and publish it as a TXT record in Namecheap.
Add a basic DMARC policy (start with
p=quarantineif you’re not monitoring reports).Create a custom tracking subdomain in Lemlist and publish the required CNAME/TXT records in Namecheap.
Troubleshooting & Pitfalls
Issue: “My inbox isn’t receiving mail” or MX verification fails
Root cause: Email Settings left on Email Forwarding, or incorrect/missing MX records.
Fix:
In Namecheap, set Email Settings to Custom MX (or Private Email if applicable).
Re-copy MX records from your email provider and ensure host/priority/value match exactly.
If an old MX can’t be deleted, add the new MX first, save, then delete the old one.
Issue: SPF fails or you see “multiple SPF records” warnings
Root cause: More than one TXT record contains
v=spf1.Fix:
Keep only one SPF TXT record.
Merge all required sender entries into a single SPF value (instead of multiple records).
If an old forwarding SPF exists, replace it rather than adding a second SPF record.
Issue: DKIM fails in Lemlist or provider check
Root cause: DKIM wasn’t generated in the provider first, selector/host is wrong, or the value was pasted incompletely.
Fix:
Generate DKIM in your email provider admin panel.
Copy/paste the DKIM host/selector and full key exactly as provided.
Wait for DNS propagation, then re-check.
Issue: DMARC fails or shows conflicting records
Root cause: Multiple DMARC TXT records exist, or the host isn’t
_dmarc.Fix:
Ensure you have exactly one DMARC TXT record at host
_dmarc.Use a valid value such as
v=DMARC1; p=quarantine.
Issue: Lemlist tracking domain “Check setup” fails
Root cause: CNAME/TXT values were not copied exactly, wrong hostname/subdomain, or propagation isn’t complete.
Fix:
Re-copy CNAME and TXT records directly from Lemlist and paste into Namecheap.
Confirm the custom subdomain format in Lemlist matches what you published (for example,
omega.yourdomain.com).Wait and retry (propagation can take up to 72 hours).
If you want to independently verify DNS status, use a third-party checker (for example, MX record and TXT record lookup tools). If records look correct in Lemlist but not externally after extended time, contact Namecheap support—DNS propagation and zone issues are handled at the domain/DNS provider level.