This is a part of what the recursive DNS server sees: To understand how this attack would work, take a look at a traditional DNS request from the user perspective and the DNS recursive server perspective.
Fortunately, this type of cache poisoning attack is no longer effective. The simplest form of this attack is to send additional A records with a request to a malicious domain. That data usually involves passing an incorrect A record to the recursive server in order to redirect traffic to infrastructure owned by the attacker. In a DNS cache poisoning attack an attacker takes advantage of flaws in the DNS protocol to load bad data into a recursive DNS server. Allan Liska, Geoffrey Stowe, in DNS Security, 2016 Cache Poisoning