Email forwarding for a custom domain: complete setup guide

Quick answer for custom domain email forwarding

Custom domain email forwarding setup: verify TXT, create printed aliases, publish MailerZ MX, delete leftover MX, probe each name from an unrelated mailbox, then print the address. That is the guide.

Best practice: hold unknowns, save the old MX set, no self-send, no backup leftover host.

Send-as after day plus one if a From must travel. Free cannot.

Stop if you need a suite. This guide will not become Vault.

MailerZ Free is one domain, three aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Google’s own Send mail as steps live in Google Gmail Help — Send mail from a different address. Workspace as a product is described on Google Workspace — product overview. Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol.

custom domain email forwarding guide: the real decision

People finish the dashboard and skip leftover delete.

They print the address before the probe.

They enable catch-all to skip the inventory.

Criteria: two public MX views, unique subjects in the destination, leftover list empty.

Technical mail flow for custom domain email forwarding

After cutover, senders hit MailerZ. Named aliases forward. Header From stays. SRS may rewrite the envelope.

During TTL split, some senders still hit the old host. That is why you saved the old set and why you probe twice.

Forms and cron are not inbound setup. They are send. Do them after inbound is honest.

Unknowns hold on Free. Do not promote harvests on day one.

MailerZ is inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP, not webmail, not an open relay. Unauthorized send is SMTP 550 / 550 5.7.1. Leftover MX is a hard stop. Self-send from Gmail to the same Gmail account can hide routing errors. Not SOC 2, not ISO 27001, not HIPAA.

custom domain email forwarding setup

Follow the clock. Skipping leftover delete is not a shortcut.

1. List printed local-parts and current public MX.
2. Save the old MX set. Lower TTL if you can.
3. Add and verify the domain on MailerZ.
4. Create named aliases. Map destinations.
5. Publish MailerZ MX. Delete leftover hosts.
6. Probe each name from another mailbox.
7. Update the homepage only after the probe.
8. Day plus one: probe again. Attach send-as only if needed.

Failure modes and proof

Footer first.

Leftover backup MX.

Self-send.

Catch-all day one.

SMTP into WordPress before inbound exists.

MailerZ workflow and product boundary

MailerZ is the operator in this guide. Related: email forwarding, features, delivery recovery, email routing lab.

Not IMAP. Unauthorized send 550 / 550 5.7.1.

Related pages: email forwarding, features, delivery recovery, and email routing lab.

custom domain email forwarding best practice

Free completes inbound on one domain and three names. Solo starts send. Confirm pricing. A failed cutover weekend costs more than Business.

Agencies reuse this clock per client.

MailerZ Free is one domain, three aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Field notes you can reuse

Keep old aliases a quarter after a rename.

Document reply owners.

Revoke SMTP when staff leave.

Check NS if edits do not publish.

Use troubleshooting for leftover MX.

Use delivery recovery for hops this layer stored.

Do not promise inbox placement after a clean cutover.

The definition article is what. This article is when.

Deeper field notes for custom domain email forwarding

The setup is a cutover, not a plugin

Custom domain email forwarding is finished when a stranger can send to a printed name and you can find that message in Gmail or Outlook without leftover MX still answering. It is not finished when a dashboard shows a green check. The green check is one record. Production is a public lookup plus an external probe. This guide is the cutover order.

Day minus one

List printed local-parts. List current MX and NS from a public view. Save the old MX set. Lower TTL if you can wait a day. Create the MailerZ domain. Verify TXT. Create the named aliases. Map destinations. Do not enable catch-all for a first production cut. Decide send-as: if you need it this week, pick a paid plan before you print “reply from hello@.” Free will receive and will not send as the domain.

Cutover hour

Publish the MailerZ MX set on the nameservers that answer. Delete leftover Google, Microsoft, Cloudflare routing, and registrar MX. Do not leave a “backup” host. Wait until public views agree — or accept that some regions lag TTL. Send a uniquely titled message from an unrelated provider to each printed alias. Confirm Header From and Gmail delivery. If a name fails, check leftover MX before you recreate the alias.

Day plus one

Probe again from a second network if you can. Check hold for a leftover you did not print. Do not promote harvest names. Attach send-as only for Froms you will use. Copy host, port, TLS. Send a test that is not a self-send. Watch for 550. Rotate if a secret leaked in chat.

The homepage change

Change the printed address only after the probe. Teams that update the footer first generate customer mail into a hole. If you must change the public string, keep the old alias for a quarter. Remap, do not delete, until the old invoices die.

Forms and cron

Contact forms that send as the domain need SMTP, not the host’s mail() to a leftover sendmail. Cron alerts need a From you created. Both need the paid send path if the From is the domain. Both fail closed with 550 if you stay on Free and try anyway. That is correct behavior.

