DanCardwell
asked on
Can I use Exchange for multiple domains and have the mail routed out multiple IP addresses
I am using exchange 2007 SP1 and I would like to have multiple approved domains send mail out specified IP addresses on the server. I want DNS lookups to be handled so that messaged don't get flagged as spam.
Is this even possible with Exchange, or do I need to look at another option.
Is this even possible with Exchange, or do I need to look at another option.
Exchange_Geek
Do you mean that you want Exchange to host multiple domains or simply have multiple accepted domains (recipient policies) ? If you plan to work on either option - Exchange would work fine - definitely it goes without say you require your ISP updated with the MX records of your accepted domains. Have PTR records also updated with the new accepted domains.
ASKER
I want to host multiple domains.
The ultimate goal is to be able to send email from 123@xyz.com and have an MX record that points to an IP address on the exchange server, and at the same time send from 789@abc.com and have the MX record point to a different IP address on the same exchange server.
The trick is that when the receiving mail client does a lookup on the domain xyz.com or abc.com to verify the IP address, I need it to work.
Would I use different send connectors to ensure that the lookup, when performed, validates the domain and the IP address correspond?
Is this even an issue, Can I have two different domains pointing to an IP address so long as my ISP has a DNS record for each?
Thanks
The ultimate goal is to be able to send email from 123@xyz.com and have an MX record that points to an IP address on the exchange server, and at the same time send from 789@abc.com and have the MX record point to a different IP address on the same exchange server.
The trick is that when the receiving mail client does a lookup on the domain xyz.com or abc.com to verify the IP address, I need it to work.
Would I use different send connectors to ensure that the lookup, when performed, validates the domain and the IP address correspond?
Is this even an issue, Can I have two different domains pointing to an IP address so long as my ISP has a DNS record for each?
Thanks
I want to host multiple domains.
The ultimate goal is to be able to send email from 123@xyz.com and have an MX record that points to an IP address on the exchange server, and at the same time send from 789@abc.com and have the MX record point to a different IP address on the same exchange server.
********You could even use the same ip address on the same exchange server
The trick is that when the receiving mail client does a lookup on the domain xyz.com or abc.com to verify the IP address, I need it to work.
*******That is a plain DNS check up - your ISP can help you set that up at their end.
Would I use different send connectors to ensure that the lookup, when performed, validates the domain and the IP address correspond?
Is this even an issue, Can I have two different domains pointing to an IP address so long as my ISP has a DNS record for each?
*******Yes, simply have the accepted domains informed to your ISP - ask them to have a MX record pointing to your firewall / exchange server for domains xyz + abc.
The ultimate goal is to be able to send email from 123@xyz.com and have an MX record that points to an IP address on the exchange server, and at the same time send from 789@abc.com and have the MX record point to a different IP address on the same exchange server.
********You could even use the same ip address on the same exchange server
The trick is that when the receiving mail client does a lookup on the domain xyz.com or abc.com to verify the IP address, I need it to work.
*******That is a plain DNS check up - your ISP can help you set that up at their end.
Would I use different send connectors to ensure that the lookup, when performed, validates the domain and the IP address correspond?
Is this even an issue, Can I have two different domains pointing to an IP address so long as my ISP has a DNS record for each?
*******Yes, simply have the accepted domains informed to your ISP - ask them to have a MX record pointing to your firewall / exchange server for domains xyz + abc.
ASKER
I guess this is getting close. I really need it to not only send and perform a lookup correctly but I also (and I realize that I didn't state this before) don't want any other domains associated with the ip address of one of the domains..
If I do a lookup on an IP address I don't want to know about any other domains.
Thanks for your assistance.
If I do a lookup on an IP address I don't want to know about any other domains.
Thanks for your assistance.
Well, then why do not you have multiple ip address associated at a firewall level and set a rule to send communication received from ISP (which by default would be on port 25) to forward queries to your server.
This ways your Exchange server wont be exposed to the net and you also would receive emails safely sitting behind a firewall
This ways your Exchange server wont be exposed to the net and you also would receive emails safely sitting behind a firewall
ASKER
That handles incoming issued but when I send, the IP address associated with the outgoing message is what I am concerned with. How do I have exchange send out one ip address for xyz.com and another for abc.com?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm going to try this one more time.
We have a partner who wants us to handle some of their customer service. We currently have exchange handling our mail and this partner wants us to send email using a subdomain that they own. They will point the MX record to one of our IP addresses. This partnership requires that the relationship be anonymous. To that end, when we send emails using their subdomain from our exchange server everything relating to us needs to be hidden.
Scenario:
I send an email to someone. They receive it and see that it came from me@xyz.com. They do a lookup on the MX record and get an IP address, host name and possibly other sites/domains associated with the IP address.
I send another email to someone. They receive it and see that it comes from me@abc.123.com. They do a lookup on the MX record and they get a DIFFERENT static IP address and host name even though the static/external IP addresses are ours. They cannot see any information relating to our domain.
I know that this would be easy with multiple exchange servers each having their own IP address. I would like to know if we can do this some way with a single exchange server or do we need to purchase a new server for any partner who wants the same thing. I know when I do a reverse lookup on our domain I get other site information and this is what I am trying to avoid.
Forgive me if I haven't been clear up to this point, and thanks for the assistance.
We have a partner who wants us to handle some of their customer service. We currently have exchange handling our mail and this partner wants us to send email using a subdomain that they own. They will point the MX record to one of our IP addresses. This partnership requires that the relationship be anonymous. To that end, when we send emails using their subdomain from our exchange server everything relating to us needs to be hidden.
Scenario:
I send an email to someone. They receive it and see that it came from me@xyz.com. They do a lookup on the MX record and get an IP address, host name and possibly other sites/domains associated with the IP address.
I send another email to someone. They receive it and see that it comes from me@abc.123.com. They do a lookup on the MX record and they get a DIFFERENT static IP address and host name even though the static/external IP addresses are ours. They cannot see any information relating to our domain.
I know that this would be easy with multiple exchange servers each having their own IP address. I would like to know if we can do this some way with a single exchange server or do we need to purchase a new server for any partner who wants the same thing. I know when I do a reverse lookup on our domain I get other site information and this is what I am trying to avoid.
Forgive me if I haven't been clear up to this point, and thanks for the assistance.