This guide walks you through configuring a dedicated sending domain for LeadConnector Email inside Siteground's DNS Zone Editor. You'll add two TXT records, two MX records, and one CNAME record — five records in total.
Before you start, decide whether you'll use your main domain (e.g. companyname.com) or a subdomain (e.g. replies.companyname.com). If your main domain is already used with Google Workspace or another mail provider, you must use a subdomain.
Initial Setup — Add & Verify Your Domain
In your sub-account, go to Settings → Email Services → Dedicated Domain → + Add Domain.

If your domain is companyname.com, you can set up either the main domain or a subdomain.
Main domain — if you add the main domain, it must not be used with Google Workspace or any other email provider at the same time.
Subdomain — type anything before your root domain, e.g. replies.companyname.com or support.companyname.com. This is the recommended option if you already use your root domain for email.
If you use Google Workspace (Gmail) for your main domain's incoming email, you must use a subdomain here — otherwise your Google Workspace MX records will conflict with the Mailgun MX records you're about to add.
Enter your domain or subdomain name and click Add & Verify.

The next screen will display the 5 DNS records you need to add. Keep this screen open — you'll reference it throughout the following steps.

1st TXT Record (SPF)
Log in to Siteground and go to Site Tools → Domain → DNS Zone Editor.

In the Create New Record section:

Enter only the subdomain portion of your domain:
- Setting up lc.companyname.com → Name: lc
- Setting up replies.companyname.com → Name: replies
- Setting up the main domain (companyname.com) → Name: @ or leave empty

Paste the following value exactly as shown:

2nd TXT Record (DKIM)
Click + Add Record again to open a new Create New Record form.

Head back to the platform's DNS records screen and copy the hostname for the 2nd TXT record. Copy everything up to (but not including) your root domain. The key is to exclude companyname.com from whatever you paste.

Everyone's 2nd TXT record hostname and value is unique to their account. Copy the exact values shown on your DNS records screen.
Examples — copy only the highlighted portion:
| Scenario | Hostname to enter in Siteground | Example screenshot |
|---|---|---|
| Subdomain (e.g. helpdesk.companyname.com) | mx._domainkey.helpdesk | ![]() |
| Main domain (companyname.com) | mailo._domainkey | ![]() |
Go back to the platform and copy the value shown for the 2nd TXT record (highlighted below). Paste it into the Value field in Siteground.

1st MX Record (mxa.mailgun.org)
Click + Add Record to open a new form. This time, click the MX tab and select Add your own MX records.


Use the same logic as the TXT records above:
- lc.companyname.com → Name: lc
- replies.companyname.com → Name: replies
- Main domain (companyname.com) → Name: @


Paste the following destination:

2nd MX Record (mxb.mailgun.org)
Click + Add Record again. The 2nd MX record is identical to the 1st except the destination changes to mxb.

- lc.companyname.com → Name: lc
- replies.companyname.com → Name: replies
- Main domain → Name: @



CNAME Record
Click + Add Record one final time.

Go back to the platform and copy the CNAME hostname. Exclude the root domain portion.
- lc.companyname.com → Name: email.lc
- replies.companyname.com → Name: email.replies
- Main domain (companyname.com) → Name: email



Now that all 5 DNS records are in place, go back to the platform and click Verify DNS Settings.

If some records still show a red ✗ after verifying, click Verify Domain again. DNS changes can take up to 24–48 hours to propagate fully, though they often appear within minutes on Siteground.
Once all records show a green checkmark, verify your SSL Certificate for Dedicated Sending Domain (LC - Email) is set up correctly.
Then send a test email from the Conversation to confirm everything is working end-to-end.
Frequently Asked Questions
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article