Quarterly review

After a nameserver move, a plugin swap, or a staff departure, look up MX again. Confirm the alias list still matches the site. Revoke SMTP for people who left. Review the store. This is the same review as leftover-MX troubleshooting, not a new product.

When the guide says stop

If you need a hosted mailbox, Calendar, or Vault, stop and buy a suite. If you need a privacy mask, buy a privacy product. If you need bulk marketing, buy an ESP. Custom domain email forwarding is the receive hop — and optional thin send — around an inbox you already have. MailerZ is that hop. Start free on a domain you can break. Sign in if the zone already lives here.

A complete worked story

A launch that updated the footer first

A SaaS printed hello@ the morning they created a MailerZ domain and before they deleted registrar MX. Launch-day press wrote hello@. Half landed at the registrar toy, half queued. They spent the afternoon on leftover delete and TTL. The probe after lunch was clean. The morning copy was not coming back. The complete setup guide is the order they skipped: probe, then print. They now keep a runbook with day minus one on the first line.

Operator brief

A longer operator brief for custom domain email forwarding

Teams that bookmark Email Forwarding for a Custom Domain: Complete Setup Guide usually arrive after a missed invoice, a form that never notified anyone, or a migration that looked clean in one resolver. The useful brief is still boring. Name the store. Name the printed local-parts. Name the nameservers that actually answer. Publish one MailerZ MX set. Delete leftover hosts. Probe from a mailbox that is not the destination. Only then talk about custom domain email forwarding as a send-as, catch-all, or comparison problem.

MailerZ remains inbound MX plus authenticated SMTP around Gmail or Outlook. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. It is not a hosted mailbox, not IMAP, not webmail, and not an open relay. Unauthorized send is 550 / 550 5.7.1. Free cannot finish send-as: SMTP and API stay off. Solo is $40 per year when the domain From must travel. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm the live pricing page. Those numbers are ceilings, not an inbox-placement service-level agreement.

If leftover Google, Microsoft, Cloudflare routing, or registrar MX is still public, stop widening custom domain email forwarding. The map you built never saw that copy. Priority numbers are an order, not load balancing. A higher preference host is idle while a leftover host still accepts mail. Save the old MX set before you delete anything. Check more than one public view because TTL lies.

Catch-all forward is not a safety feature for email forwarding for a custom domain complete setup guide. Hold unknowns on everyday production. Review the store. Promote a leftover only when a real person used it. Paid forward belongs to a dated cutover. Fan-out of unknowns into two inboxes trains two spam buttons. Plus addressing on Gmail is not a custom-domain unknown policy. MailerZ will not strip plus tags on your domain the way Gmail does on @gmail.com.

Send-as is a second hop. Creating an inbound alias does not approve outbound. Catch-all does not mint a From. Copy the dashboard host, port, and TLS pair together. Set From to an identity you created. Do not paste a Gmail password into a CMS, a cron file, or a ticket. Do not mail SMTP secrets to support. Send a 550 line, a timestamp, and a Message-ID. Rotate if a secret already leaked.

Self-send from Gmail to the same Gmail account can short-circuit. That green result is why people swear custom domain email forwarding works while customers vanish. Use a second provider. Put a unique subject on the probe so delivery history is searchable. If Header From was rewritten by some other forwarder, authentication stories get noisier. MailerZ does not rewrite Header From on inbound.

Agencies should keep custom domain email forwarding per client zone. Separate SMTP credentials. Do not pour every client into one catch-all because the spreadsheet got long. Agency plan capacity exists so you can hold more domains and aliases. It does not replace a named list. Offboard means delete MX you own, revoke SMTP, and stop forwarding leftovers into the agency inbox.

Legal and security questions have published answers on the security, privacy, terms, DPA, and subprocessors pages. MailerZ is not SOC 2, not ISO 27001, and not HIPAA. The 14-day Free store, the 90-day Solo–Agency store, and the 180-day Unlimited store are recovery windows for hops this layer saw. They are not an archive and not legal hold. If counsel wants eDiscovery, buy eDiscovery.

Comparisons only help after the hop is honest. Cloudflare Email Routing is inbound routing. A privacy-mask product hides a destination on a provider domain. A suite hosts mailboxes, Calendar, and admin. Proton-class mailboxes encrypt a store. MailerZ is the delivery layer when you already have Gmail or Outlook and you need a domain route you can prove. Cite the other product’s documentation. Do not invent feature parity.

When Email Forwarding for a Custom Domain: Complete Setup Guide is closed, the next physical action is a lookup and a probe, not another tab. Start free on one domain you can break. Sign in if the zone already lives here. Review quarterly, or sooner after a nameserver move, a plugin swap, or a staff departure. That is how custom domain email forwarding stays a runbook instead of an incident.

