Current Date: 6 September, 2026

How to Use Gmail With a Custom Domain Name

You can use a custom domain with Gmail in one of two ways today: pay for Google Workspace and get a full you@yourbusiness.com Gmail account on your own email domain, or keep a free @gmail.com account and route your domain's mail through it with forwarding plus Gmail's "Send mail as" feature. A third option that used to work for free — pulling custom domain email into Gmail via POP — no longer does, because Google shut it down in January 2026. Which of the two remaining paths makes sense depends mostly on whether you need other people on the same domain and whether replying as that address matters to you.

Whether you're searching "how to use Gmail with custom domain", "gmail for domain", or the Dutch equivalent gmail eigen domain ("own domain"), the setup is identical — only the domain-management panel you're logging into differs by registrar. Here's what actually works right now, what changed, and how to set up each option.

What Changed in Gmail's Custom Domain Support

Two announcements from Google matter more to this topic than anything about Workspace pricing or DNS settings, and most existing guides on this topic don't mention either one.

Gmail's POP fetch for other accounts is already gone. Starting in January 2026, Google removed "Check mail from other accounts" — the setting under Gmail's Accounts and Import tab that let a free Gmail account periodically pull mail from a separate mailbox over POP3. That feature, combined with "Send mail as," used to be the entire free method for using Gmail with custom domain mail: your host's mailbox held the mail, and Gmail fetched it. Google's official notice on Gmailify and POP changes cites security as the reason — POP3 transmits credentials and message content without modern authentication, and Gmailify (the related feature that applied Gmail's spam filtering to outside accounts) was retired at the same time. Messages already pulled into Gmail before the cutoff stayed put; only new fetching stopped.

Gmail's outbound "Send mail as" for non-Google addresses is scheduled to end in January 2027. This is the feature that lets you compose a message in Gmail and have it go out showing you@yourdomain.com in the From field, even though you're typing inside a @gmail.com account. Google's help page on sending from a different address confirms this will stop working for third-party addresses — Yahoo, Outlook, iCloud, and custom domains alike — from January 2027, citing the same security rationale. It does not affect Google Workspace addresses or aliases, and receiving mail (including auto-forwarding into Gmail) is a separate setting that isn't part of this change. As of this writing, you can still use a custom domain with your free Gmail account for sending — it just has an end date attached to it now.

Put together, that leaves one setup that's permanently free but now sending-only unless paired with forwarding, and one paid setup that's unaffected by either change.

Method 1: Google Workspace (Full Custom Domain Gmail Account) — Gmail for Business

Google Workspace turns your custom domain into a real Gmail account — not a forwarding trick layered onto a personal inbox. This is the standard route for business email setup: your team logs into mail.google.com (or the Gmail app) with you@yourdomain.com credentials directly, and gets Gmail's full storage, spam filtering, admin controls, and access to Drive, Calendar, and Meet — plus cloud storage and collaboration features — under the same account. It's the closest thing to true email hosting built around Gmail's interface, and it's the setup Google itself markets as Gmail for business.

Direct cost: Business Starter runs $7 per user per month on an annual commitment (or roughly $8.40/month billed flexibly), with Business Standard and Business Plus above that for more storage and features. Google periodically runs short-term promotional pricing for new sign-ups, so treat any specific figure as a starting point to verify at Google Workspace's official pricing page rather than a fixed rate.

When this is the right call:

  • More than one person needs an address on the domain (support@, sales@, individual staff addresses).
  • You want mail, calendar, video calls, and shared drives under one admin console.
  • You don't want a setup that Google could change again — Workspace accounts weren't touched by either 2026/2027 deprecation.

Setup steps:

  1. Sign up at workspace.google.com and choose "I already own a domain" if you're connecting an existing one, rather than buying a new one through Google.
  2. Enter your business details — name, size, and the domain you're connecting.
  3. Create your admin user — this becomes your first you@yourdomain.com login.
  4. Complete DNS verification. Google gives you a TXT record (or, on some registrars, an HTML file or CNAME option) to add in your domain's DNS settings. Log into whichever service manages your domain's DNS — that might be your registrar (GoDaddy, Namecheap) or a separate DNS host (Cloudflare) — and paste the record in exactly as shown. Verification can take anywhere from a few minutes to a few hours depending on DNS propagation.
  5. Add Google's MX records and remove any conflicting MX records your domain already has (for example, from a previous hosting provider's email). Google's setup wizard lists the exact records to add — this step is where "receiving" gets switched over to Google's mail servers, and it's also where any old SMTP configuration or POP3 settings from a previous host need to be retired.
  6. Add SPF, DKIM, and DMARC records when Google's setup wizard prompts you to. These aren't optional extras: without them, mail sent from your domain is far more likely to land in recipients' spam folders, and DKIM specifically needs to be turned on inside the admin console, not just added to DNS. This is also where you'd configure any additional SMTP configuration if you're relaying mail from other apps or services through your domain.
  7. Activate Gmail and add any additional users or aliases your team needs.

Budget an hour or two for the whole process, most of which is waiting for DNS changes to take effect rather than active work.

Method 2: Free Custom Domain Email Through a Personal Gmail Account

If you only need one address and don't want a monthly bill, you can still use custom domain with free Gmail account access to send and receive you@yourdomain.com mail — it just takes two separate pieces now instead of one, because the old all-in-one POP method is gone. Either way, mail travels over a secure email connection — Gmail and Google Workspace both enforce TLS for delivery regardless of which method you use.

