terminalb
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.or g 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-Se ndConnecto r subdomain.example.org | fl
AddressSpaces : {SMTP:subdomain.example.or g;1}
AuthenticationCredential :
Comment :
ConnectedDomains : {}
ConnectionInactivityTimeOu t : 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 :
SmtpMaxMessagesPerConnecti on : 20
SourceIPAddress : 0.0.0.0
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {EXCHANGE}
TlsAuthLevel :
TlsDomain :
UseExternalDNSServersEnabl ed : True
I've specifically enabled the UseExternalDNSServersEnabl ed 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.
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.or
I've also tried creating a Send Connector specifically for the subdomain.example.org domain. Here's the details:
[PS] C:\Windows\system32>Get-Se
AddressSpaces : {SMTP:subdomain.example.or
AuthenticationCredential :
Comment :
ConnectedDomains : {}
ConnectionInactivityTimeOu
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 :
SmtpMaxMessagesPerConnecti
SourceIPAddress : 0.0.0.0
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {EXCHANGE}
TlsAuthLevel :
TlsDomain :
UseExternalDNSServersEnabl
I've specifically enabled the UseExternalDNSServersEnabl
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.
ASKER
Done - same result. DNS query failed.
ASKER
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
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thats why I was asking what your MX record was set to. Glad you got it figured out.
ASKER
No other solutions worked.
It may not be the correct way, but it has worked for me.