A second worked pass for custom domain email forwarding: write the last change on a sticky note before you open the dashboard. Nameserver move, leftover MX, new form plugin, contractor laptop, or a registrar forwarding toggle are the usual five. MailerZ history only shows hops that reached this layer. If the sticky note says leftover MX, you do not have a custom domain email forwarding mystery. You have a split. Delete the leftover. Wait for TTL. Probe again.

A third worked pass: print the public list. If you cannot print it, you are not ready for production unknowns and you are not ready for a bigger alias ceiling. Unlimited aliases as marketing will not save a missing list. Three named aliases on Free are enough to stop printing a personal Gmail on a homepage. Grow the list when a real person used a leftover, not when a harvest guessed admin@.

More working detail

A printed checklist for the person at the keyboard

Before you touch DNS: printed names listed, destinations exist and can log in, old MX saved, verify TXT shows on the nameservers that answer, aliases created, catch-all off, send-as decision written (Free receive-only or paid this week). During DNS: MailerZ MX published, leftover hosts deleted, no backup leftover, two public views opened. After DNS: unique subject from another provider to each name, Header From checked, history checked, homepage updated only if probes passed, old public names kept if you renamed.

Hand that list to whoever has the registrar password. Do not hand a philosophy. Custom domain email forwarding fails when the person with the password improvises a backup MX because “we might need to roll back.” Rollback is republishing the saved old set, not leaving both live. Both live is split brain, not rollback.

If marketing wants the footer live at 9:00 and DNS is at 9:30, the footer waits. If legal wants the old address alive for invoices, keep the alias. Those are setup decisions. They are not product limitations.

After a plugin swap, run the after-DNS block again even if you did not touch MX. Forms that start sending as the domain are a new send-as job. After a nameserver move, run the during-DNS block because you may have restored leftovers from a template. The complete guide is reusable because the ghosts repeat.

Stop and buy a suite if the checklist grows Calendar, Vault, and device management. The guide will not absorb those rows. MailerZ will not either.

One more working distinction

Rollback that is actually a rollback

If you must roll back in the first hour, publish the saved old MX set and delete MailerZ MX, or leave MailerZ only if you want split brain. Do not add both. Tell senders that TTL still applies — some will stay on MailerZ for the old TTL. Probe both worlds if you truly run both, and admit you are not in the complete setup anymore. You are in an incident. Custom domain email forwarding setup assumes one public answer.

After a successful week, delete the rollback note from the homepage plan. Keep the saved old set in the runbook for a quarter. Registrar templates love to resurrect leftovers during a nameserver clone. The complete guide’s quarterly row exists because of those templates.

If a contractor did the cutover and left, the next person still needs the saved old set, the alias list, and the destination logins. Setup is not finished until those three live outside one human’s laptop.

A short operating rule

Who is allowed to click Publish on MX

One person. Custom domain email forwarding setup fails when marketing, a contractor, and a registrar chatbot all publish a host. Write the name in the runbook. If that person is out, delay the cutover. A late footer is cheaper than two MX editors in the same hour.

FAQ

What is the safest way to handle custom domain email forwarding?

Inventory printed names, verify the domain, create aliases, publish one MailerZ MX set, delete leftover hosts, and probe from another mailbox before you change the homepage. Catch-all is not day one. Send-as is a later paid hop.

Does this require a new mailbox?

No. MailerZ is not IMAP and not webmail. Gmail or Outlook remains the store unless you separately buy a hosted mailbox product.

Will it work with Gmail or Outlook?

Yes for inbound when the destination is a verified mailbox. Branded replies need paid send-as plus Gmail Send mail as or a manual Outlook SMTP identity. Free has no send-as.

What DNS records are involved?

A verification TXT, one MailerZ MX set on the authoritative nameservers, leftover host MX removed, and SPF, DKIM, and DMARC if you also send as the domain.

What should I test before production?

Send a uniquely titled message from an unrelated provider into each named alias. Confirm Header From and delivery history. Do not email yourself from the same Gmail account.

Key takeaways

• Cutover, not plugin.
• Inventory first.
• Delete leftovers.
• Probe before print.
• No self-send.
• Hold unknowns.
• Send later.
• Review quarterly.

Conclusion and next action

Finish custom domain email forwarding when a stranger reaches a printed name and leftover MX is gone. MailerZ is the hop. Start free on a domain you can break.

Sign in if the dashboard is green and public MX is still the old host.

Review quarterly, or sooner if Gmail, Workspace, or MailerZ scope changes. Author: MailerZ editorial, Secuno LLC.