Forum Discussion
Hurricane_1983_
Cirrus
Cirrusmx record configuration in dns
Hi All,
I have two ISP links and each one pointing an mx record. if one link is go down than all emails is redirecting to another.But this take the some time so end some importent users are not satisfy for this situation. So we want to automize this process if a link goes down and minimize down time with our F5 DNS.All our DNS record is managed by ISP and our dns record is as below.We have configured the some delageted domains in our F5 DNS. We created a cname on ISP site and also created wideip for this domain. I think i will follow the same steps when i configured MX record in DNS. But in the pool configuration when i change record type as MX then the Member List section is changing as WideIP instead of Virtual Server.So firstly i have to configure wideIP for mx record and then i could configure a pool.
Anybody have an experience hot to dns need to be configred for below situation ?
many thanks,
A Record
mx1.xyz.com 192.168.1.1
mx2.xyz.com 192.168.1.2
MX Record
10 mx1.xyz.com
20 mx2.xyz.com
Hi Andrew,
By the way 192.168.1.1 and 192.168.1.2 ip addresses have to be Virtual Ip in the DNS config. Because dns need to return these virtual ip when client query for mx1.xyz.com. If i configure virtual ip as these ip addresses than i could not configure pool member and there is an another issue it will be ip conflict with isp address. do you have any suggestion for this?
Andy_McGrathCumulonimbus
A WideIP is equivalent to an A record (with any Alias' setup being CNAME records), you cannot create an MX record as a WideIP. Hence F5 DNS MX record is required to point to a WideIP.
Best option I think is to have a single MX record setup on your ISP that points to your WideIP on F5 DNS (GTM)
For example:
ISP Records for xyz.com MX Record 10 mx1.gtm.xyz.com F5 DNS Records for gtm.xyz.com (delegated zone) WideIP (A Records) mx1.gtm.xyz.com pool member 192.168.1.1 pool member 192.168.1.2
Hurricane_1983_Hi Andrew,
By the way 192.168.1.1 and 192.168.1.2 ip addresses have to be Virtual Ip in the DNS config. Because dns need to return these virtual ip when client query for mx1.xyz.com. If i configure virtual ip as these ip addresses than i could not configure pool member and there is an another issue it will be ip conflict with isp address. do you have any suggestion for this?