Learning Objective
By the end of this tutorial, you’ll know how to configure your GoDaddy-hosted domain DNS so your email authentication (MX, SPF, DKIM, DMARC) is correct and your Lemlist custom tracking domain (CNAME + TXT) validates successfully.
Why This Matters
Correct DNS records help mailbox providers trust your messages, which improves deliverability and reduces bounces/spam placement. A custom tracking domain also helps your links and tracking align with your brand domain, making outreach more consistent and easier to manage.
Prerequisites
You have access to your GoDaddy account where the domain DNS is managed.
You know where your mailbox is hosted (for example: Google Workspace/Gmail, Microsoft 365/Outlook, Zoho, or another provider).
You have admin access to your email provider to generate or retrieve DKIM details.
You have access to your Lemlist workspace and the sending email account you want to configure.
Core Lesson — Step-by-Step Workflow
Phase 1: Open your DNS management area in GoDaddy
In GoDaddy, open the left-hand menu and click DNS to access DNS tools for your domains.
From your domain list, open the domain you want to edit (you’ll land on the domain’s Overview page).
Go to the domain’s DNS tab to manage records.
You should now see the DNS Management area for the selected domain. (If needed, you can also use Domain Settings from this screen.)
Under DNS Records, click Add New Record to start creating a DNS entry.
Most of the work happens in the DNS records area, where you’ll add or update MX, TXT, and CNAME records.
Phase 2: Configure MX records (mail routing)
MX records tell the internet where to deliver email for your domain. Without correct MX records, inbound mail may bounce or never arrive.
In the MX section, choose the setup option that matches your mailbox host:
If your email is hosted with GoDaddy, use the GoDaddy option.
If you use an external provider (Google, Microsoft, Zoho, etc.), select that provider.
If your provider is listed, let GoDaddy generate the MX records automatically and continue to apply them.
If your provider is not listed, add MX records manually using the exact values provided by your email host (record name/host, priority, and target/server).
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 |
Important: 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.
Tip: MX record values are not universal. Always use the official MX targets and priorities provided by your mailbox host.
Phase 3: Add your SPF record (TXT)
SPF defines which services are allowed to send email on behalf of your domain. In GoDaddy, SPF is added as a TXT record.
Click Add New Record.
Fill in the new record fields:
Set Type to TXT
Set Name (Host) to @ (this represents the root domain)
In Value, paste your SPF string from your email provider
Leave TTL at the default value unless you have a specific reason to change it
Click Save.
Common SPF examples (your provider may differ):
Google Workspace:
v=spf1 include:_spf.google.com ~allMicrosoft 365:
v=spf1 include:spf.protection.outlook.com ~allZoho: (use the current Zoho-provided SPF include for your region/account)
Important: You should have only one SPF record per domain. If you use multiple senders (for example, Google Workspace + Microsoft 365 or additional sending services), you must merge them into a single SPF value (multiple include: mechanisms) rather than creating separate SPF TXT records.
Phase 4: Add DKIM (TXT) and DMARC (TXT)
DKIM proves that your email wasn’t altered in transit and that it was authorized by your domain. DKIM values are generated by your email provider (they are not universal).
In your email provider admin settings, generate or locate your DKIM record details.
In GoDaddy, click Add New Record and select TXT (or follow your provider’s instructions if it requires CNAME-based DKIM).
Paste the DKIM Name/Host and Value exactly as provided.
Keep TTL at default and click Save.
Note: If you can’t find DKIM in your email provider, check their help center for “DKIM setup” or contact their support. The provider must supply the correct record name and value.
DMARC tells receiving servers what to do if SPF/DKIM checks fail. It’s also added as a TXT record and can use a universal structure.
Click Add New Record in GoDaddy.
Set Type to TXT.
Set Name/Host to
_dmarc(commonly used; keep exactly as needed by your DNS format).Set Value to a DMARC policy string.
Keep TTL at default and click Save.
Recommended policy approach:
Start with quarantine as a practical default for many outreach setups.
As your domain reputation strengthens (for example, after warming up and stable sending), consider moving to reject.
Example DMARC values:
Quarantine:
v=DMARC1; p=quarantine;Reject:
v=DMARC1; p=reject;Monitoring only:
v=DMARC1; p=none;
Phase 5: Set up a Lemlist custom tracking domain (CNAME + TXT)
A custom tracking domain helps align tracking links with your brand. Lemlist provides the exact values you must add in GoDaddy.
In Lemlist, open the email account settings where you want to add a custom tracking domain.
Choose the option to configure manually so you can view the DNS requirements.
In GoDaddy, click Add New Record and create a CNAME record:
Type: CNAME
Name/Host: copy the host/name from Lemlist (often a subdomain like
trackorlinks)Value/Target: copy the destination provided by Lemlist
TTL: leave default
Then add the required TXT record from Lemlist:
Type: TXT
Name/Host: use the host/name specified by Lemlist
Value: paste the TXT value provided by Lemlist
TTL: leave default
Return to Lemlist and run the Check setup validation for the tracking domain.
If you have multiple team members using the same domain, use the option in Lemlist to validate/apply for the domain so you don’t need to repeat the tracking-domain setup per user.
Practical Application / Real-Life Example
Scenario: Your company uses Google Workspace for mailboxes, but you also send from an additional platform that needs SPF authorization.
MX: Use Google Workspace MX records (set via GoDaddy’s Google option or manually using Google’s published values).
SPF: Publish a single SPF TXT record that includes Google plus your additional sender (combined into one string).
DKIM: Generate DKIM in Google Admin and publish the provided DKIM record in GoDaddy.
DMARC: Start with
p=quarantine, then move top=rejectonce sending is stable and authenticated mail is consistent.Tracking domain: Add Lemlist’s CNAME + TXT to a subdomain like
track.yourdomain.com, then validate in Lemlist.
Troubleshooting & Pitfalls
Issue: Emails bounce or incoming mail doesn’t arrive
Root cause: MX records are missing, incorrect, or pointing to the wrong provider.
Fix:
Confirm which provider hosts your mailbox (Google/Microsoft/Zoho/etc.).
Replace MX records with the official values from that provider.
Wait for DNS propagation, then test by sending to the domain from an external address.
Issue: SPF “PermError” or SPF validation fails
Root cause: Multiple SPF TXT records exist, or the SPF string is malformed.
Fix:
Ensure there is only one SPF TXT record for the domain.
Merge all required senders into a single SPF value (multiple
include:entries).Remove old/duplicate SPF TXT records.
Issue: DKIM shows as not set or failing
Root cause: DKIM value/host is not copied exactly, or DKIM hasn’t been enabled/generated in the email provider.
Fix:
Regenerate or re-check DKIM in your email provider admin.
Copy/paste the DKIM host and value exactly (no extra spaces).
Confirm whether your provider requires DKIM as TXT vs CNAME and follow that format.
Issue: Lemlist tracking domain won’t validate
Root cause: Missing TXT verification record, incorrect CNAME host/value, or DNS propagation delay.
Fix:
Verify both records exist: the CNAME and the Lemlist-provided TXT.
Confirm you added records to the correct domain and correct subdomain host.
Wait and re-check (DNS changes can take time to propagate).