JrSysAdmin
asked on
Unable to resolve Google hosted email accounts
Scenario
- We have email hosting via Google with the domain name company.com.
- We also have an Active Directory domain with the same namespace.
- We provide hosted services for small businesses and host their email on an Exchange server on the company.com domain. We use aliases to give them a user@therecompany.com e-mail account.
Problem
Our clients can not send email to us at support@company.com because the internal DNS server thinks it knows how to resolve that name but is unable to resolve. Is there a way to resolve this issue either via DNS or Exchange Server?
- We have email hosting via Google with the domain name company.com.
- We also have an Active Directory domain with the same namespace.
- We provide hosted services for small businesses and host their email on an Exchange server on the company.com domain. We use aliases to give them a user@therecompany.com e-mail account.
Problem
Our clients can not send email to us at support@company.com because the internal DNS server thinks it knows how to resolve that name but is unable to resolve. Is there a way to resolve this issue either via DNS or Exchange Server?
mlongoh
Are your clients e-mail addresses also @company.com?
ASKER
Clients are their own e-mail address, i.e. user@therecompany.com
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So what you want to do is configure the Exchange system to forward mail destined for @company.com to the MX record of your Google mail. I'm assuming that someone external to your clients can get mail to you with no problem.
Simon's links I think are appropriate - I did this years ago on an Exchange 2003 server. In essence I had a client running an old mail system on a separate domain and needed Exchange to route mail to the old system if the SMTP recipient couldn't be found in the Exchange system. In your case, it's the same concept.
Simon's links I think are appropriate - I did this years ago on an Exchange 2003 server. In essence I had a client running an old mail system on a separate domain and needed Exchange to route mail to the old system if the SMTP recipient couldn't be found in the Exchange system. In your case, it's the same concept.