Slashdot Mirror

← Back to Stories (view on slashdot.org)

How Does the New Google DNS Perform? (and Why?)

Posted by CmdrTaco on from the all-your-data-are-belong-to-me dept.

Tarinth writes "Google just announced its new Google DNS platform. Many have viewed this as a move to increase ad revenue, or maybe capture more data. This article explores those questions, as well as the actual benchmarking results for Google DNS — showing that it is faster than many, but not nearly as fast as many others." We also recently discussed security implications of the Google Public DNS.

2 of 275 comments (clear)

  1. Pointless hype by suso · · Score: 5, Interesting

    Its funny how the Google hype is driving so much talk about something like DNS, a service which probably 95% of non-tech people don't know exists. Most people
    wouldn't care about DNS normally, but since its Google it must be something to get excited about. I doubt really that any significant number of people will
    switch to using 8.8.8.8, but I worry that if they do, one of the the original goals for DNS will be lost. That its distributed.

    Just ask yourself one question, if you don't trust your internet provider enough to do DNS correctly, should you trust them at all?

    1. Re:Pointless hype by Anonymous Coward · · Score: 5, Interesting

      Fair enough -- you don't trust your ISP.

      How does using google's DNS help you? You really think your ISP isn't logging your DNS traffic regardless of if you're using their DNS servers or not? A simple tcpdump udp port 53 on a passive tap is enough for them to collect your DNS traffic no matter what you do unless you use TOR or a vpn.

      So, now google *and* your ISP have logs of what you've been looking up. How are you better off?

      Oh -- and if you really don't trust your ISP, how are you to be sure that they aren't redirecting your port 53 traffic to their DNS servers *anyway*? Comcast -- I'm looking at you... Why is it that 5% of responses that *should* be an NXDOMAIN from a root server instead are an A record to some site that happens to be running a web server?