On a workstation, `ping 8.8.8.8` succeeds with normal round-trip times, but `ping www.example.com` fails immediately with a message that the name or service is not known. Which two causes are consistent with these symptoms? (Choose two.)
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
Choose 2.
Not correct The interface is administratively down
Wrong. A down interface could not have sent the successful pings to 8.8.8.8. Those replies prove layer 1 to layer 3 are working.
Correct /etc/resolv.conf lists no nameserver, or lists one that is unreachable
Correct. Without a usable name server the resolver cannot translate the name, and the failure is reported as a resolution error rather than as packet loss.
Not correct No default gateway is configured
Wrong. Without a default route the ping to the off-link address 8.8.8.8 would itself have failed with a network-unreachable error.
Correct The hosts line in /etc/nsswitch.conf has been edited so that it lists neither files nor dns
Correct. That line tells the C library which sources to consult for hostname lookups. With no usable source listed, every name lookup fails while traffic sent straight to an IP address is unaffected. (Note that deleting the line altogether would not do this: glibc falls back to a built-in default that still includes dns and files.)
Not correct A local firewall is dropping outbound ICMP echo requests
Wrong on two counts: the successful ping to 8.8.8.8 shows ICMP is getting through, and a blocked ICMP packet would produce a timeout, not a name-resolution error.
Why
The classic split diagnosis: pinging an IP address exercises the interface, the routing table and the path; pinging a name additionally exercises name resolution. When the address works and the name does not, the fault is above layer 3, in resolution. Check /etc/resolv.conf for nameserver entries, /etc/nsswitch.conf for the hosts line, and query directly with `dig @NAMESERVER www.example.com` and `getent hosts www.example.com` to see whether DNS or NSS is at fault.
Where this comes from
- Cited
- LPI exam objective 109.3
- What it says
- Diagnose common network problems by isolating which layer has failed.
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