Exchange Server Send connector and DNS Round Robin ?

Hi All,

If I create two different IP address (A) record for the Linux appliance in my internal DNS server and then make it the same name like below:

External AD-Integrated DNS server: (A Record) Default TTL 1 hr. (A Record) Default TTL 1 hr.

Internal AD-Integrated DNS server: (A Record) Default TTL 1 hr. (A Record) Default TTL 1 hr. (A Record) (A Record)

Would that configuration works for the Exchange Server 2013 Send Connector resiliency if I just put ?

So if I need to perform maintenance or upgrade on the Virtual appliance, I can just delete the (A) record and then retype it again once it is done, without causing any email queue or blockage.

My assumption is that the TTL in the public DNS can be reduced to just 1 minute to expedite the process when the email is queued during the appliance maintenance.

Any help and comment would be greatly appreciated.
LVL 12
Senior IT System EngineerSenior Systems EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris DentPowerShell DeveloperCommented:
it doesn't, by itself, offer resiliency. If an attempt to send leads to one A record, and that fails, the mail service will not try the other one.

If you're going to pull / push records as and when you need (and with awareness of the TTLs) them it'll be fine.
Senior IT System EngineerSenior Systems EngineerAuthor Commented:
OK, so how to make it resilient by using DNS round robin ?
Chris DentPowerShell DeveloperCommented:
Resilient / DNS round robin... These things don't fit together at all in any automatic sense.

If you're looking at this to provide resilience you have to consider it as you did in the first place: Low TTL and change / remove records if something is going offline.

If you need it to be automatic you need to think in terms of load balancers, or at the very least something to monitor services and carry out the DNS changes for you.
Ensure Business Longevity with As-A-Service

Using the as-a-service approach for your business model allows you to grow your revenue stream with new practice areas, without forcing you to part ways with existing clients just because they don’t fit the mold of your new service offerings.

Senior IT System EngineerSenior Systems EngineerAuthor Commented:
Chris, so in my case here it would be better off just to use each appliance IP address (A) record than the mail.domain com ?
Chris DentPowerShell DeveloperCommented:
The send connector accepts more than one smart host when you define the connector. I would imagine that this is somewhat fault tolerant and it'll try all of them until it works or there are no more to try. This might be the safest path, routing stays strictly with Exchange in that scenario.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Senior IT System EngineerSenior Systems EngineerAuthor Commented:
Thanks, Chris.

So I assume that I leave the both IP address like the two lines above, then Exchange will intelligently pick which one is up.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.