Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.
Course Of The Month
11 days, 1 hour left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
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 today
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 today
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 today
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
Check out this step-by-step guide for using the newly updated Experts Exchange mobile app—released on May 30.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment.
The video tutorial explains the basics of the Exchange server Database Availability grou…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month11 days, 1 hour left to enroll
628 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.