Print

Applies To:
Hide Versions BIG-IP GTM 11.1.0

Manual Chapter: Delegating DNS Traffic to Wide IPs

Original Publication Date: -

Overview: Delegating DNS traffic to wide IPs

BIG-IP Global Traffic Manager (GTM) resolves DNS queries that match a wide IP name. BIG-IP GTM can work in conjunction with an existing DNS server on your network. In this situation, you configure the DNS server to delegate wide IP-related requests to BIG-IP GTM for name resolution.

Traffic flow when DNS server delegates traffic to BIG-IP GTM

This implementation focuses on the fictional company SiteRequest that recently purchased BIG-IP GTM to help resolve queries for two web-based applications: store.siterequest.com andcheckout.siterequest.com. These applications are delegated zones of www.siterequest.com. Currently, a DNS server manages www.siterequest.com. SiteRequest administrators have already configured BIG-IP GTM with two wide IPs,www.store.siterequest.com and www.checkout.siterequest.com. These wide IPs correspond to the two web applications.

About listeners
A listener is a specialized virtual server that uses port 53 and to which you assign a specific IP address. When traffic is sent to that IP address, the listener alerts BIG-IP GTM and the system either handles the traffic locally or forwards the traffic to the appropriate resource. You control how BIG-IP GTM responds to network traffic on a per-listener basis. The number of listeners you create depends on your network configuration and the destinations to which you want to send specific DNS requests. For example, a single BIG-IP GTM can be the primary authoritative server for one domain, while forwarding other DNS requests to a different DNS server. Regardless of how many listeners you configure, BIG-IP GTM always manages and responds to requests for the wide IPs that you have configured on the system.

Task summary
Perform these tasks to delegate DNS traffic to wide IPs.

Creating a delegated zone on a local DNS server

Determine which DNS servers will delegate wide IP-related requests to BIG-IP GTM. If you are using BIND servers and you are unfamiliar with how to modify the files on these servers, consider reviewing the fifth edition of DNS and BIND, available from OReilly Media. In order for BIG-IP GTM to manage the web applications of store.siterequest.com andcheckout.siterequest.com, you must create a delegated zone on the DNS server that manageswww.wip.siterequest.com. Perform the following steps on the selected DNS server.

1.

Create an address record (A record) that defines the domain name and IP address of each BIG-IP GTM in your network. 2. Create a nameserver record (NS record) that defines the delegated zone for which BIG-IP GTM is responsible. 3. Create canonical name records (CNAME records) to forward requests for store.siterequest.comand checkout.siterequest.com to the wide IPs store.siterequest.com andcheckout.siterequest.com, respectively.

A delegated zone for store.siterequest.com and checkout.siterequest.com exists on each DNS server on which you performed this procedure.

Creating a listener to handle traffic for wide IPs

Determine the self IP address of BIG-IP GTM. Create a listener on BIG-IP GTM that identifies the wide IP traffic for which BIG-IP GTM is responsible.

1. 2. 3. 4. 5. 6.

On the Main tab, click Global Traffic > Listeners . The Listeners List screen opens. Click Create. The new Listeners screen opens.

In the Destination field, type the IP address on which BIG-IP GTM listens for network traffic. The destination is a self IP address on BIG-IP GTM. From the VLAN Traffic list, select All VLANs. From the Protocol list, select either UDP or TCP. Click Finished.

Implementation results
You now have an implementation of BIG-IP GTM in which the DNS server manages DNS traffic unless the query is for store.sitrequest.com or checkout.siterequest.com. When the DNS server receives these queries, it delegates them to BIG-IP GTM, which then load balances the queries to the appropriate wide IPs.