3 ms·
The timing of this is funny. On the one hand, Google introduces a faster DNS service. On the other hand, one of the videos shows how DNS pre-fetching in Chrom
by amichail 17y ago
The timing of this is funny. On the one hand, Google introduces a faster DNS service. On the other hand, one of the videos shows how DNS pre-fetching in Chrome means that DNS lookup speed is not that critical.
- eli 17y agoit doesn't mean it's not that critical... it means it's a problem, and that different teams are trying to solve it from different angles.
- amichail 17y agoIt does take away much of the incentive to use a faster DNS service though.
- pyre 17y agoIt's not like people not using Google DNS is losing them money.
- notauser 17y agoIt does if they are using OpenDNS or an ISP like Comcast (if they still do DNS interception?). These organizations redirect failed lookups to their own search pages and sell the traffic on for a price or show their own ads. The alternative is a clean failure which gets handled by the browser. I believe that most browsers send you to the default search in those cases - which is usually Google. There's a kickback involved in that case too (searches from Firefox earn Mozilla a small fee for example) but I wouldn't be surprised if it was cheaper.
- InclinedPlane 17y agoGoogle is going for a belt and suspenders approach here. On the one hand they are encouraging people to dump DNS servers from crappy ISPs (of which there are many). This benefits everybody regardless of their browser. On the other hand google is implementing and promoting dns prefetching in the browser in order to sidestep the problem of page load overhead due to dns lookups. Though neither method is perfect they complement each other well.