Google Invades ISP, OpenDNS Turf With Google Public DNS > Wait

Wait

How does Google Public DNS handle non-existent domains?
If you issue a query for a domain name that does not exist, Google Public DNS always returns an NXDOMAIN record, as per the DNS protocol standards. The browser should show this response as a DNS error. If, instead, you receive any response other than an error message (for example, you are redirected to another page), this could be the result of the following:

* A client-side application such as a browser plug-in is displaying an alternate page for a non-existent domain.
* Some ISPs may intercept and replace all NXDOMAIN responses with responses that lead to their own servers. If you are concerned that your ISP is intercepting Google Public DNS requests or responses, you should contact your ISP.

Yes... it's annoying that the article goes on and on about something (ad redirection for failed lookups) that Google is NOT DOING, and something that they clearly state is not their purpose. I think we should take them at their word, until there's reason to do otherwise.

Google also talks about "burning the logs", and not correlating this data with search queries or other personal info.
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

Well, the point was to give context into what has been driving these DNS changes, and on the ISP level its been DNS redirection -- without any effort to make DNS tools that are useful -- which is why OpenDNS has been so successful.

I saw Google's claims that this is all about altruism and efficiency -- and maybe it is as it begins to take root among engineers. But there's billions upon billions to be made from redirection ads and user tracking, and I find it very hard to believe they just plan to not bother touching that revenue once the project evolves.

reply to braden
Exactly. Google wants stuff to resolve quickly because web apps are their livelihood.

BTW, here are my ns_bench results. All 6 Level3 IPs, all four Comcast DNS servers for my area, my school's server, Google's servers...

Nameserver Response Time (ms)
min/avg/max/stdev/retries

4.2.2.1 16.00/43.80/78.00/24.73/0
4.2.2.2 47.00/50.00/62.00/6.00/0
4.2.2.3 15.00/46.80/63.00/17.53/0
4.2.2.4 46.00/53.00/63.00/7.77/0
4.2.2.5 31.00/50.00/78.00/15.31/0
4.2.2.6 16.00/34.40/62.00/15.03/0
8.8.4.4 93.00/103.00/110.00/7.77/0
8.8.8.8 93.00/99.60/109.00/7.68/0
68.87.85.98 0.00/9.40/16.00/7.68/0
68.87.69.146 47.00/50.00/62.00/6.00/0
138.67.1.2 15.00/15.60/16.00/0.49/0
68.87.85.102 0.00/12.40/16.00/6.22/0
68.87.69.150 47.00/68.60/93.00/20.76/0

reply to wmcbrine
And they reserve the right to change those policies whenever they want.

Like, say, when the service has become popular, the controversy has faded and it becomes profitable to gradually erode the privacy features.

I think you hit right on it.

My guess is they're approaching this in the opposite way ISPs did.

When ISPs saw what OpenDNS was doing, they quickly just rushed to make a buck from DNS redirection ads, without presenting any valuable DNS-related services to consumers.

Google's going to start by creating a valuable DNS service, and the supporting profit model comes later.

Again, I have a hard time believing Google execs will leave billions in potential ad and tracking revenue just sitting there out of goodwill.