Campus lab PCs at a university resolve a host when students type the full domain, and single-label names fail because the client search suffix is empty. What should be fixed?
Select an answer to reveal the explanation.
Short Explanation
A search suffix is the rest of the address your client adds when you write only the first line. You fix the DNS suffix or resolver on the endpoint so those short names expand. The WAN is not in the path of a name that never became a lookup for the right domain.
Full Explanation
Full domain names resolve, and single-label names fail while the client search suffix is empty. The resolver on the endpoint is working for names that are already complete, and the missing piece is the DNS suffix that should expand short names before they are queried. Fixing the endpoint DNS suffix or resolver addresses that gap on the lab PCs. Replacing the WAN circuit would matter for traffic that exists only after a name has resolved to an address, and these short names are failing before that. A BGP alert for the campus DNS prefix watches routing to servers that already answer when the full domain is typed. Placing a data-center Enterprise Agent nearer those DNS servers adds a probe by the servers and does not fill in the search suffix on the lab PCs. Exam caveat: a resolver that answers fully qualified names can still fail everyday short names when the search suffix on the client is empty. Operational check: on a lab PC, compare a full-domain lookup with a single-label lookup, then confirm the short name expands once the endpoint suffix is set.