The first nameserver in /etc/resolv.conf is unreachable, and every lookup on the host stalls for five seconds before the second server answers. Which resolv.conf directive shortens that per-server wait?
LPIC-1 Exam 102-500, objective 109. Networking fundamentals hard
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Correct options timeout:1
Correct. timeout sets how long the resolver waits for a reply from one name server before it moves on and retries; the default is five seconds.
Not correct options attempts:1
Wrong. attempts caps how many times the resolver cycles through the whole server list. Cutting it reduces the number of rounds but leaves each individual wait at the full timeout.
Not correct options rotate
Wrong. rotate makes the resolver round-robin over the listed servers between queries to spread load. Some queries would still start on the dead server and wait out the timeout.
Not correct options ndots:1
Wrong. ndots sets how many dots a name must contain before it is tried as absolute rather than being appended to the search list. It affects how many queries are sent, not how long each one waits.
Why
The glibc resolver's stall on a dead server is governed by two independent numbers: timeout, the seconds spent waiting on a single server before giving up on that try, and attempts, the number of passes made over the whole nameserver list. Lowering timeout is what shortens each individual wait; lowering attempts only reduces how often you pay it. Both are capped internally, timeout at 30 seconds and attempts at 5, and the true remedy for an unreachable resolver is to remove it from the list.
Where this comes from
- Cited
- manual page resolv.conf(5)
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 109 and space the ones you get wrong.
More questions on this objective
- A subnet is defined as 192.168.10.0/26. How many addresses in it can actually be assigned to hosts? machine-checked
- A host is configured with the address 172.20.35.77/20. What is the network address of its subnet? machine-checked
- In IPv6, which address is the loopback address, equivalent in role to 127.0.0.1 in IPv4? machine-checked
- Which is the correct fully compressed form of the IPv6 address 2001:0db8:0000:0000:0000:ff00:0042:8329? machine-checked
- Which pairing of a service with its default port number is correct? machine-checked
- DNS normally uses UDP port 53. In which situation does a DNS client or server fall back to TCP on port 53? machine-checked