An attacker can spoof such an answer packet as long as he can pretend to be the DNS server and also guess the source port and transaction ID (the destination port is usually 53) ... The attacker also needs to make sure his spoofed answer packet reaches the client before the actual answer packet from the legitimate DNS server.