The primary purposes of the Global Traffic Manager are 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 that a network must handle. One implementation of the Global Traffic Manager has the system become the authoritative name server for both wide IPs and all other DNS-related traffic. Typically, this implementation requires that the Global Traffic Manager replace an existing DNS server on the network.
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 the IP
address of the Global Traffic Manager. Since the Global Traffic Manager replaces an existing DNS server, this IP address must correspond with the IP address denoting the authoritative name server for the appropriate domain.
This solution covers the steps necessary to replace an existing DNS server
with the Global Traffic Manager. In this solution, the existing DNS server has an IP address of 192.168.5.73
, while the Global Traffic Manager has an IP address of 192.168.10.105
Here, the focus is 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
. These applications are subdomains of www.siterequest.com
, which are managed by an existing DNS server. SiteRequest has decided to replace its existing DNS server with the Global Traffic Manager. Earlier, SiteRequest configured the wide IPs that it needs on the system; the final task is to make the Global Traffic Manager the authoritative name server for our domains.
Before you configure the Global Traffic Manager to replace the existing
DNS server, you need to configure the DNS server to allow zone file transfers to the Global Traffic Manager. You can enable this authorization through the use of an allow-transfer
statement that specifies the IP address of the Global Traffic Manager: 192.168.10.105
. Please refer to your BIND documentation for more information on how to implement an allow-transfer
The next task you must accomplish before the Global Traffic Manager
becomes our primary DNS server is to acquire the siterequest.com
zone files from the existing DNS server. Again, this task requires that you have added an allow-transfer
statement to the existing DNS server that authorizes zone transfers to the Global Traffic Manager. You can acquire these zone files through the ZoneRunner utility.
At this point, you have configured the Global Traffic Manager as the
primary (master) DNS server for the siterequest.com
zone. You must now either change the existing DNS server to become a secondary (slave) DNS server to the Global Traffic Manager, or remove it from your network.
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.73
You now have an implementation of the Global Traffic Manager that is now
also the authoritative name server for siterequest.com
. This system now handles any incoming DNS traffic, whether destined for a wide IP or another node of siterequest.com