DNS Traffic Control (DTC)
An Infoblox NIOS feature for DNS-based traffic steering using health monitors, servers, pools, topology, and load-balanced domain names. It supports GSLB-style responses from authoritative DNS.
Category glossary
Search all termsTraffic management
10 definitions associated with Traffic management.
DTC LBDN
A DTC Load Balanced Domain Name object that links a queried DNS name and record type to DTC pools and selection logic. It is the policy entry point for a DTC-managed answer.
DTC pool
A collection of DTC servers or endpoints with load-balancing and health behavior. Pools are associated with an LBDN and may be selected by topology or availability.
DTC server
An Infoblox DTC object representing an application endpoint and one or more service addresses or ports. Health monitors determine whether it is eligible for DNS responses.
GeoDNS
DNS response selection based on the estimated location or network of the requester. The decision may use resolver address, ECS data, latency, policy regions, or anycast ingress.
GSLB
Global Server Load Balancing, the use of DNS and health, geography, topology, or load information to direct clients to an appropriate application endpoint. Some vendors call it global traffic management.
Health check
An active or passive test used to decide whether an endpoint should receive traffic. GSLB systems may monitor TCP, HTTP, DNS, application content, or external telemetry before publishing an answer.
Monitor
A health-check definition used to determine whether a server or service is available. Monitors may run from one or multiple locations and can test transport, application content, or dependency health.
Pool
A collection of resources from which a service selects a member. In DHCP it is an address range; in GSLB or load balancing it is a group of application endpoints.
Topology ruleset
A DTC policy object that maps client, resolver, network, geography, or extensible-attribute conditions to an ordered set of pools or destinations.