Google Chrome to forcefully use Google DNS

This article is bogus. Nowhere in the original G+ article does the author suggest that Chrome would switch to using Google's public DNS resolvers by default, which is what she implies.

And then she throws in the spurious claim "there is very little to stop Google should it decide there is a compelling need to closely inspect unencrypted packets hitting its DNS servers" which is absurd considering their DNS resolvers are obviously already doing exactly that in order to respond to the DNS queries! Ridiculous. But it all suffices to set up the obligatory Facebook competition angle.

And mainstream media outlets wonder why they're struggling...

An interesting note. Typekit (the embedded font webservice) went done for all my site while I was using the google DNS. After reverting to my ISP DNS, I was able to have the typekit service work.

Locking in a DNS provider is bad.