101 · Question #115
A GTM System performs a name resolution that is not a WideIP. The name is in a domain for which the GTM System is authoritative. Where does the information come from?
The correct answer is A. It comes from BIND database (zone) files on the GTM System.. When a GTM System is authoritative for a domain and receives a query for a non-WideIP name, it resolves the name using its local BIND zone files.
Question
A GTM System performs a name resolution that is not a WideIP. The name is in a domain for which the GTM System is authoritative. Where does the information come from?
Options
- AIt comes from BIND database (zone) files on the GTM System.
- BGTM System cannot resolve a host name that is not a WideIP.
- CIt comes from the database of previously cached name resolutions.
- DIt comes from a zone transfer initiated when the request was received.
How the community answered
(29 responses)- A93% (27)
- C3% (1)
- D3% (1)
Why each option
When a GTM System is authoritative for a domain and receives a query for a non-WideIP name, it resolves the name using its local BIND zone files.
F5 GTM runs an embedded BIND instance and can host standard DNS zone files. For names within its authoritative zones that are not defined as WideIPs, the GTM resolves them directly from those BIND zone database files, just as a standard authoritative DNS server would.
GTM can resolve any name within its authoritative zones - not only WideIPs - because non-WideIP records are served from the BIND zone files it hosts.
Cached resolutions apply to recursive or non-authoritative lookups, not to names for which the GTM itself holds authoritative zone data.
Zone transfers replicate zone data between servers and are not triggered per query - the local zone files already contain the authoritative answer.
Concept tested: F5 GTM BIND zone file authoritative resolution
Source: https://techdocs.f5.com/en-us/bigip-15-1-0/big-ip-dns-implementations.html
Topics
Community Discussion
No community discussion yet for this question.