Slashdot Mirror


Google Launches Public DNS Resolver

AdmiralXyz writes "Google has announced the launch of their free DNS resolution service, called Google Public DNS. According to their blog post, Google Public DNS uses continuous record prefetching to avoid cache misses — hopefully making the service faster — and implements a variety of techniques to block spoofing attempts. They also say that (unlike an increasing number of ISPs), Google Public DNS behaves exactly according to the DNS standard, and will not redirect you to advertising in the event of a failed lookup. Very cool, but of course there are questions about Google's true motivations behind knowing every site you visit."

3 of 540 comments (clear)

  1. Re:At least they have a clear privacy policy by Ziekheid · · Score: 0, Offtopic

    Quis custodiet ipsos custodes?

  2. Register this connection's addresses in DNS? by Futurepower(R) · · Score: 0, Offtopic

    Thanks again for your help.

    Another question: In Windows XP, what does this setting mean:
    "Register this connection's addresses in DNS"

    I found that at Start/ Settings/ Network Connections/ Choose the connection/ Internet Protocol (TCP/IP)/ Properties/ General/ Advanced/ DNS/

    In the same tab, what do these settings mean?
    "Append primary and connection specific DNS suffixes"
    "Append parent suffixes of the primary DNS suffix"

  3. OpenDNS is faster by ksemlerK · · Score: 0, Offtopic
    Open DNS is still faster then Google.

    C:\Users\*****>ping -a 8.8.8.8

    Pinging google-public-dns-a.google.com [8.8.8.8] with 32 bytes of data:
    Reply from 8.8.8.8: bytes=32 time=82ms TTL=244
    Reply from 8.8.8.8: bytes=32 time=79ms TTL=244
    Reply from 8.8.8.8: bytes=32 time=80ms TTL=244
    Reply from 8.8.8.8: bytes=32 time=81ms TTL=244


    Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 79ms, Maximum = 82ms, Average = 80ms

    C:\Users\*****>ping -a 208.67.222.222



    Pinging resolver1.opendns.com [208.67.222.222] with 32 bytes of data:
    Reply from 208.67.222.222: bytes=32 time=51ms TTL=53
    Reply from 208.67.222.222: bytes=32 time=48ms TTL=53
    Reply from 208.67.222.222: bytes=32 time=49ms TTL=53
    Reply from 208.67.222.222: bytes=32 time=61ms TTL=53


    Ping statistics for 208.67.222.222:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 61ms, Average = 52ms