The primary purpose of the BIG-IP® Global Traffic Manager is to help you manage incoming wide IP traffic, and load balance that traffic to the appropriate network resources. However, wide IP traffic is only part of the overall DNS traffic a network must handle. Consequently, typical installations of the Global Traffic Manager involve configuring the system to work in conjunction with existing DNS servers already on the network. The recommended configuration is to configure your DNS server to delegate wide IP-related requests to the Global Traffic Manager for name resolution.
To control how the Global Traffic Manager responds to DNS requests, you must configure a listener. A listener is a specialized resource that is assigned a specific IP address and uses port 53, the DNS query port. When traffic is sent to that IP address, the listener alerts the Global Traffic Manager, allowing it to handle the traffic locally or forward the traffic to the appropriate resource.
In this configuration, you must create a listener that corresponds to a delegated zone that you create on your existing DNS server.
This implementation describes the steps necessary to integrate a Global Traffic Manager with an existing DNS server.
This implementation focuses on the fictional company SiteRequest. SiteRequest recently purchased a Global Traffic Manager to help load balance traffic across two of its web-based applications: store.siterequest.com and checkout.siterequest.com. These applications are delegated zones of www.siterequest.com, which an existing DNS server manages. They have already configured the Global Traffic Manager with two wide IPs, store.wip.siterequest.com and checkout.wip.siterequest.com, which correspond to these two web applications.
In order for the Global Traffic Manager to manage the web applications of store.siterequest.com and checkout.siterequest.com, you must create the delegated zone on the existing DNS server. Creating a delegated zone typically involves the following tasks:
Again, if you are unfamiliar with how to create these zones, we recommend you review 5th edition of DNS & BIND, available from O'Reilly.
The final configuration step requires you to set a listener on the Global Traffic Manager. The Global Traffic Manager employs this listener to identify the DNS traffic for which it is responsible. In this solution, the listener you create is the same as the IP address of the Global Traffic Manager: 192.168.5.17.
You now have an implementation of the Global Traffic Manager in which the existing DNS server manages DNS traffic unless the query is for store.siterequest.com or checkout.siterequest.com. When the DNS server receives these queries, it delegates them to the Global Traffic Manager, which then load balances them on the appropriate wide IPs.