said by nweaver:YES, changing DNS fixes this problem.
THIS particular tampering was based on changing DNS results from the recursive resolver, so using a third-party DNS (eg, Google Public DNS) fixes the problem.
And once people start doing this, more ISPs (there are already many doing it how I describe over in Europe) will begin using transparent proxies (read: they don't look for DNS traffic, they transparently monitor your HTTP packets and obtain your search queries and results via that) to achieve the same thing. For example, Sandvine equipment is quite capable of doing this.
Folks can dance around the problem all they want -- go ahead, use different DNS servers. Use private VPNs that act as IP routing proxies, drive yourself batshit crazy getting it all to work. Use HTTPS everywhere and wonder why the web suddenly becomes a complete piece of junk performance-wise (read: you cannot cache HTTPS content). There are drawbacks to everything.
I'll stick with just browsing the web how I always have. If people want to see my search queries for Intel MCA/MCE architecture, working drafts for T13 ATA specifications, and other technical things, awesome. Let 'em. Couldn't care less. I don't feel my privacy is being "invaded" since if the ISP wasn't doing this, the search engine company could be. Paranoia has no bounds/ends, so I choose not to become paranoid.