If absolute assurance is required, deploying DNSSEC may be appropriate for your zones. That, along with DNSSEC-aware recursive nameservers, is the "best" way to ensure that recursive nameservers provide the correct answer.
For a more realistic answer
, the first part of your question makes it sound like you're concerned about Linode's recursive nameservers (the ones in your resolv.conf), but the second part makes it sound like you're concerned about Linode's authoritative nameservers (the ones you point your domain at). The latter are, strictly speaking, not susceptible to cache attacks as they aren't recursive nameservers. The former, as with all other recursive nameservers, are at least a little bit susceptible. The situation used to be worse, but there have been improvements in recent years with how recursive nameserver software operates.
There is nothing you can do about your end users' recursive nameservers other than transitioning to DNSSEC and hope they've got secure connections to nameservers that support and validate DNSSEC. This is not common.