Link to home
Start Free TrialLog in
Avatar of Eric Jack
Eric JackFlag for United States of America

asked on

Secondary email address is undeliverable (secondary domain)

I'm probably missing something stupid and simple. But as a 1-man IT department, I don't have a second set of eyes to pick up on my mistake...

A sister company closed its US office and some of the employees moved to our office. Their managed service provider shut down their Exchange server, but assigned ownership of the domain name to us. I duplicated the DNS Zone File information for the second domain name on the GoDaddy web portal to match our primary domain. On my Exchange 2010 server, I added an additional email address to select users such as

However, when I send a test email from an outside source, I keep getting "Delivery Notification: Delivery has failed" messages:

This report relates to a message you sent with the following header fields:

  Message-id: <>
  Date: Wed, 28 Oct 2015 14:00:15 +0000 (GMT)
  From: Eric Jack <>
  Subject: Test 10:00

Your message cannot be delivered to the following recipients:

  Recipient address:
  Reason: Remote SMTP server has rejected address
  Diagnostic code: smtp;550 5.7.1 Unable to relay
  Remote system: dns; (TCP||44229|(My IP)|25) ( Microsoft ESMTP MAIL Service ready at Wed, 28 Oct 2015 10:00:29 -0400)
Avatar of Todd W
Todd W
Flag of United States of America image

the mx record (with your hosting provider's DNS) for the shutdown exchange environment must be configured to route email to your existing exchange server.

so if your working mx record is and all email is working there

then your mx record for old domain should also be

you also have to set your receive connector within exchange to accept email for
Avatar of Eric Jack


Well, that's why I'm still perplexed. I've configured the DNS settings for the secondary domain on GoDaddy to match that of our primary domain. See the screenshots I've attached.

Here's the DNS settings for the company's primary domain:
User generated imageAnd here they are for the secondary domain I'm trying to get emails for:
User generated image
Regarding the Receive Connector on the Exchange server, I have one in place for Since the DNS settings on GoDaddy have email going to, what do I need to add in Exchange?

If I try to create a new Receive Connector, I'm getting this error:

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00

Linear Forwarding

The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "SWIK-S-EX01\Default SWIK-S-EX01". A Receive connector must have a unique combination of a local IP address, port bindings, and remote IP address ranges. Change at least one of these values.
Click here for help...

Exchange Management Shell command attempted:
new-ReceiveConnector -Name 'Linear Forwarding' -Usage 'Custom' -Bindings '' -Fqdn '' -RemoteIPRanges '' -Server 'SWIK-S-EX01'

Elapsed Time: 00:00:00
shouldn't that be

New-ReceiveConnector -Name 'Linear Forwarding' -Usage 'Custom' -Bindings '' -Fqdn 'decommissioned' -RemoteIPRanges '' -Server 'SWIK-S-EX01'
and create an MX record for the decommissioned domain (wherever that domain is being hosted) that points to the IP address of
The decommissioned domain is hosted by GoDaddy, same as the active domain. As you can see in my screen captures above, the DNS settings for linear-tv (the decommissioned domain) have the following settings:

A (Host) Mail =
MX host @ points to

Should the MX record on instead say and then create a new Connector on the Exchange server with the FQDN

I thought by "redirecting" the decommissioned domain name in the DNS settings on GoDaddy's site, it would redirect emails. Apparently since the email address is still that wasn't working.
ok your dns is fine.  need to tell exchange now to accept email for via a receive connector.
Okay, but I'm having trouble with that. From the Exchange Management Console > Server Configuration > Hub Transport > New Receive Connector...

In the "wizard", I'm giving it a Name: Linear Forwarding, Intended use: Custom, Local network settings: Leaving all available IPv4, Specify FQDN, Remote network settings, IP addesses: leaving all, but then getting the same failure I mentioned above.
my bad.. I didn't catch that you were using the same internal IP address for this new receive connector as you are with the old receive connector.

You must have different internal IP addresses for each receive connector.

you need to make sure your firewall is allowing that through as well.

receive connector 1 (existing that works) should be for example and allowed through the firewall

receive connector 2 (new one) should be for example and allowed through the firewall.
Different IP addresses?! So if I have multiple domains, I would need a different IP address for each? (Internal or external?)

A few years ago when we changed our company name, we had kept the old domain name email address on everyone's mailbox, but just created a new domain name email address and made it the primary address. I don't remember having to have different connectors or IP addresses. We just had our domain host point each domain to the mail server and things worked.
Avatar of Eric Jack
Eric Jack
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I discovered the correct answer on my own and posted it to help anyone else who runs into this problem.