The BIG-IP DNS configuration has the following components:

• Listener: This is the BIG-IP DNS object that operates and answers to DNS queries. The listener configuration on BIG-IP DNS should be defined before executing the LBaaS workflow.
• Data center: This is a container object which host the place for application delivery components and has two LTM virtual servers from each site. The data center configuration on BIG-IP DNS should be defined before executing the LBaaS workflow.
• Server: This is a container object which host application components reside and can be a BIG-IP DNS, LTM server, or physical server instance. The server configuration on BIG-IP DNS should be defined before executing the LBaaS workflow.
• Virtual server: The virtual server has the IP address and service port configured on a physical server. BIG-IP DNS use these IP addresses and service ports to resolve queries and choose suitable virtual server.
• Pool: This is a logical object configured on the BIG-IP DNS system. Virtual servers can be set with different pools to resolve queries in a smart way. GSLB pool can be created by grouping all concerned virtual servers. Pool configuration for LBaaS will be customized on-demand using LBaaS workflow.
• Wide-IP: This is a logical container that is known as FQDN by grouping GSLB pools and have a batch of all concerned virtual servers. This object is developed and customized in the LBaaS workflow. The IP address for the FQDN will be restrained on Infoblox by leveraging a vRO workflow.
• DIG: The DNS resolution utility is a tool to experiment with wide-IP configuration and can be downloaded to a system. Users like to download the utility to the PowerShell desktop to check the acceptance of wide-IP configuration with the LBaaS workflow. The #dig @listener-ip wide-ip-name command will post a DNS query to the listener and show the response from BIG-IP DNS.