Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

Hurricane_1983_'s avatar
Hurricane_1983_
Icon for Cirrus rankCirrus
8 years ago
Solved

mx 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 ...
application delivery
BIG-IP DNS
LTM
  • Hurricane_1983_'s avatar
    Hurricane_1983_
    8 years ago

    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_McGrath's avatar
Andy_McGrath
Icon for Cumulonimbus rankCumulonimbus
8 years ago

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