?
Solved

Send Connector for sub-domain

Posted on 2012-09-10
8
Medium Priority
?
2,094 Views
Last Modified: 2012-09-16
Hello Experts,

Email from our domain to a sub-domain with a separate MX record is failing.  Here's the situation:

- Our domain is example.org and has an MX record pointing to our Exchange server.
- Email sent to a sub-domain, let's call it subdomain.example.org, is failing for internal users.  External email sent to subdomain.example.org is routing fine.
- The DNS server in our environment has a Forward Lookup Zone for example.org that did not previously include an MX record for subdomain.example.org
- All email for both subdomain.example.org and example.org is working fine except for email sent from example.org to subdomain.example.org

I've tried adding an internal DNS record to the Forward Lookup Zone for example.org to include the appropriate MX record for subdomain.example.org and ran a ipconfig /flushdns with no effect.  I can still see email stuck in the Queue Viewer for any email sent to alias@subdomain.example.org with a 451 4.0.0 "DNS query failed" error.

I've also tried creating a Send Connector specifically for the subdomain.example.org domain.  Here's the details:

[PS] C:\Windows\system32>Get-SendConnector subdomain.example.org | fl


AddressSpaces                : {SMTP:subdomain.example.org;1}
AuthenticationCredential     :
Comment                      :
ConnectedDomains             : {}
ConnectionInactivityTimeOut  : 00:10:00
DNSRoutingEnabled            : True
DomainSecureEnabled          : False
Enabled                      : True
ErrorPolicies                : Default
ForceHELO                    : False
Fqdn                         :
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : EXCHANGE
Identity                     : subdomain.example.org
IgnoreSTARTTLS               : False
IsScopedConnector            : False
IsSmtpConnector              : True
LinkedReceiveConnector       :
MaxMessageSize               : 10 MB (10,485,760 bytes)
Name                         : subdomain.example.org
Port                         : 25
ProtocolLoggingLevel         : Verbose
RequireOorg                  : False
RequireTLS                   : False
SmartHostAuthMechanism       : None
SmartHosts                   : {}
SmartHostsString             :
SmtpMaxMessagesPerConnection : 20
SourceIPAddress              : 0.0.0.0
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {EXCHANGE}
TlsAuthLevel                 :
TlsDomain                    :
UseExternalDNSServersEnabled : True

I've specifically enabled the UseExternalDNSServersEnabled property so no internal DNS records will be used and restarted the Microsoft Exchange Transport service multiple times in an attempt to make the Send Connector "stick" with no effect.  What am I doing wrong here?

PS - the only other Send Connector in our environment is assigned the * SMTP address space and is the Default one for all other internet connections.

Thanks in advance.
0
Comment
Question by:terminalb
  • 4
  • 4
8 Comments
 
LVL 10

Expert Comment

by:Purple_Tidder
ID: 38385131
Create a new forward lookup zone for subdomain.example.org and set up MX records within it instead of using example.org.

It may not be the correct way, but it has worked for me.
0
 
LVL 2

Author Comment

by:terminalb
ID: 38385155
Done - same result.  DNS query failed.
0
 
LVL 2

Author Comment

by:terminalb
ID: 38385156
This was after an ipconfig /flushdns
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
LVL 10

Expert Comment

by:Purple_Tidder
ID: 38385252
What is your MX record set to?
0
 
LVL 10

Expert Comment

by:Purple_Tidder
ID: 38385253
Also, I'd think you'd want your external DNS option disabled.  If all the domains are in-house, you'll hit routing issues trying to route internal mail to a public IP or address I would think.
0
 
LVL 2

Accepted Solution

by:
terminalb earned 0 total points
ID: 38388438
While I did create an internal MX record previously without any effect, I completely forgot to add the internal A record for the host the MX record pointed to.  Once I did that in the Forward Lookup Zone for the sub-domain in question, mail started flowing again.  Thanks anyway.
0
 
LVL 10

Expert Comment

by:Purple_Tidder
ID: 38388486
Thats why I was asking what your MX record was set to.  Glad you got it figured out.
0
 
LVL 2

Author Closing Comment

by:terminalb
ID: 38402930
No other solutions worked.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you looking for the options available for exporting EDB files to PST? You may be confused as they are different in different Exchange versions. Here, I will discuss some options available.
If you have come across a situation where you need to find some EDB mailbox recovery techniques, then here you will find the same. In this article, we will take you through three techniques using which you will be able to perform EDB recovery. You …
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question