What are the recommendations to prevent DNS cache poisoning?

Keep your resolver private and protected. Protections built in to DNS software to protect against cache poisoning include adding variability to outgoing requests, to make it harder for a hacker to get a bogus response accepted. Possible ways of doing this include:

• using a random source port (instead of UDP port53)
• randomizing the query ID
• randomizing the case of the letters of the domain names that are sent out to be resolved. (That's because name servers will treat example.com and ExaMPle.com the same when it comes to resolving the IP address, but it will reply using the same case as the original query.)