Home/HighLevel/Features/Email/HighLevel guide: configure Mailgun with Google Domains

Conversations and Inbox

HighLevel guide: configure Mailgun with Google Domains

In short

Mailgun can be linked to a domain that you manage in Google Domains by adding five DNS records. The process includes creating a Mailgun account, choosing a main domain or subdomain, entering SPF, DKIM, MX and CNAME entries, then verifying the settings so email can be sent through HighLevel without interrupting existing Gmail service.

AreaEmail · MailGun
Used forDigital marketing agency, SaaS startup, Online retailer
Setup steps28 steps in 7 tasks
Last updatedNovember 16, 2026

01Who this is for

  • Marketing agencies that send bulk campaigns and need a dedicated sending domain to protect client inboxes.
  • SaaS Founders who want to route transactional emails through Mailgun while keeping their primary domain for Google Workspace.
  • Ecommerce owners who require reliable delivery for order confirmations and prefer to use a subdomain for mail services.

02Mailgun DNS records, explained

The feature lets you point a domain or subdomain you own in Google Domains to Mailgun’s email infrastructure. When the DNS entries are correct, Mailgun handles SPF, DKIM and MX routing for the chosen domain. The platform shows a green check for each record once propagation is complete, allowing you to send and receive email through HighLevel’s conversation view. All configuration lives in the Mailgun dashboard (Sending > Add New Domain) and the DNS editor of Google Domains (domains.google.com > DNS). The records consist of two TXT entries, two MX values combined in one record, and a single CNAME entry.

03How businesses use Mailgun DNS records

  • Digital marketing agency. The agency creates a subdomain like mg.agency.com in Mailgun, adds the required records in Google Domains, and then links the API key in HighLevel. This lets the agency send client newsletters without affecting their Google Workspace email.
  • SaaS startup. The startup registers a subdomain such as email.app.com, follows the DNS steps, and verifies the domain in Mailgun. After adding the API key to HighLevel, the app can deliver welcome and password reset emails while keeping its main domain for employee Gmail accounts.
  • Online retailer. The retailer adds a subdomain like orders.store.com, configures the SPF, DKIM, MX and CNAME records in Google Domains, and verifies the setup in Mailgun. HighLevel then routes order confirmation emails through Mailgun, preserving the store's primary domain for customer support email.

04The numbers and rules that matter

  • Two TXT records: SPF (v=spf1 include: Mailgun.org ~all) and DKIM (longer TXT value).
  • Both MX values: 10 mxa.mailgun.org and 10 mxb.mailgun.org.

05Before you start

  • A Mailgun account must be created and the email address verified.
  • The domain to be used must be managed in Google Domains and you must have edit access to its DNS settings.
  • Decide whether to use the root domain or a subdomain and ensure the choice is set in the US region.

06How to set up and use Mailgun DNS records in HighLevel

Sign up for Mailgun and add your domain

  1. Register at Mailgun.com and confirm the account via the verification email.
  2. Log in to Mailgun and open Sending > Add New Domain.
  3. Select either the root domain or create a subdomain such as mg.example.com, following guidance about sharing a domain.
  4. Make sure the domain is created under the US region, then click Add domain.

Access DNS records in Google Domains

  1. Sign in at domains.google.com.
  2. Click the domain you intend to configure.
  3. Select DNS from the left navigation panel.

Add the 1st TXT record (SPF)

  1. Press Create new record.
  2. Enter the host name: use mg, replies, or @ for the root domain.
  3. Choose TXT from the Type dropdown.
  4. Paste v=spf1 include:mailgun.org ~all into the Data field; do not save yet.

Add the 2nd TXT record (DKIM)

  1. Press Create new record.
  2. Set the host name to the portion before the subdomain in the DKIM value.
  3. Select TXT as the record type.
  4. Paste the longer DKIM TXT string into the Data field.

Add the MX records

  1. Press Create new record.
  2. Enter the appropriate host name (mg, replies, or @).
  3. Choose MX from the Type options.
  4. Add the value 10 mxa.mailgun.org.
  5. Click +Add more and add the value 10 mxb.mailgun.org to the same record.

Add the CNAME record

  1. Press Create new record.
  2. Enter the host name as email.<prefix> (email.mg, email.replies, or email for the root).
  3. Select CNAME as the record type.
  4. Paste mailgun.org into the Data field.

Verify DNS and finish setup

  1. After all five records are entered, click Save.
  2. Return to the Mailgun dashboard and click Verify DNS Settings.
  3. If any record does not show a green check, wait for propagation and click Verify again.
  4. When all checks are green, copy the Mailgun API key, add it to HighLevel email service settings, and send a test email.

07What it looks like in HighLevel

08Settings that matter

  • Host name. Specifies the prefix that identifies the subdomain or root for each DNS entry.
  • Type. Determines the DNS record category such as TXT, MX or CNAME.
  • Data. Contains the value that Mailgun requires for SPF, DKIM, MX routing or CNAME target.

09Things to know before you rely on it

  • Domain creation must be performed in the US region; the EU region is not supported for this setup.
  • If you keep Gmail on the root domain, use a subdomain for Mailgun to avoid disrupting existing Google Workspace MX records.
  • Google Domains stores both MX values in a single record using the +Add more option.
  • Propagation can take a few hours; records may not immediately display a green check in Mailgun.

10If something goes wrong

  • DNS records do not show a green check in Mailgun. Wait for propagation, then click Verify DNS Settings again.
  • Saving after the first record slows the process. Add all five records before clicking Save to avoid repeated page reloads.

11How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Mailgun DNS setup is useful but not essential for everyone. If you already have a reliable email provider, skip it.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 16, 2026

Common questions

Common questions about Mailgun DNS records.

Why does Google Domains only need one MX record instead of two?

Google Domains lets you add multiple values to a single MX record using the +Add more option, so both Mailgun MX entries live under one record.

Will using a subdomain for Mailgun affect my existing Gmail service?

No. Keeping Gmail MX records on the root domain and adding Mailgun records to a subdomain leaves current Google Workspace delivery unchanged.

What priority should I use for the Mailgun MX entries?

Enter 10 before each MX value, for example "10 mxa.mailgun.org".

How long can DNS propagation take in Google Domains?

Propagation is usually fast but can occasionally require a few hours before Mailgun shows a green check.

Do I need to save after adding the first DNS record?

You can save at any point, but adding all five records before saving reduces the need to reopen the DNS page.

What should I do after all records are verified?

Copy the Mailgun API key, paste it into HighLevel’s email service settings, and send a test email to confirm delivery.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.