Custom Domain Email DNS: MX Checklist Before You Send

Custom domain email DNS is the part most freelancers skip until mail bounces. You buy you@yourdomain.com, open the inbox, send a test—and nothing arrives because MX records still point at a parked host, an old cPanel box, or two providers at once.

This page is Record-Then-Test. It is not Namecheap email vs Google Workspace (which mailbox product to buy—early-link that owner first). It is not Namecheap vs GoDaddy (registrar checkout). It is not domain name mistakes (naming traps).

Write the provider’s MX values. Remove conflicting hosts. Propagate. Then send a real test.

Official: Set up MX records for Google Workspace · Namecheap: Google Workspace on Namecheap DNS · Namecheap Private Email records (third-party DNS) (confirm live pages—values and UI change).

Disclosure: Namecheap and Google Workspace are third-party products. Pricing and DNS templates change. This is a checklist, not a guarantee of deliverability.

Table of contents

1. Record-Then-Test
2. Pick the mailbox, then the zone
3. MX checklist (any provider)
4. Google Workspace MX notes
5. Namecheap Private Email MX notes
6. Test before you announce the address
7. FAQ
8. Finish DNS tonight

Record-Then-Test

        RECORD-THEN-TEST
  1. ZONE     → find who hosts DNS (nameservers), not only who sold the .com
  2. RECORD   → paste MX (and required TXT) from the live provider doc
  3. CLEAN    → remove leftover MX pointing at old hosts
  4. WAIT     → allow propagation (minutes → sometimes up to ~72h)
  5. TEST     → external send + provider dig/Check MX tools

Skipping step 3 is the classic failure: new MX added, old MX left, mail splits or fails. Record-Then-Test treats cleanup and verification as part of setup—not optional polish.

Pick the mailbox, then the zone

Choose the product on Namecheap email vs Google Workspace. Then ask: where do the nameservers point?

Registrar choice (Namecheap vs GoDaddy) matters for checkout and renewals. Mail routing follows the DNS zone, not the shopping cart.

MX checklist (any provider)

Use this order every time:

1. Verify domain ownership with the email provider (TXT or CNAME as their wizard shows).
2. Copy MX hostnames and priorities from the provider’s current help article—do not invent values from memory.
3. Set Mail Settings / Custom MX (or equivalent) and add each MX row.
4. Delete conflicting MX that still name parked, webmail, or previous hosts.
5. Add SPF (and DKIM/DMARC when the provider supplies them) so outbound mail can authenticate.
6. Save, wait for propagation, then test inbound and outbound.

MX answers: “Where should other servers deliver mail for this domain?” SPF/DKIM answer a different question: “Should receivers trust mail claiming to be from this domain?” Do both jobs; do not confuse them.

Google Workspace MX notes

Google Workspace Help currently documents a primary MX destination of smtp.google.com with priority 1 (confirm live Help—Google has also documented legacy multi-host sets that may still work if already present).

Practical notes from Google + Namecheap Knowledgebase:

• Remove other MX records so only the intended Google hosts remain.
• On Namecheap Advanced DNS, Namecheap’s guide often recommends Custom MX with SMTP.GOOGLE.COM / priority 1 rather than relying on a broken preset template—confirm their live article.
• Activate Gmail in the Google Admin console after DNS is set.
• Propagation can take time; Google notes recognition can take up to about 72 hours in some cases.

Do not mix Private Email MX hosts and Google MX hosts on the same domain unless you intentionally run a complex split (most solo blogs should not).

Namecheap Private Email MX notes

For Namecheap Private Email, Namecheap’s third-party DNS guide lists MX hosts such as mx1.privateemail.com and mx2.privateemail.com (priority commonly 10—confirm live KB). They also document SPF TXT values and additional records for webmail / autodiscover.

If the domain uses Namecheap DNS, Mail Settings may offer a Private Email template—still verify the published records after save. If nameservers are elsewhere, create the same records in that zone.

For “why can’t I send or receive?” troubleshooting, Namecheap’s email KB walks MX checks and authentication separately—use that when tests fail.

Test before you announce the address

Do not print the address on invoices until these pass:

If inbound fails, re-check nameservers first—editing the wrong zone is common after a host or Cloudflare move. If outbound fails but inbound works, prioritize SPF/DKIM from the provider guide.

FAQ

What is an MX record?

An MX (mail exchanger) record tells other mail servers where to deliver email for your domain. Without correct MX values pointing at your provider, inbound mail may bounce or land in the wrong place.

Is this Namecheap vs Google Workspace?

No. The mailbox product split lives on Namecheap email vs Google Workspace. This page is the DNS/MX checklist after you choose a provider.

Where do I edit MX if nameservers are elsewhere?

Edit DNS at the provider that hosts your nameservers—not always the registrar checkout. If Cloudflare (or another DNS host) holds the zone, add MX there.

Can I keep old MX records for “backup”?

Usually no. Conflicting MX hosts confuse delivery. Google Workspace MX Help says to remove other MX records when you point mail at Google. Confirm live provider docs for your setup.

Is MX enough to send reliably?

MX mainly routes inbound mail. Outbound reputation also needs authentication records (SPF, and often DKIM/DMARC) from your provider’s guide. Set those after MX works.

How long until MX changes work?

Often minutes to a few hours; Google notes DNS changes can take up to about 72 hours to be recognized everywhere. Test with your provider’s tools before you announce the address.

Where are official setup pages?

Google Workspace MX setup, Namecheap Google Workspace DNS, and Namecheap Private Email third-party DNS. Confirm live values before you save.

Finish DNS tonight

1. Confirm mailbox choice on the comparison owner.
2. Note current nameservers.
3. Paste MX from the live provider doc; delete leftovers.
4. Add SPF (and DKIM when ready).
5. Wait, then send one external test both ways.

Mail that works is boring DNS done once. Record-Then-Test keeps it boring on purpose.