Link to home
Start Free TrialLog in
Avatar of terminalb
terminalbFlag for United States of America

asked on

Send Connector for sub-domain

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.
Avatar of Purple_Tidder
Purple_Tidder
Flag of United States of America image

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.
Avatar of terminalb

ASKER

Done - same result.  DNS query failed.
This was after an ipconfig /flushdns
What is your MX record set to?
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.
ASKER CERTIFIED SOLUTION
Avatar of terminalb
terminalb
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thats why I was asking what your MX record was set to.  Glad you got it figured out.
No other solutions worked.