Exercise 1: Same Failure, Different Wording — Possible Solution
====================================================================

WHY THE ASSUMPTION CAN BE WRONG
------------------------------
Per this chapter's finding-box, "a single DNS response code can look
completely different depending on which tool reports it." Two failure
messages that read completely differently in plain English can still
be reporting the exact same underlying DNS response - the tools just
phrase it differently, not because the underlying cause differs.

THE SPECIFIC EXAMPLE FROM THIS CHAPTER
------------------------------
Per this chapter, a name that doesn't exist produces a literal
"status: NXDOMAIN" line in dig's output, but the exact same underlying
failure shows up in nslookup as a plain-English sentence: "can't find
... : Non-existent domain." Both tools are reporting the identical
NXDOMAIN condition - one just states the DNS status code directly,
the other translates it into a human-readable sentence.

WHAT ACTUALLY MATTERS INSTEAD
------------------------------
Per this chapter, "recognizing that both are reporting the exact same
underlying DNS failure - not two different problems - matters more
than memorizing either tool's specific wording." The lesson is to look
past each tool's own phrasing to the underlying DNS response code
itself, since that's what's actually diagnostic, not the sentence
structure a particular tool happens to use.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies that the two error messages can represent one
identical underlying condition, cites the chapter's own NXDOMAIN
example showing both tools' exact wording, and explains why looking at
the underlying DNS status matters more than comparing surface wording
between tools.