Revset
Book a Free Audit

30-minute call · No obligation

HomeGHL HubSettings & AdminSet Up Mailgun DNS Records for Google Domains in GoHighLevel
REVSET LABS · EXPERT GUIDE·Settings & Admin

Set Up Mailgun DNS Records for Google Domains in GoHighLevel

1,403 words·6 min read·Updated 28 April 2026·beginner·
Arsalan ZaffarArsalan ZaffarLinkedIn

👉 Start your 30-day GoHighLevel free trial.

Start 30-Day Free Trial
Quick Answer

To set up Mailgun DNS records for your Google Domain, go to your Google Domains DNS settings and add the required TXT, MX, and CNAME records. This ensures your GoHighLevel emails send reliably and reach recipients' inboxes. The process takes approximately 15-20 minutes to complete the setup.

Key Takeaways
  • Always use the correct hostname for your domain type (main domain or specific subdomain) for each DNS record.
  • Carefully copy the full TXT record values from Mailgun, especially the second DKIM record, to avoid verification errors.
  • Add both MX records with the specified priority of '10' for proper inbound email routing to Mailgun.
  • Verify DNS settings in Mailgun *after* saving all records in Google Domains to confirm successful propagation.
  • Allow up to an hour for DNS propagation before re-verifying if records do not show as active immediately.

Why Set Up Mailgun DNS for Google Domains?

Setting up Mailgun DNS records for your Google Domain is a critical step for ensuring high email deliverability within GoHighLevel. Without proper DNS configuration, your emails risk being marked as spam or failing to reach your contacts entirely. This guide walks you through the precise steps to configure Mailgun with your Google Domain, ensuring your GoHighLevel communications are sent reliably. By correctly configuring these records, you authenticate your domain as an authorized sender, building trust with email providers. This significantly improves your chances of landing in the inbox, which is essential for successful marketing campaigns and client communication.

1
Access Mailgun DNS RecordsLog into your Mailgun account and navigate to the Domains section. Click on the specific domain you want to set up with GoHighLevel to view its required DNS records.
2
Log Into Google DomainsOpen a new browser tab and log into your Google Domains account. Ensure you are accessing the account that manages the domain you intend to integrate with Mailgun.
3
Navigate to DNS SettingsIn Google Domains, select the domain you are configuring. Click on DNS in the left-hand menu to access your domain's DNS management page.
GoHighLevel screenshot
0

⚠️ Do not modify any existing DNS records unless you are certain they are related to Mailgun and need updating. Incorrect changes can disrupt other services like your website or existing email.

🔥 Pro Tip

Keep both Mailgun and Google Domains open in separate browser tabs. This allows you to easily copy and paste record values without switching back and forth, saving time and reducing errors.

How Do I Add the First Mailgun TXT (SPF) Record?

The first TXT record you add is for SPF (Sender Policy Framework). This record tells receiving email servers which IP addresses are authorized to send emails on behalf of your domain. It helps prevent spammers from forging emails from your domain, thereby improving your email's trustworthiness and deliverability.

1
Locate Custom RecordsOn your Google Domains DNS page, scroll down to the Custom records section. This is where you will add all new Mailgun DNS entries.
2
Create a New RecordClick the Create new record button to open the form for adding a new DNS entry. You will use this button for each record you add.
GoHighLevel screenshot
0
3
Set Record Type to TXTFrom the Type dropdown menu, select TXT. This specifies the type of DNS record you are creating.
4
Determine the HostnameEnter the correct hostname based on your domain setup. If you are configuring a main domain (e.g., `yourcompany.com`), use `@` as the hostname. If you are using a subdomain (e.g., `mg.yourcompany.com` or `replies.yourcompany.com`), use only the subdomain part (e.g., `mg` or `replies`).
GoHighLevel screenshot
1
5
Paste the SPF ValueIn the Data field, paste the first TXT record value provided by Mailgun, which typically looks like `v=spf1 include:mailgun.org ~all`. Ensure no extra spaces are copied.
6
Prepare for Next RecordDo not click Save yet. You will add four more records before saving all changes at once. Click Create new record again to add the next entry.
GoHighLevel screenshot
2
GoHighLevel screenshot

⚠️ Using the wrong hostname for your domain type is a common mistake. Double-check whether you are setting up a main domain or a subdomain before entering the hostname.

What is the Second Mailgun TXT (DKIM) Record and How Do I Add It?

The second TXT record is for DKIM (DomainKeys Identified Mail). DKIM adds a digital signature to your outgoing emails, allowing receiving servers to verify that the email truly originated from your domain and was not altered in transit. This is another crucial layer of email authentication that significantly boosts deliverability.

