CNAME Record domain forwarding breaks emails due to MX Records mis-match

CNAME Record caused my emails to fail.

I hosted 2 emails at RackSpace for my domain, and verified they worked fine. This required me to update the MX records where I host my domain.
name1@domain1.com
name2@domain1.com

Fine.

Then, before I could create a website, I was allowed by my partner to point my domain at his website.

The redirect worked once I created a CNAME record.
domain1.com brings up the site at domain2.com

But the emails stopped working.

The error is "553 Relaying disallowed"

I called RackSpace and they said it's because the MX records at the domain2.com, where domain1.com points at, are pointing to Zoho (a major email provider).

So, my question is...

If I move my two emails from RackSpace to Zoho, can I have a solution where

1) domain forwarding is working (domain1.com brings up the site at domain2.com)
2) emails work as well (both (domain1.com emails work again)

?

Thanks.

Or, is there another way to configure this?

Thanks

curiouswebsterSoftware EngineerAsked: 2018-03-15

Who is Participating?

Experts Exchange Solution brought to you by

Enjoy your complimentary solution view.

Get this solution by purchasing an Individual license! Start your 7-day free trial.

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LVL 51

nociSoftware EngineerCommented: 2018-03-15

If the IP address of domain.com is stable use the A address in stead of CNAME.
then all mail would follow the MX record and the web access would follow the domain1.com

Another way could be: domain1.com to your site
www.domain1.com CNAME -> domain2.com
on your site handle the case for domain1.com -> redirect -> www.domein1.com

A third option: run HAPROXY on you domain1.com system and reversproxy all requests to the domain2.com system.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial