You can deploy 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 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.
When the Hardware SYN Cookie setting is enabled, the BIG-IP system triggers SYN cookie protection in either of these cases, whichever occurs first:
For example, you can type 255.255.255.0.
|Inherit From Data Center||By default, a server inherits the prober preference selection assigned to the data center in which the server resides.|
|Inside Data Center||A server selects the probers from inside the data center where the server resides.|
|Outside Data Center||A server selects the probers from outside the data center where the server resides.|
|Specific Prober Pool||Select one of the Prober pools
from the drop-down list. When assigning the Prober pool at the server
Prober pools are not used by the bigip monitor.
|Inherit From Data Center||By default, a server inherits the prober fallback selection assigned to the data center in which the server resides.|
|Any Available||For selecting any available prober.|
|Inside Data Center||A server selects probers from inside the data center where the server resides.|
|Outside Data Center||A server selects probers from outside the data center where the server resides.|
|None||No fallback probers are selected. Prober fallback is disabled.|
|Specific Prober Pool||Select one of the probers from the list When you want to assign a prober pool at the server level.|
|All Health Monitors||By default, specifies that all of the selected health monitors must be successful before the server is considered up (available).|
|At Least||The minimum number of selected health monitors that must be successful before the server is considered up.|
|Require||The minimum number of successful probes required from the total number of probers requested.|
|Disabled||Use this option when you plan to manually add virtual servers to the system, or if your network uses multiple route domains. This is the default value.|
|Enabled||The system automatically adds virtual servers using the discovery feature.|
|Enabled (No Delete)||The system uses the discovery feature and does not delete any virtual servers that already exist.|
You now have an implementation in which BIG-IP DNS monitors BIG-IP LTM virtual servers on the various route domains in your network.