Receiving: set up forwarding at the mail-hosting level, not inside Gmail. Two common ways to do this:

  • If your domain already has email hosting (through your web host or registrar), create a mailbox or alias for the address you want, and set it to forward to your Gmail address.
  • If you have no hosting at all, a free email-routing service — Cloudflare Email Routing is the most commonly used — can forward mail sent to you@yourdomain.com straight to your Gmail inbox, using MX records pointed at that service instead of a real mailbox.

Sending: in Gmail, go to Settings → See all settings → Accounts and Import → Send mail as → Add another email address, enter the custom address, and verify it (Gmail emails a confirmation link or code to that address — which is why receiving has to be working first). Once verified, you can select that address from the "From" dropdown when composing.

This combination gets you the same practical result — mail lands in Gmail, and you can reply from your custom address — without paying for Workspace. The trade-offs: it's a single mailbox, not a multi-user setup; you're dependent on a third-party forwarding service staying free and reliable; and the sending half of this setup is the exact feature Google has said it will remove for third-party addresses in January 2027, so it isn't a permanent fix.

Method 3 (No Longer Available): POP Fetching Into Gmail

Older guides describe going to Settings → Accounts and Import → Check mail from other accounts, entering your domain's mailbox credentials and POP3 server details, and having Gmail periodically pull that mail in automatically — no forwarding setup required. This was the simplest free method, and it no longer works for new setups as of January 2026. If you already had it configured before the cutoff, previously fetched mail is still in your Gmail account, but new incoming mail stopped arriving through that path once Google turned it off. If you're still relying on this, migrate to the forwarding setup in Method 2 before you start missing mail — Google's own migration guidance points to forwarding or IMAP as the replacement, not a delayed cutoff.

Google Workspace vs. Free Forwarding: Which One Fits

  Google Workspace Free Forwarding + Send As
Cost From ~$7/user/month (annual) Free
Multiple users on one domain Yes Not really — one Gmail account per setup
Storage & apps Full Drive, Calendar, Meet included None beyond Gmail's normal storage
Setup time 1–2 hours (mostly DNS propagation) 30–60 minutes
Affected by the 2026/2027 changes No Sending half scheduled to end January 2027
Best for Businesses, teams, anyone who wants this to be a long-term setup Solo users or side projects testing a domain before committing

If you're setting this up for a business with any expectation of adding people later, Workspace is the setup that won't need to be redone. If you're testing a domain, running a personal project, or genuinely can't justify a monthly cost yet, the forwarding method works today — just don't treat it as permanent.

Troubleshooting Common Setup Issues

Domain verification won't complete. DNS changes can take up to 48 hours to propagate, though most registrars update within an hour. Double-check you added the TXT record to the exact domain (not a subdomain) and didn't leave extra characters or quotation marks that some DNS panels add automatically.

Mail stopped arriving after switching MX records. Old MX records pointing to a previous host can conflict with new ones. Remove the old entries rather than leaving both in place — mail servers don't reliably pick the "right" one when duplicates exist.

"Send mail as" verification email never arrives. This almost always means the receiving side isn't actually working yet — check that forwarding or Workspace mail delivery is confirmed working first, since the verification message is sent to the custom address itself.

Outgoing mail lands in recipients' spam. Missing or misconfigured SPF, DKIM, or DMARC records are the usual cause. These need to match exactly what your mail provider specifies, and DKIM in particular often requires a separate activation step beyond just adding the DNS record.

A Few Things Worth Clarifying

Google Workspace and Gmail aren't the same product. Gmail is Google's free consumer email service. Google Workspace is the paid, business-oriented product that includes a custom-domain Gmail account plus Drive, Calendar, Meet, and admin controls under one subscription — Workspace uses Gmail, but Gmail alone doesn't give you a custom domain.

Yes, you can still use Gmail with a custom domain for free. Forward your domain's mail to a free Gmail account and use Gmail's "Send mail as" feature to reply from that address — that's Method 2 above. What you can't do anymore is use Gmail's old POP-fetch method, since Google discontinued it in January 2026.

That free setup still works in 2026, specifically. A free Gmail account can send and receive custom domain email today through forwarding plus "Send mail as." The only method that's actually gone is POP fetching; the "Send mail as" half of the free setup is still active now and only has an end date attached for January 2027.

Frequently Asked Questions

Can I use any custom domain with Gmail? Yes, as long as you can access and edit that domain's DNS settings. You don't need to buy the domain through Google — an existing domain from any registrar works with both Workspace and free forwarding methods.

Will my custom domain email in Gmail stop working in 2027? Only the free forwarding method is affected, and only the sending half of it. Starting January 2027, Gmail's "Send mail as" feature will stop supporting third-party addresses, including custom domains connected to a free Gmail account. Receiving mail through forwarding is unaffected, and Google Workspace accounts aren't part of this change at all.

How much does Google Workspace cost for a custom domain email? Business Starter, the entry plan, is priced at $7 per user per month with an annual commitment as of 2026, with monthly (non-annual) billing running higher. Google adjusts pricing and promotions periodically, so check Google Workspace's pricing page for the current rate before signing up.

Can I use the Gmail app with a custom domain? Yes, on both setups. If you're on Google Workspace, the Gmail app works exactly like a normal Gmail account once you sign in with your you@yourdomain.com credentials. If you're using the free forwarding method, the Gmail app on Android and iOS supports the same "Send mail as" addresses you configured on desktop, so you can reply from your custom address on mobile too — the setup happens once in the browser and then applies everywhere you're signed in.

Admin

Author of this article.

Leave a Reply

Your email address will not be published. Required fields are marked *