Email Forwarding for a Custom Domain: Setup and Pitfalls

Forwarding is the oldest trick in custom-domain email, and for many people it’s still the right one. You keep reading mail in the Gmail or Outlook.com inbox you’ve used for years, and the outside world sees a tidy [email protected]. Setup takes about fifteen minutes. The catch shows up later, when you hit “reply”.

How email forwarding for a custom domain works

When someone writes to [email protected], their mail server looks up the MX record of your domain (the DNS entry that says where mail goes). With forwarding, that MX record points to a forwarding service. The service accepts the message and immediately sends it on to the address you chose, for example [email protected].

Nothing is stored in between. There’s no mailbox at the forwarding service, just a rule.

Sender ──> MX of yourdomain.com ──> forwarding service ──> [email protected]

Where to get forwarding

Whichever you use, the DNS side is the same: MX records point to the service, and an SPF record allows it to handle mail for your domain.

The DNS records for forwarding

A typical set, with example hostnames (your service shows the real ones):

yourdomain.com.   3600  IN  MX   10 mx1.forwarder.example.
yourdomain.com.   3600  IN  MX   20 mx2.forwarder.example.
yourdomain.com.   3600  IN  TXT  "v=spf1 include:spf.forwarder.example ~all"
yourdomain.com.   3600  IN  TXT  "forwarder-verification=8f2c1a"

The number before the hostname is the priority. Lower numbers are tried first, higher numbers are backups.

One rule matters: only one SPF record per domain. If you already have one, for a newsletter tool for example, add the new include: into the same line instead of creating a second TXT record starting with v=spf1.

Aliases, catch-all and multiple recipients

An alias is an address that exists only as a forwarding rule. Common setups:

[email protected]     -> [email protected]
[email protected]  -> [email protected]
[email protected]      -> [email protected], [email protected]

The third line shows one alias delivering to two people. That’s the cheap way to run a shared address for a club or a two-person business. Our guide on a domain for a club uses exactly this pattern for role addresses like secretary@.

A catch-all forwards mail to any address at your domain, even ones you never created. Some people like it so they can hand out [email protected] per online shop. It also catches every spammer who tries admin@, sales@ and ceo@. If you use it, combine it with filters.

Why forwarded mail sometimes lands in spam

Forwarding has a technical weakness. When the forwarding service passes on a message from, say, [email protected], the receiving inbox sees a server that isn’t listed in bigcompany.com’s SPF record. Strictly speaking, SPF fails.

Two things fix this in practice:

• SRS (Sender Rewriting Scheme). The forwarding service rewrites the envelope sender, the technical return address, to one of its own, so SPF passes. Good forwarding services do this automatically.
• DKIM. If the original sender signed the message, the signature survives forwarding unchanged as long as the content isn’t modified.

If you still see forwarded messages in spam, check whether the service uses SRS and mark a few messages as “not spam” so the inbox learns.

The sending problem

Forwarding only handles incoming mail. When you reply from Gmail, the recipient sees your Gmail address unless you configure a custom sender. Gmail calls this “Send mail as”. It requires an SMTP server, the outgoing mail server, that’s permitted to send for your domain.

Options:

1. A forwarding service plan that includes SMTP.
2. A hosting mailbox you only use for its SMTP login.
3. A full mailbox at a mail provider.

The Gmail custom domain guide walks through the “Send mail as” settings click by click. Gmail’s own POP fetching from other accounts, “Check mail from other accounts”, was announced to end on Gmail’s website from January 2026, which makes forwarding the more reliable route for getting domain mail into Gmail.

Forwarding at the mailbox vs forwarding at the domain

People mix up two different things:

If you already have a hosting mailbox, you can add a forwarding rule there and keep a copy as backup. If you have no mailbox at all, domain-level forwarding is the way.

When forwarding isn’t enough

Forwarding is fine for:

• A personal address on your own domain
• A side project or club
• Testing a new domain before you commit to a mail provider

It starts to hurt when:

• Several people need to send from the same address and see each other’s replies
• You need sent mail stored centrally for record-keeping
• You send a lot of mail and need full control over DKIM signing

Then a real mailbox makes more sense. The comparison in email with your own domain lists the options and their costs.

Testing your setup

Check the MX records from a terminal:

dig MX yourdomain.com +short

You should see the forwarding service’s hostnames. Then send a test from a different account (not the one you forward to, because Gmail sometimes hides messages that you sent to yourself), and check the spam folder.

Don’t have the domain yet? See whether yourname.email is free, compare classic endings on the .com page, or browse the betadomain price list for something short.

Step by step

1. Choose a forwarding serviceUse your registrar's or web host's forwarding feature if it has one, or a dedicated forwarding service.
2. Add the domain and verify itEnter your domain at the service and add the TXT verification record it shows you.
3. Point the MX records to the serviceAt your registrar, replace existing MX records with the ones the forwarding service lists.
4. Add the SPF recordAdd or merge the service's SPF include so forwarded mail passes checks.
5. Create aliasesSet up addresses such as hello@ and invoices@ and point each one to your real inbox.
6. Test from a different accountSend a message from another mailbox, check it arrives, and look in the spam folder too.