How does Infoblox handle DNS caching across the grid?

• A. Disables caching to ensure up-to-date answers
• B. Caches query results locally according to TTLs to improve performance
• C. Caches every query indefinitely
• D. Shares the cache data only between grid masters

Answer: (B)

Caching behavior and TTL control Infoblox DNS performance across the grid. When a DNS query is answered, the result is stored in the local cache of the DNS server that handled the query. Each cached entry stays valid for the duration specified by the resource record’s TTL (time to live). While that TTL remains valid, subsequent identical queries can be served from cache, delivering faster responses and reducing load on upstream servers. Once the TTL expires, the entry is removed or refreshed, ensuring data isn’t kept longer than allowed. This approach keeps responses quick and scalable, with caches being local to each grid member rather than shared across grid masters, and it avoids indefinite caching.