1
Create Another New RecordClick the Create new record button once more. This opens a new empty record entry for your second TXT record.
2
Set Record Type to TXTSelect TXT from the Type dropdown menu for this record as well. Both authentication records are TXT types.
3
Copy Mailgun DKIM HostnameGo back to Mailgun and carefully copy the *entire* hostname provided for the second TXT record. This hostname is usually a long string followed by `._domainkey` or similar, specific to your Mailgun domain setup (e.g., `k1._domainkey` or `mg.domainkey`). Paste this into the Hostname field in Google Domains.
4
Paste the DKIM ValueCopy the full, often very long, second TXT record value from Mailgun. Paste this entire string into the Data field in Google Domains, ensuring no parts are missed or truncated.
5
Prepare for MX RecordsDo not click Save yet. You still need to add the MX and CNAME records. Click Create new record to proceed to the next set of records.
GoHighLevel screenshot
0

⚠️ Mailgun's DKIM hostname can be tricky. Do not try to guess it; always copy it directly from your Mailgun domain settings to ensure accuracy.

🔥 Pro Tip

The second TXT record value (DKIM) is often very long. Ensure you copy the *entire* string from Mailgun without any omissions, as even a single missing character will prevent verification.

Try GoHighLevel Free

Start your 30-day GoHighLevel free trial

Everything in this guide is in your free trial. 30 days, no credit card — the platform behind 78+ revenue systems.

Start 30-Day Free Trial

Some links are affiliate links — if you sign up we may earn a commission, at no extra cost to you. We only recommend GoHighLevel because we build on it every day.

How Do I Add Mailgun MX Records to My Google Domain?

MX (Mail Exchange) records specify the mail servers responsible for accepting email messages on behalf of your domain. For Mailgun, these records ensure that any replies or bounce messages related to your sent emails are correctly routed back to Mailgun for processing and tracking. You will add two MX records, both with the same priority.

1
Create a New RecordClick the Create new record button to begin adding your first MX record. This prepares a fresh entry form.
2
Set Record Type to MXFrom the Type dropdown, select MX. This indicates that you are configuring a Mail Exchange record.
3
Determine the HostnameEnter the correct hostname: use `@` for a main domain (e.g., `yourcompany.com`), `mg` for `mg.yourcompany.com`, or `replies` for `replies.yourcompany.com`. Consistency with your TXT records is key.
4
Set Priority for First MXIn the Priority field, enter `10`. Both Mailgun MX records use this priority level.
5
Add First MX DataIn the Data field, paste `mxa.mailgun.org`. This is the address of Mailgun's primary inbound mail server.
GoHighLevel screenshot
0
6
Add Another MX EntryClick the +Add more to this record button. This allows you to add a second MX entry for the same hostname without creating a separate record form.
7
Set Priority for Second MXFor the newly added entry, set the Priority to `10`. This ensures both Mailgun servers are treated equally.
8
Add Second MX DataIn the Data field for the second entry, paste `mxb.mailgun.org`. This provides redundancy for Mailgun's inbound mail service.
9
Prepare for CNAME RecordDo not click Save yet. You have one final record to add. Click Create new record to move on to the CNAME entry.
GoHighLevel screenshot

⚠️ If you have existing MX records for another email provider, adding Mailgun's MX records may disrupt your current email service. Only proceed if Mailgun is intended to handle all inbound mail for this domain.

🔥 Pro Tip

Ensure both MX records have a priority of '10'. This tells email servers that both `mxa` and `mxb` are equally valid for receiving mail, improving reliability.

How Do I Add the Mailgun CNAME Record?

The CNAME (Canonical Name) record is used by Mailgun for tracking email opens, clicks, and other engagement metrics. This record redirects a specific subdomain to Mailgun's tracking servers, allowing you to gain valuable insights into your email campaign performance directly within GoHighLevel. This is the final record you need to add.

1
Create a New RecordClick the Create new record button to open the final record entry form. This will be for your CNAME record.
2
Set Record Type to CNAMEFrom the Type dropdown, select CNAME. This designates the record as an alias for another domain.
3
Determine the HostnameEnter the correct hostname: use `email` for a main domain (e.g., `yourcompany.com`), `email.mg` for `mg.yourcompany.com`, or `email.replies` for `replies.yourcompany.com`. This hostname is specific to Mailgun's tracking needs.
4
Paste the CNAME DataIn the Data field, paste `mailgun.org`. This is the target domain that your tracking subdomain will point to.
5
Save All DNS RecordsNow that you have added all five DNS records, click the Save button in Google Domains. This action applies all your new records simultaneously.

⚠️ Ensure you click the main 'Save' button in Google Domains after adding all records. If you exit the page without saving, your changes will be lost.

🔥 Pro Tip

Once all records are saved, grab a cup of coffee. DNS changes can take a few minutes to propagate across the internet, so patience is key before verification.

How Do I Verify Mailgun DNS Settings?

After adding all the DNS records to your Google Domain, the final step is to verify them within Mailgun. This process confirms that Mailgun can detect your newly configured records, indicating that your domain is properly set up for sending and tracking emails. Verification is crucial before you can reliably send emails through GoHighLevel.

