With no usable cached delegation, where can an iterative DNS lookup begin?
- The old server named in a previous answer
- A root server, which gives the first referral
- The browser's screen before any network query
What can DNS resolution return for a human-readable name?
- An address or other record associated with the name
- A password that grants access to an administrator
- A folder containing all page files for the site
What does a DNS TTL tell a caching resolver?
- The length of the domain name
- The speed at which packets cross the network
- How long a cached record may be reused
A cached record has a one-hour TTL. When may the resolver need to ask for it again?
- After one second, whether or not the answer is needed
- After an hour has passed, when a lookup next needs that record
- Never, because cached records remain valid for every later lookup
After a .com server refers the resolver to example's authoritative servers, what happens next?
- The resolver asks an authoritative server for the record
- The resolver goes back to the browser without asking
- The root server replaces the delegation with an address
Right after an address change, every user sees the new server at once.
Circle one: True False
Caching can make repeated name lookups faster by avoiding a full hierarchy walk.
Circle one: True False
A site moved servers, but you still reach the old server hours later. What best explains this?
- The screen is showing an old copy of the page layout
- The root server deleted the new address
- A cached DNS answer still has time left before expiry