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:
mail.domain.com (A Record) 202.43.252.167 Default TTL 1 hr.
mail.domain.com (A Record) 202.43.252.91 Default TTL 1 hr.
Internal AD-Integrated DNS server:
mail.domain.com (A Record) 10.1.1.100 Default TTL 1 hr.
mail.domain.com (A Record) 10.1.11.113 Default TTL 1 hr.
PRODMAIL01-VA.domain.com (A Record) 10.1.1.100
PRODMAIL02-VA.domain.com (A Record) 10.1.11.113
Would that configuration works for the Exchange Server 2013 Send Connector resiliency if I just put mail.domain.com ?
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.
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:
mail.domain.com (A Record) 202.43.252.167 Default TTL 1 hr.
mail.domain.com (A Record) 202.43.252.91 Default TTL 1 hr.
Internal AD-Integrated DNS server:
mail.domain.com (A Record) 10.1.1.100 Default TTL 1 hr.
mail.domain.com (A Record) 10.1.11.113 Default TTL 1 hr.
PRODMAIL01-VA.domain.com (A Record) 10.1.1.100
PRODMAIL02-VA.domain.com (A Record) 10.1.11.113
Would that configuration works for the Exchange Server 2013 Send Connector resiliency if I just put mail.domain.com ?
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.
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.
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 Systems Engineer
CERTIFIED EXPERT
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 ?