* Patrick Vande Walle wrote:
Lutz Donnerhacke wrote, On 7/12/09 21:29:
This kind of technocentric approch is interesting, because it's highlights the net neutrality issue and the seperation of the Internet and the GoogleNet.
As others said, this article is a bunch of crap. Actually, Google is now offering a plain vanilla DNS service that ISPs are more and more unwilling to offer. ISPs and folks at OpnDNS love to make their DNS servers lie. At least, Google returns an NXDOMAIN for failed queries. They respect TTLs, too, unlike some ISP resolvers.
I do not want to discuss technical issues here. Google DNS is doing right. I'd like to mention the political implications. Google offers DNS for commercial reasons. NXDOMAIN rewriting is done by ISPs for obtaining a bit of the money usually payed to Google alone. So Google DNS ensures the money flow as it is. Google DNS gives Google the opportunity to register trends very early, even if the pages are not yet spidered. I do not imply, that those ISP nor Google are "allowed" to do so. My personal impression is to avoid advertising at all. The quoted article is interesting, because it draws the picture a bit more into the future: A separate overlay network named Google. You might consider this FUD, but my fear comes from the Dejanews archive, which was altrustically provided by Google for years. Now we are facing the problems, that Google Groups are a supernet to the Usenet. Google extended the Usenet by avoiding the group creation process at all. They simply offer additional groups at their own side. Consider the same mechanism for DNS ... We will receive an other INAIC, but this time it will work. BTW: INAIC also first spidered, before offering "services": whois -h whois.inaic.net bofh
The only thing that is questionable in Google DNS is that they are pre-fetching DNS records before they expire so they are always in their cache. With DNSSEC, this is probably bad.
That's not a problem at all. (Spreading FUD, this is only to keep the GoogleNet Database up to date, as they are doing it for the web pages.) There are technical problems with amplification attacks. I expect up to 30Gbps. https://lists.dns-oarc.net/pipermail/dns-operations/2009-December/004673.htm... And there are serve privacy issues in conjuntion with Chrome. Chrome prefetches the FQDN for those links, the mouse is hovered on. This way Google is able to trace how a user works with a web page. Of course, if Chrome would record the user actions directly and send them to home, everybody will cry loud.