You can deploy BIG-IP® DNS (formerly GTM) on a network where BIG-IP Local Traffic Manager™ (LTM®) systems are configured with multiple route domains and overlapping IP addresses.
The following figure shows BIG-IP DNS deployed in a network with multiple BIG-IP Local Traffic Manager™ (LTM®) systems, one configured with the default route domain (zero), and one configured with two additional route domains. BIG-IP DNS can monitor the Application1 and Application2 servers that have overlapping IP addresses and reside in different route domains. The firewalls perform the required address translation between the BIG-IP DNS and BIG-IP LTM addresses; you must configure the firewalls to segment traffic and avoid improperly routing packets between route domain 1 and route domain 2.
BIG-IP DNS deployed on a network with multiple route domains
Before BIG-IP® DNS can gather status and statistics for the virtual servers hosted on BIG-IP LTM® systems that are configured with route domains, you must configure the following on each BIG-IP LTM that handles traffic for route domains:
Additionally, configure a BIG-IP DNS server object on BIG-IP DNS to represent each LTM system device.
Perform the following tasks to configure BIG-IP DNS to monitor BIG-IP LTM systems with route domains.
For example, you can type ffff:ffff:ffff:ffff:0000:0000:0000:0000 or ffff:ffff:ffff:ffff::.
|Inherit from Data Center||By default, a server inherits the Prober pool assigned to the data center in which the server resides.|
|Prober pool name||Select the Prober pool that contains the BIG-IP systems that you want to perform monitor probes of this server.|
You now have an implementation in which BIG-IP DNS monitors BIG-IP LTM virtual servers on the various route domains in your network.