Store registers at a retailer fail to resolve the payment hostname, while a ping to that server's address succeeds. Which test should the team run?
Select an answer to reveal the explanation.
Short Explanation
You can reach the right door by address and still have the wrong name in the phone book. You run a DNS test, because the address replies and the hostname does not resolve. A path-quality test or a page-load test assumes the name has already been looked up.
Full Explanation
The registers cannot resolve the payment hostname, and a ping to that server's address succeeds. Forwarding to the address works, so the break is in name resolution, and a DNS test is the measurement that checks how the hostname resolves from the stores. A network test for loss and latency toward an address that already replies describes path quality, which is not the failure the registers are hitting. A voice test scores call quality on handsets, and nobody reported a voice problem at the registers. A web test loads a portal and times objects, which presumes a name or address to fetch and does not explain a hostname that fails to resolve. The registers are waiting on the name, so the test has to query that payment hostname from the store rather than score a call or time a page. Exam caveat: success by address and failure by name is the classic split between forwarding and DNS, so the next test follows the name. Operational check: run the DNS test for the payment hostname from a failing store and compare the result with the address that already answers a ping.