Hi Everyone
We currently use a smart host to route all mail which does not belong to an internal domain to our outbound 3rd party servers on ouur exchange infrastructure.
We now have a requirement for a 3rd party application to route mail for all domains ending in a certain domain to a specific host:
Lets say the last domain is "blah" the mail that needs to be routed to this host could be @anything.blah or @anythingelse.blah (i.e the first part of the domain could be literally anything)
The company have suggested that we create a non-public domain in our DNS (AD integrated) called "blah" with an MX records in this domain that points to the host that the mail needs to be relayed to.
From what I've read - I can't see how this will work considring the fact that we use the smart host I mentioned above. Am I wrong? Will the MX record work? Is it an advisable way to do this?
Your comments/suggestions/advice are appreciated.
Regards
Brendon
We currently use a smart host to route all mail which does not belong to an internal domain to our outbound 3rd party servers on ouur exchange infrastructure.
We now have a requirement for a 3rd party application to route mail for all domains ending in a certain domain to a specific host:
Lets say the last domain is "blah" the mail that needs to be routed to this host could be @anything.blah or @anythingelse.blah (i.e the first part of the domain could be literally anything)
The company have suggested that we create a non-public domain in our DNS (AD integrated) called "blah" with an MX records in this domain that points to the host that the mail needs to be relayed to.
From what I've read - I can't see how this will work considring the fact that we use the smart host I mentioned above. Am I wrong? Will the MX record work? Is it an advisable way to do this?
Your comments/suggestions/advice are appreciated.
Regards
Brendon