Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
Solved
Name resolution for Smarthost FQDN in Exchange 2010 send connector
Posted on 2014-03-13
Hi All
We Journal our email to a 3rd party archive company via SMTP rather than a MAPI mailbiox, we have a journal rule configured to send all email to a specific email address mycompany@3rdparty.com, we then have a send connector configured to send all email for that email address via a smart host which is mailarchive.3rdparty.com
Today everything stopped working and i ended up with 50'000 emails in the queue for this Smarthost connector.
On troubleshooting i noticed that i could not resolve the FQDN of the smarthost mailarchive.3rdparty.com so thought that must be the issue
However everything kicked back into life and the email queue is going down, heres the twist, even though its now working, from the Hub Transport servers i still cannot resolve mailarchive.3rdparty.com!!
I turned on verbose logging for the send connector and can see that actually it is making connections to mail.3rdparty.com but i just cant work out how if it cannot resolve the FQDN specified in the send connector how it can possibly get any further.
We have TLS configured for on the send connector and use Basic Authentication over TLS.
Im wondering is there any other way in which this could be resolving
Thanks
We Journal our email to a 3rd party archive company via SMTP rather than a MAPI mailbiox, we have a journal rule configured to send all email to a specific email address mycompany@3rdparty.com, we then have a send connector configured to send all email for that email address via a smart host which is mailarchive.3rdparty.com
Today everything stopped working and i ended up with 50'000 emails in the queue for this Smarthost connector.
On troubleshooting i noticed that i could not resolve the FQDN of the smarthost mailarchive.3rdparty.com so thought that must be the issue
However everything kicked back into life and the email queue is going down, heres the twist, even though its now working, from the Hub Transport servers i still cannot resolve mailarchive.3rdparty.com!!
I turned on verbose logging for the send connector and can see that actually it is making connections to mail.3rdparty.com but i just cant work out how if it cannot resolve the FQDN specified in the send connector how it can possibly get any further.
We have TLS configured for on the send connector and use Basic Authentication over TLS.
Im wondering is there any other way in which this could be resolving
Thanks
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
3
4 Comments
Active 2 days ago
Hello,
If you open the Properties page of your hub transport server and go to the "External DNS Lookups" tab, do you have DNS servers listed here?
-JJ
If you open the Properties page of your hub transport server and go to the "External DNS Lookups" tab, do you have DNS servers listed here?
-JJ
Active 3 days ago
Hi JJ
We dont have any specific DNS servers listed there, we just use the NIC's
We dont have any issues with external name resolution, i can resolve many other external FQDNs sucj as www.google.com etc.
Its just this one in particular
Thanks
We dont have any specific DNS servers listed there, we just use the NIC's
We dont have any issues with external name resolution, i can resolve many other external FQDNs sucj as www.google.com etc.
Its just this one in particular
Thanks
Active 3 days ago
I got to the bottom of this,
What i thought was the FQDN of a server was in fact a sub-domain, so exchange looks up the MX records for that sub-domain and sends email via one of those.
I did not know you could do this, i have always used either the IP address or FQDN of a relay server as a smarthost target.
Mystery solved.
Thanks
What i thought was the FQDN of a server was in fact a sub-domain, so exchange looks up the MX records for that sub-domain and sends email via one of those.
I did not know you could do this, i have always used either the IP address or FQDN of a relay server as a smarthost target.
Mystery solved.
Thanks
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
- Software-Other
- Exchange
- Email Servers
- Email Software
- Exchange 2007
- *Exchange Server 2010
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA).
For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651
If you want to manage em…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month9 days, 8 hours left to enroll
722 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.