Question 470
During an introductory open-source workshop, the task is: A user can ping a numeric server IP address but cannot access the service by hostname on a Linux laptop. What result confirms the intended Linux behavior?
Explanation
Correct Answer
The hostname resolves to an expected IP and the corresponding service opens by its name. This is specific evidence for the stated requirement. The explanation is: DNS converts hostnames into addresses; IP connectivity can work even when DNS resolution fails. The required action is: Check name resolution configuration and perform a host lookup against the intended domain.
Incorrect Answers
“A route lookup identifies a reachable next hop and permitted traffic reaches the remote subnet” tests the technical condition: Routing controls where packets go; a DNS search suffix cannot create a missing network path. The current control has another acceptance boundary: DNS converts hostnames into addresses; IP connectivity can work even when DNS resolution fails. Its direct evidence is “The hostname resolves to an expected IP and the corresponding service opens by its name”.
This test can succeed without resolving the cause described here. It addresses: An ICMP echo reply does not prove that a particular TCP service is listening or allowed by a firewall. The relevant causal dependency is: DNS converts hostnames into addresses; IP connectivity can work even when DNS resolution fails. The required validation is “The hostname resolves to an expected IP and the corresponding service opens by its name”.
The alternative measures an outcome associated with: A DHCP client receives an address and related network parameters from a configured network service. It does not verify the stated failure. Here dNS converts hostnames into addresses; IP connectivity can work even when DNS resolution fails. Confirm “The hostname resolves to an expected IP and the corresponding service opens by its name”.