1
Return to MailgunSwitch back to your Mailgun domain settings page in your browser. This is where you initially copied the DNS records from.
2
Initiate VerificationClick the Verify DNS Settings button. Mailgun will now attempt to check for the presence and correctness of your DNS records.
3
Check for Green CheckmarksLook for green checkmarks next to each DNS record in Mailgun. Green checkmarks indicate successful verification for that specific record.
4
Re-verify if NeededIf some records do not show a green checkmark immediately, wait 5-10 minutes and click Verify DNS Settings again. DNS propagation can take a short while.

⚠️ Do not attempt to send emails from GoHighLevel using this domain until all Mailgun DNS records are successfully verified. Sending before verification can lead to high bounce rates and poor deliverability.

✅ Once all records show green checkmarks, your Mailgun domain is fully verified! You can now proceed to integrate your Mailgun API key into GoHighLevel for email sending.

🔥 Pro Tip

If after 30-60 minutes some records still aren't verifying, meticulously re-check each entry in Google Domains against Mailgun's requirements. Even a single typo can prevent verification.

Troubleshooting Common Issues

⚠️ Mailgun DNS records not verifying after 15 minutes.
Double-check every record's hostname, type, and data for typos in Google Domains. Allow up to 1 hour for DNS propagation before trying to verify again.
⚠️ The second TXT record (DKIM) is not verifying.
Ensure you copied the *entire* hostname and data value for the DKIM record directly from Mailgun. This record is often long and complex; even a missing character will cause failure.
⚠️ MX records show an error or are not verifying.
Confirm both MX records have a priority of '10' and the correct data (`mxa.mailgun.org`, `mxb.mailgun.org`). Also, ensure the hostname matches your domain type (e.g., `@` for main domain).
⚠️ Emails sent from GoHighLevel are failing after Mailgun setup.
Verify that your Mailgun API key is correctly entered and saved in your GoHighLevel account. Also, confirm the Mailgun domain shows as 'Active' in Mailgun itself.
⚠️ My website or existing email stopped working after DNS changes.
Immediately review your Google Domains DNS records. You may have accidentally deleted or overwritten critical records unrelated to Mailgun. Revert any unintended changes or contact your web host/email provider.

Common Mistakes to Avoid

  • Using an incorrect hostname for your domain type (e.g., using `@` for a subdomain like `mg.yourdomain.com`).
  • Not copying the *full* second TXT (DKIM) value, leading to truncated or incomplete data for the record.
  • Forgetting to add both MX records or assigning an incorrect priority value (should be '10' for both).
  • Saving individual DNS records one by one instead of adding all five records and then performing a single save action in Google Domains.
  • Not waiting long enough for DNS propagation (can take up to an hour) before repeatedly attempting to verify in Mailgun.

Frequently Asked Questions

QWhat is the difference between a main domain and a subdomain hostname when adding records?
The hostname for a main domain (e.g., `yourdomain.com`) is typically represented by an `@` symbol in Google Domains. For a subdomain (e.g., `mg.yourdomain.com`), the hostname is just the subdomain part itself (e.g., `mg`). It's crucial to use the correct hostname for each record type to ensure proper configuration and Mailgun verification.
QWhy are there two TXT records required for Mailgun setup?
The two TXT records serve different, vital authentication purposes. One is for SPF (Sender Policy Framework), which identifies servers authorized to send email from your domain. The other is for DKIM (DomainKeys Identified Mail), which adds a digital signature to your emails. Both are essential for proving email authenticity and improving deliverability.
QHow long does DNS propagation typically take after saving records in Google Domains?
DNS propagation times can vary, but for most changes in Google Domains, it typically takes anywhere from a few minutes to an hour. In rare cases, it might take up to 48 hours. If records don't verify immediately in Mailgun, waiting 15-30 minutes and re-verifying is usually sufficient.
QWhat should I do if some Mailgun DNS records don't verify immediately after saving?
First, wait at least 15-30 minutes for DNS propagation, then click the **Verify DNS Settings** button in Mailgun again. If issues persist, meticulously re-check each entered value (hostname, type, data) in your Google Domains DNS settings against Mailgun's requirements for any typos or omissions. Even a small error can prevent verification.
QCan I use a different email service provider with GoHighLevel instead of Mailgun?
Yes, GoHighLevel offers flexibility. While Mailgun is a popular choice for its robust features and deliverability, GoHighLevel also has its own integrated email service, LC Email (LeadConnector Email), which often requires less setup. You can choose the provider that best fits your needs and technical comfort level for sending emails.
Try GoHighLevel Free

Start your 30-day GoHighLevel free trial

Everything in this guide is in your free trial. 30 days, no credit card — the platform behind 78+ revenue systems.

Start 30-Day Free Trial

Some links are affiliate links — if you sign up we may earn a commission, at no extra cost to you. We only recommend GoHighLevel because we build on it every day.

Arsalan Zaffar
Arsalan Zaffar
Revset Labs · Revenue Systems · 78+ GHL Builds

Arsalan writes GHL guides from real build experience — 78+ systems, $9.2M in client pipeline. Wharton, CXL & Google certified.

Connect on LinkedIn
Tags:GoHighLevel emailMailgun setupGoogle Domains DNSEmail deliverabilityDomain verificationGHL integrations