Avatar of swcrook
Flag for United States of America asked on

DNS and Exchange

Hi experts. I have a two part question about a problem I am trying to resolve.

Before the question, I'll provide the scenario.

I am using a vendor which is basically sending out promotion materials via our domain name with the exception that they are adding their own servers and then forwarding that to customers, etc.

For example, I have domain contoso.com. They are wanting to send email from vendor.contoso.com.  We house internal servers with contoso.com, but they want to send emails from @vendor.contoso.com. This is actually working to a certain extent because I have DNS entries on our external DNS servers which points to the "vendor" servers.

So, with this working as best I can describe, the piece that is not working is when a user is created on the vendor.contoso.com server as joe@vendor.contoso.com this address can't seem to email the domain of @contoso.com.

In fact, no user accounts setup with @vendor.contoso.com can email @contoso.com BUT those same users emailing from @vendor.contoso.com can email all other domains successfully i.e. joe@gmail.com

I am sure I am missing something easy, but can someone show a little pity and direct me to the water :)

Thanks all!
ExchangeDNSEmail Servers

Avatar of undefined
Last Comment

8/22/2022 - Mon

Not sure I understand the scenario; so are we talking about two different servers in different places? You have your server on site which is responsible for handling mail for contoso.com, and then another server on your vendor's site which is responsible for handling mail for vendor.contoso.com?

You say you "have NS entries on [your] external DNS servers which points to the "vendor" servers". Could you elaborate a little here? Exactly what do you have in DNS for that?

Sounds like you need to check what contoso.com resolves to at your *vendor* site, or from the vendor mailservers. In order to send email to you at contoso.com they will need to have the appropriate MX records pointing to the external IP addresses of the device you expect to receive the emails destined to you on that domain.

If they have set up the domain contoso.com and vendor.contoso.com on their own local/internal DNS servers they may just be trying to deliver the email somewhere internally on their own network.

Sorry if I wasn't being clear, but you almost have the scenario.

We house @contoso.com and send email from this domain. Since the vendor we are working with wants to send lots and lots of emails to our customers, they wanted us to add NS entries to our external DNS servers that point to their servers for the domain vendor.contoso.com

For example:

vendor.contoso.com. 1800 IN NS ns1.vendor.com
vendor.contoso.com. 1800 IN NS ns2.vendor.com

The domain / subdomain:  vendor.contoso.com
Has an authotitaive nameserver at :  ns1.vendor.com
This nameserver will then resolve queries for this domain / subdomain.

I would imagine that Vendor would need to make sure that their server knows it is not authoritative for contoso.com.  If they are using Exchange 2007/2010 they should check the list of accepted domains in the hub transport section at the Org level. You could look at adding contoso.com as an accepted domain and create a send connector for traffic to that domain that directs the traffic straight at the appropriate mail server.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

Btw, what happens to these messages so far, do you know?  Do they get any bounces?  Have they gone into the message tracking tool and searched for emails being sent to contoso.com? What can be found there?

So mail users @vender.contoso.com can send/receive email anywhere except to/from contoso.com?

What happens when they try?  Does it bounce?

Is the server handling mail for these domains the same?  Do you have a valid mx record for the sub domain?

This vendor is a marketing company that is up and coming. They don't have "control over the domain" because essentially they are just playing with a "fake" domain housed on their servers that they then use to send emails from.

This way, they are no in my AD, ever, adn they can send marketing emails as my company. I simply needed to trick AD and Exchange inot thinking that the server sending those particular emails would be routing to their severs.
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.