The vulnerability description clearly states that the Hickory DNS resolver followed irrelevant CNAME records, leading to increased query amplification. The provided patch commits directly address this behavior within the RecursorDnsHandle::handle_response function. The first commit (4689fc8d3ddd3e3f99ec1b7be4e2e9e78afd2e6b) narrows the scope of CNAME processing from all_sections() to answers.iter(), preventing the resolver from querying CNAMEs in the authority or additional sections. The second commit (ccd6952378f250c714fc2af0cb1053e1c179f832) then refines the CNAME following logic within the answer section itself. It ensures that only CNAMEs directly related to the current query name are considered and introduces a mechanism to track the CNAME chain (effective_qname, name_history) to prevent infinite loops and unnecessary queries. Both changes are critical to mitigating the described vulnerability, indicating that the handle_response function was the central point of the flawed CNAME resolution logic.