Email forwarding Namecheap DNS means Advanced DNS on the authoritative zone, MailerZ MX only, leftovers deleted, and a re-query after Namecheap’s email or website tiles republish records. It is not Private Email plus MailerZ. It is not parking MX left beside a new hop. It is not Domain Connect theater on a zone the world does not use. Exclusive MX. Two resolvers. Foreign probe. Filename screenshots with the zone.
Quick answer for email forwarding namecheap dns
Confirm public NS. Add the domain in MailerZ. Paste verification TXT and MX from the dashboard into Advanced DNS. Delete every other MX. Product path: docs, tools, troubleshooting, migration planner. MX is IETF RFC 5321 — Simple Mail Transfer Protocol. Names are IETF RFC 1035 — Domain names. Domain Connect explainers such as Forward Email’s Domain Connect page are research, not our wizard.
Confirm pricing. Free: 1 domain, 3 aliases, 14-day store, HOLD, no send-as. Solo $40/yr. Starter $8/$80. Business $19/$190. Agency $39/$390. No inbox SLA. Not SOC 2.
Helpful DNS pages name the panel you edited: people-first content.
The user problem and the decision criteria
Namecheap offers email products that publish MX for you. Operators then add MailerZ MX “as well.” Senders split. Self-send looks fine. The useful cut is Advanced DNS with one owner. The useless cut is two products that both think they own mail.
| Question | If yes | If no |
|---|---|---|
| Do public NS match the panel? | You can edit. | Theater zone. Stop. |
| Any non-MailerZ MX left? | Leftover MX. Delete. | You can probe. |
| Private Email still sold on the domain? | Expect republish. Disable it. | Still re-query after website saves. |
| Aliases built before the cut? | Good. | Maps first. Then MX. |
| Self-send only? | Invalid gate. | Foreign probe. |
Technical mail flow
Senders ask the public NS for MX. Those NS must be the ones Namecheap documents for the zone you edited—or Cloudflare, or whoever actually serves the name. Editing Basic DNS while NS point elsewhere is theater. IETF RFC 1035 — Domain names does not care which UI you liked.
Envelope SRS on the hop. Header From untouched. Destination Gmail still sees the sender. Leftover Google or Private Email MX means some senders never reach MailerZ. IETF RFC 5321 — Simple Mail Transfer Protocol picks one MX set, not a compromise.
Step-by-step setup and decision path
Query NS from two resolvers
If they are not Namecheap, edit the real host. Do not fight the registrar UI.
Add the domain and create aliases
Old MX stays exclusive until maps exist.
Advanced DNS: TXT + MailerZ MX only
Copy dashboard hostnames. Do not invent priorities as load-balancing.
Delete leftover MX and forwarding products
Private Email, parking, Google, old host. Filename the screenshot with the zone.
Foreign-probe every printed alias
Unique subjects. History 250. Destination search.
Re-query after the next Namecheap save
Email tiles republish. Monday after launch. Then after website edits.
Failure modes and proof
| What you see | Likely cause | Proof |
|---|---|---|
| Some senders hit Private Email | Leftover MX | Second resolver |
| Panel looks exclusive, world does not | Theater NS | NS query |
| MX returned after a weekend | Email product republish | Dated re-query |
| TXT verify fails | Quoting or hostname | Next article in this cluster |
| 250 empty inbox | HOLD, filter, wrong Gmail | Recovery |
| 550 on send-as | Free or unmapped From | Plan, not DNS |
Proof is NS, exclusive MX on two resolvers, a zone-named screenshot, and foreign probes. A Namecheap green check is not exclusive MX.
MailerZ workflow and product boundary
Inbound MX plus authenticated SMTP. Envelope SRS. Header From never rewritten. Not IMAP. Not Namecheap Private Email. Not an open relay. Unhosted send is 550 5.7.1.
Free: 1/3/14-day/HOLD/no send-as. Solo $40/yr. Starter $8/$80. Business $19/$190. Agency $39/$390. Confirm pricing. No inbox SLA. No SOC 2.
Cost, alternatives, and trade-offs
| Choice | What you get | What you give up |
|---|---|---|
| MailerZ + Advanced DNS | A hop you can recover | The email-product tile |
| Namecheap Private Email | Their mailbox. Quote live | Gmail as the store |
| Both MX sets | A split | A cut you can explain |
| Workspace on the same zone | A suite. Quote Google live | MailerZ as inbound owner |
Time is a line item. Deleting leftovers once costs less than a month of split senders. Domain Connect can speed TXT/MX paste. It cannot excuse a leftover row.
Advanced DNS versus email product
Advanced DNS is where you type records. The email product is a merchant flow that writes MX for you. Operators who “set up email” in the product and “set up MailerZ” in Advanced DNS created leftover MX on purpose. Disable or unused the product. Keep Advanced DNS exclusive.
Parking pages sometimes publish MX that accepts and blackholes. That is still leftover MX. Delete it. Null MX is a different, explicit reject—do not invent it to “pause” a cut.
Website saves republish MX
Website builders and email upsells rewrite zone files. After anyone clicks those tiles, query MX again. Filename the new screenshot. If leftovers returned, delete them again and write the date on the sheet. This is the Namecheap-specific version of leftover MX, not a new physics.
TTL does not make dual MX safe. Dual MX is leftover even at 60 seconds.
Theater zones
If NS are Cloudflare, edit Cloudflare. If NS are a host, edit the host. Namecheap Advanced DNS on a parked UI while Cloudflare serves the name is how you “set MX” and change nothing. Confirm NS first. Every time.
Two-factor on destinations. HOLD review. IPv6 failures after exclusive names exist are host problems. Night operators who add Google MX “as backup” recreate leftover MX. Write exclusive on the ticket.
If a second operator needs the order, send this page plus leftover MX troubleshooting. NS. Advanced DNS. MailerZ only. Delete extras. Two resolvers. Probe. Re-query after saves.
The artifacts that close email forwarding Namecheap DNS are matching NS, exclusive resolver listings, and probes. Everything else is a tile you clicked.
Field notes for Namecheap Advanced DNS
NS first, always
Namecheap can be the registrar while Cloudflare or a host answers the name. Editing Advanced DNS on a theater zone changes a diary, not the public MX. Query NS from two resolvers before you paste anything. If NS are not Namecheap, stop. Edit the host that answers. Domain Connect helpers are research, not a substitute for that check.
RFC 1035 does not care which tile you liked. The nameservers that answer are the typewriter that matters.
Private Email is a second inbound owner
Namecheap Private Email and similar tiles publish MX for you. Adding MailerZ MX “as well” is leftover MX on purpose. Senders split. Self-send from Gmail can look fine. Disable or unused the email product. Keep Advanced DNS exclusive: verification TXT plus the MailerZ MX set from the dashboard. Delete parking MX that blackholes. Null MX is a different, explicit reject — do not invent it to pause a cut.
Priority numbers are an order, not load balancing. A leftover host with preference 1 still wins if it accepts mail.
Website and email saves republish
Website builders and email upsells rewrite zone files. After anyone clicks those tiles, query MX again at 8.8.8.8 and 1.1.1.1, then at authoritative NS. Filename screenshots with the zone and the date. If leftovers returned, delete them again and write the date on the sheet. TTL does not make dual MX safe. Dual MX is leftover even at sixty seconds.
Split caches after a correct exclusive cut are TTL. Same leftover on both public views means unfinished config or the wrong panel. See the resolver comparison article for that classification. Do not add Google MX to “help propagation.”
Maps before the cut
Create named aliases while the old MX is still exclusive. Then paste MailerZ MX and delete leftovers. Cutting first with an empty map holds or bounces printed names. Free holds unknowns and has three aliases. Confirm pricing. Foreign-probe every printed alias with a unique subject. Search the destination including spam. Header From intact.
TXT verification is not MX. Both may be required. Quoting and hostname mistakes are a sibling article. Do not fight verify by adding a second MX owner.
Send-as is not a Namecheap DNS row
GoDaddy-style or Namecheap “SMTP” from a mailbox product you do not own is not MailerZ send-as. Paid MailerZ send-as is a dashboard pair on a paid plan. Free 550 is honest. SPF, DKIM, and DMARC belong to the sending hop you actually use. Two SPF records are a permerror. Authentication is not encryption.
Agencies and shared logins
Per-client Namecheap login. A template that restores Private Email MX on every zone is how client B inherits client A’s leftover. Offboard means delete MX you own and revoke SMTP you issued. Agency capacity does not merge DNS.
Two-factor on destination Gmail. HOLD review. Night operators who add Google MX as backup recreate leftover MX. Write exclusive on the ticket.
Worked story: a founder enabled Private Email, then pasted MailerZ MX. Preference favored Namecheap’s host. MailerZ history stayed quiet. They disabled Private Email, deleted leftover MX, probed from another mailbox, and the next lead showed a history row. The courtesy dual list was the outage.
Second story: another team edited Namecheap DNS for three evenings while public NS was Cloudflare. Nothing moved. They published exclusive MailerZ MX on Cloudflare, deleted leftovers there, and the probe landed. The registrar panel was a diary.
Operator brief: confirm NS, build aliases, Advanced DNS TXT and MailerZ MX only, delete Private Email and parking leftovers, two public resolvers, foreign probe, re-query after the next Namecheap save. MailerZ is inbound MX plus authenticated SMTP. Not IMAP. Not Private Email. Not SOC 2. Start free on one domain and keep the listing exclusive.
Related: docs, tools, troubleshooting, leftover MX, how long MX changes take, GoDaddy MX mistakes if you also operate that registrar, and pricing. Keep zone-named screenshots in the ticket.
Operator packet for a Namecheap exclusive cut
Pre-cut checklist you can print
Public NS from two resolvers. Confirmation that Advanced DNS is the zone those NS serve. Alias list built in MailerZ. Old MX saved as text and a screenshot named with the zone. Private Email and parking tiles noted as on or off. Website builder access listed so you know who can republish. Third-mailbox ready. Unique subject pattern written.
If NS are Cloudflare, stop and open Cloudflare. If NS are a host, open the host. Namecheap as registrar only is not Namecheap as DNS. Theater zones waste evenings.
During the cut
Paste verification TXT exactly. Paste MailerZ MX exactly. Delete every other MX, including Google, Microsoft, ImprovMX, Cloudflare routing, Private Email, and parking. Do not leave a backup host. Priority is an order. Two vendors is leftover.
Query 8.8.8.8, 1.1.1.1, and authoritative NS. Classify split versus leftover. Foreign-probe each printed alias. Search dest including spam. Header From intact. Filename the post-cut screenshot with the zone and UTC date.
After the first website save
Re-query MX. Namecheap email and website tiles republish. If leftovers returned, delete them again and add a calendar reminder for Monday. TTL does not excuse a leftover row. Dual MX at sixty seconds is still leftover.
TXT quoting failures are a sibling article. Do not add a second MX owner to “help verify.” Send-as 550 is a plan or From problem, not Advanced DNS.
What to tell the client
We edited the zone the world uses. We published one MailerZ MX set. We turned off Private Email as an inbound owner. We probed from another mailbox. We will re-query after anyone clicks email or website tiles. We did not buy inbox placement. We did not install IMAP. Confirm pricing if they want send-as.
Related: leftover MX, compare Google Public DNS and Cloudflare DNS, GoDaddy MX mistakes, docs, tools, troubleshooting. Start free on one domain. Keep Advanced DNS exclusive.
More operational notes
Basic DNS versus Advanced DNS
Namecheap Basic DNS and Advanced DNS are easy to confuse under time pressure. The records you need are on the zone the public NS serve. If you edited a parked Basic view while Advanced held leftovers, you split yourself. Query public MX after every save. Filename screenshots. The green check in the panel is not exclusive MX.
Email forwarding alias inside Namecheap
Registrar forwarding products that create mailbox-like aliases are not MailerZ aliases. If that product still publishes MX, it owns inbound. Turn it off. Recreate printed names as MailerZ named aliases. Do not run both maps. Applicants and customers will split across products.
TTL you can live with
Lower TTL a day before a planned cut if you control it. After the exclusive paste, wait the remaining old TTL for caches to converge. Split 8.8.8.8 versus 1.1.1.1 is cache. Do not add dual MX during the wait. See how long MX changes take and how to tell propagation from bad configuration.
Internationalized names and www mistakes
Mail uses the registrable domain in the address, not www. Publishing MX only on www is a different QNAME. Internationalized domains need the same exclusive discipline on the name senders actually use. Write the QNAME on the ticket.
Monday after launch
Re-query every Monday after launch for a month if the client clicks website tiles weekly. Republish is the Namecheap-specific leftover. Tools help you see listings. They do not delete them. Start free, exclusive Advanced DNS, foreign probe.
MailerZ remains inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. Not Google Workspace, not IMAP, not webmail, not an open relay. Unauthorized send is 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. Free is one domain, three aliases, one seat, a fourteen-day store, fifty outgoing messages per month, unknown recipients held, and no send-as. Solo is forty dollars per year. Starter is eight monthly or eighty yearly. Business is nineteen or one hundred ninety. Agency is thirty-nine or three hundred ninety. Confirm numbers on the pricing page. Limits are not an inbox-placement promise. Start free at the MailerZ register URL when inbound must be proven first.
Worked closeout
A complete Namecheap evening
Eighteen hundred: query NS. They are Namecheap. Eighteen ten: aliases already exist. Eighteen fifteen: save old MX as text. Eighteen twenty: Advanced DNS — verification TXT, MailerZ MX only. Eighteen twenty-five: delete Private Email MX, parking MX, and two Google hosts. Eighteen thirty: query 8.8.8.8 and 1.1.1.1. Both show MailerZ. Eighteen thirty-five: foreign probe hello@ and support@ with unique subjects. Eighteen forty: dest including spam. Header From intact. Eighteen forty-five: filename screenshot. Next Monday: re-query after the client edits the website tile. If leftovers returned, delete them again.
If eighteen hundred had shown Cloudflare NS, the evening would have been Cloudflare’s DNS, not Namecheap Advanced DNS. That is the whole theater-zone lesson. If eighteen twenty-five had left Private Email “as backup,” the probes might have been a coin flip. Backup is leftover.
What Namecheap support cannot do for you
They can explain their tiles. They cannot make dual MX exclusive. They cannot create MailerZ aliases. They cannot 250 a third mailbox for you. They cannot excuse a leftover row. You still owe maps, exclusive listings, and probes. Domain Connect can paste records faster. It cannot delete a product tile that republishes MX tomorrow.
Send-as after the DNS cut
DNS exclusivity does not create SMTP. Paid dashboard pair. Mapped From. Free 550. Copy host, port, and TLS together. Two SPF records permerror. Authentication is not encryption. Do not use Namecheap mailbox SMTP beside MailerZ inbound and call it hybrid.
Close this Namecheap ticket
NS match the panel. MailerZ MX only. Private Email off as inbound owner. Two public views plus auth. Foreign probes. Zone-named screenshots. Monday re-query on the calendar. Start free with one domain and exclusive Advanced DNS.
Last operational reminders
Why leftover MX keeps coming back at Namecheap
Email tiles, website tiles, Domain Connect, and parking pages all write MX. Operators delete leftovers once and assume the zone is done. A teammate clicks Email the next afternoon. Private Email republishes. History goes quiet again. The fix is a habit: re-query after every Namecheap save, filename the screenshot, delete leftovers again, write the date. That habit is cheaper than a month of split senders.
Two resolvers plus authoritative NS classify cache versus leftover. Split is TTL. Same leftover on both public views is unfinished work. Dual MX is never a cache warmer. Maps first. Exclusive cut. Foreign probe. Free proves inbound on one domain. Paid send-as is a different hop. Confirm pricing. Not IMAP. Not Private Email. Not an inbox SLA. Start free and keep Advanced DNS exclusive.
If you also operate GoDaddy zones, do not copy a Namecheap evening onto a GoDaddy panel without an NS check. Each registrar republishes in its own way. The physics is the same: one inbound owner. The clicks are not.
Definition of done
Namecheap email forwarding DNS is finished when public NS match the panel you edited, Advanced DNS shows MailerZ MX only, Private Email is not an inbound owner, two public resolvers plus authoritative NS agree or you have classified a TTL split, every printed alias has a unique-subject foreign probe, Header From is intact, and a Monday re-query is on the calendar. Anything less is a tile you clicked. MailerZ can accept names it has. It cannot delete leftover rows you left in the panel. Start free on one domain. Confirm pricing if From must travel. Not IMAP. Not SOC 2. Not an inbox SLA.
Keep zone-named screenshots in the ticket next to the probe subjects. The next argument should not restart at a registrar preview pane. If NS moved to Cloudflare last year, this page does not apply until you open Cloudflare. If a teammate republishes Private Email next week, this page applies again the same hour. Exclusive is a habit, not a one-time paste.
The one rule
If you remember one Namecheap rule, remember this: the email aisle is a merchant flow that writes MX, and Advanced DNS is the typewriter. Use the typewriter. Disable the merchant flow as an inbound owner. Re-query after website saves. Foreign-probe every printed alias. Filename screenshots with the zone. That is email forwarding Namecheap DNS. Everything else is a leftover you will meet again on Monday.
Two public resolvers plus authoritative NS tell you whether you are waiting on TTL or still publishing Private Email. Split is cache. Same leftover is unfinished work. Dual MX is never a warmer. Maps first. Exclusive cut. Probe from another mailbox. Header From intact. Start free on one domain. Confirm pricing if send-as is in scope. Not IMAP. Not SOC 2. Not an inbox SLA.
FAQ
What is the safest way to handle email forwarding namecheap dns?
Open Advanced DNS on the zone the public NS actually serve. Publish the MailerZ verification TXT and the MailerZ MX set only. Delete leftover Private Email, forwarding, parking, and Google MX. Query two resolvers. Foreign-probe each printed alias. Re-query after any Namecheap email or website save. Do not use Namecheap’s email product as a second hop.
Does this require a new mailbox?
No. Mail lands in the Gmail or Outlook you map. MailerZ is not IMAP. Namecheap Private Email is a different product. Mixing it with MailerZ MX is leftover MX.
Will it work with Gmail or Outlook?
Yes when MX is exclusive and the alias exists. Self-send from Gmail can hide leftovers. Free has no send-as. Confirm pricing. Solo $40/yr. Starter $8/$80. Business $19/$190. Agency $39/$390.
What DNS records are involved?
Verification TXT, exclusive MailerZ MX, leftovers deleted. SPF, DKIM, DMARC when you send. See RFC 5321 and RFC 1035. Domain Connect helpers are not a substitute for exclusive listings.
What should I test before production?
Confirm NS. Build aliases first. Cut MX. Two resolvers. Foreign probe. Re-query after the next Namecheap click. Do not dual-MX “during DNS.”
Key takeaways
- Edit the zone public NS actually serve.
- MailerZ MX only. Delete Private Email and parking leftovers.
- Maps first. Then exclusive cut. Then foreign probe.
- Re-query after Namecheap email or website saves.
- Filename screenshots with the zone.
- Self-send is a bad gate.
- Confirm /pricing. Free has no send-as.
- Not IMAP. Not SOC 2. Not an inbox SLA.
Conclusion and next action
If the domain lives at Namecheap, use Advanced DNS as a typewriter, not the email aisle as a second MX owner. MailerZ can accept mail for names it has. It cannot delete leftover rows you left in the panel. Start free on one domain and keep the listing exclusive.
Ready to cut one Namecheap zone
Start free with one domain and exclusive Advanced DNS.
Copy dashboard MX. Delete extras. Sign in if the domain is already there.
Review after any Namecheap email or website save, and quarterly otherwise. Author: MailerZ editorial, Secuno LLC.