Google Public DNS released
FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 1 2 LastLast
Results 1 to 15 of 21
  1. #1
    aleph's Avatar
    aleph is offline Banned (for/from) behaving just like everybody else!
    Join Date
    Jul 2007
    Location
    Nanjing, China
    Posts
    1,332
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Google Public DNS released

    tl;dr version: 8.8.8.8 and 8.8.4.4

    Project homepage:
    http://code.google.com/speed/public-dns/

    Logging privacy policy: http://code.google.com/speed/public-dns/privacy.html

    Killer feature: when you asks for a domain that doesn't exist, there are no side effects like redirection, correction or anything. Just NXDOMAIN. (How sad it is now considered a "feature" that is being advertised.)
    Code:
    from rlyeh import cthulhu
    cthulhu.fhtagn()

  2. #2
    Join Date
    May 2007
    Location
    U.S.
    Posts
    4,851
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Interesting. Thanks for the mention.

    I've been sticking with OpenDNS these days.
    - Tom
    "What is freedom? To have the will to be responsible for one's self." - Stirner

  3. #3
    Join Date
    Jul 2009
    Location
    London,England
    Posts
    1,102
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    cool, another easy to remember DNS ip for emergencies.

    There are others available, I often use 4.2.2.x , x=1...6, you can ping them to see which is fastest for your location

    Code:
    $ ping 8.8.8.8
    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    64 bytes from 8.8.8.8: icmp_seq=1 ttl=244 time=18.4 ms
    64 bytes from 8.8.8.8: icmp_seq=2 ttl=244 time=22.1 ms
    64 bytes from 8.8.8.8: icmp_seq=3 ttl=244 time=16.8 ms
    64 bytes from 8.8.8.8: icmp_seq=4 ttl=244 time=19.1 ms
    64 bytes from 8.8.8.8: icmp_seq=5 ttl=244 time=19.7 ms
    
    $ ping 8.8.4.4
    PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.
    64 bytes from 8.8.4.4: icmp_seq=1 ttl=244 time=17.5 ms
    64 bytes from 8.8.4.4: icmp_seq=2 ttl=244 time=17.6 ms
    64 bytes from 8.8.4.4: icmp_seq=3 ttl=244 time=18.4 ms
    64 bytes from 8.8.4.4: icmp_seq=4 ttl=244 time=16.7 ms
    64 bytes from 8.8.4.4: icmp_seq=5 ttl=244 time=16.7 ms
    
    $ ping 4.2.2.1
    PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data.
    64 bytes from 4.2.2.1: icmp_seq=1 ttl=247 time=10.7 ms
    64 bytes from 4.2.2.1: icmp_seq=2 ttl=247 time=11.4 ms
    64 bytes from 4.2.2.1: icmp_seq=3 ttl=247 time=10.0 ms
    64 bytes from 4.2.2.1: icmp_seq=4 ttl=247 time=10.9 ms
    64 bytes from 4.2.2.1: icmp_seq=5 ttl=247 time=10.6 ms
    
    $ ping 4.2.2.2
    PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
    64 bytes from 4.2.2.2: icmp_seq=1 ttl=247 time=29.5 ms
    64 bytes from 4.2.2.2: icmp_seq=2 ttl=247 time=29.5 ms
    64 bytes from 4.2.2.2: icmp_seq=3 ttl=247 time=28.9 ms
    64 bytes from 4.2.2.2: icmp_seq=4 ttl=247 time=29.2 ms
    64 bytes from 4.2.2.2: icmp_seq=5 ttl=247 time=24.1 ms
    
    $ ping 4.2.2.3
    PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data.
    64 bytes from 4.2.2.3: icmp_seq=2 ttl=247 time=10.1 ms
    64 bytes from 4.2.2.3: icmp_seq=3 ttl=247 time=11.4 ms
    64 bytes from 4.2.2.3: icmp_seq=4 ttl=247 time=10.3 ms
    64 bytes from 4.2.2.3: icmp_seq=5 ttl=247 time=10.3 ms
    64 bytes from 4.2.2.3: icmp_seq=6 ttl=247 time=10.3 ms
    
    ...
    4.2.2.1 and 4.2.2.3 have better pings than google for me, although that doesn't necessarily mean the overall dns lookup time will be faster, in this case the google servers are slightly slower (except for 4.2.2.2, which had a slower ping as well):

    Code:
    $ time nslookup www.google.com 4.2.2.1 >/dev/null
    
    real	0m0.032s
    user	0m0.006s
    sys	0m0.009s
    
    $ time nslookup www.google.com 4.2.2.2 >/dev/null
    
    real	0m0.044s
    user	0m0.007s
    sys	0m0.009s
    
    $ time nslookup www.google.com 4.2.2.3 >/dev/null
    
    real	0m0.030s
    user	0m0.006s
    sys	0m0.007s
    
    $ time nslookup www.google.com 8.8.8.8 >/dev/null
    
    real	0m0.036s
    user	0m0.008s
    sys	0m0.007s
    
    $ time nslookup www.google.com 8.8.4.4 >/dev/null
    
    real	0m0.037s
    user	0m0.006s
    sys	0m0.007s
    Let's see if this is an improvement over my default isp dns lookup:

    Code:
    $ time nslookup www.google.com >/dev/null
    
    real	0m0.031s
    user	0m0.008s
    sys	0m0.007s
    Nope

  4. #4
    Join Date
    Mar 2005
    Location
    Terre Haute, IN
    Posts
    261
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Perhaps the primary is getting hammered?

    Code:
    [andy@localhost ~]$ time nslookup www.google.com 8.8.8.8 >/dev/null
    
    real	0m15.234s
    user	0m0.003s
    sys	0m0.008s
    [andy@localhost ~]$ time nslookup www.google.com 8.8.4.4 >/dev/null
    
    real	0m0.043s
    user	0m0.002s
    sys	0m0.004s
    [andy@localhost ~]$
    F18

  5. #5
    aleph's Avatar
    aleph is offline Banned (for/from) behaving just like everybody else!
    Join Date
    Jul 2007
    Location
    Nanjing, China
    Posts
    1,332
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Code:
    $ dig @8.8.8.8 example.com | grep 'Query time'
    ;; Query time: 95 msec
    
    dig @8.8.4.4 example.com | grep 'Query time'
    ;; Query time: 79 msec
    Code:
    from rlyeh import cthulhu
    cthulhu.fhtagn()

  6. #6
    Join Date
    Mar 2006
    Location
    Wallingford, Oxfordshire, UK
    Age
    40
    Posts
    295
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    whats wrong with the dns servers provided your ISP??

    why do people use openDNS and others??

    I'm just curious as I've only ever used my ISP dns and probably always will
    Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
    Memory: 16GB
    OpenGL Renderer: GeForce GTX 550 Ti/PCIe/SSE2
    Operating System: Fedora release 20 (Heisenbug)
    Desktop Environment: KDE 4.1.12

  7. #7
    Join Date
    May 2007
    Location
    U.S.
    Posts
    4,851
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Personally, I started using OpenDNS when my ISP's DNS servers took a turn for the worst (slow lookups most of the time, and occasional poison). Though they may have been fixed since then I haven't really considered switching back since then.
    - Tom
    "What is freedom? To have the will to be responsible for one's self." - Stirner

  8. #8
    Join Date
    Jun 2006
    Location
    Paris, TX
    Posts
    24,107
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    My ISP decided to do a little social engineering, dropped some sites completely from their DNS list, and did some redirecting to "favored" businesses two years ago. Ever since then I've gone with OpenDNS.

    ISP=SuddenLink

  9. #9
    Join Date
    Mar 2006
    Location
    Wallingford, Oxfordshire, UK
    Age
    40
    Posts
    295
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by Dan
    My ISP decided to do a little social engineering, dropped some sites completely from their DNS list, and did some redirecting to "favored" businesses two years ago. Ever since then I've gone with OpenDNS.

    ISP=SuddenLink
    Oh wow, ok that's a valid reason, if I found out my ISP did things like that I'd probably change too
    Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
    Memory: 16GB
    OpenGL Renderer: GeForce GTX 550 Ti/PCIe/SSE2
    Operating System: Fedora release 20 (Heisenbug)
    Desktop Environment: KDE 4.1.12

  10. #10
    Join Date
    Jul 2009
    Location
    London,England
    Posts
    1,102
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Your look up times are on the slow side aleph, mine are faster, but google's dns isn't winning any races here, yet, probably getting high hit counts by testers atm:

    Code:
    $ dig @4.2.2.1 google.com | grep 'Query time'
    ;; Query time: 10 msec
    Google dns:
    Code:
    $ dig @8.8.8.8 google.com | grep 'Query time'
    ;; Query time: 33 msec
    
    $ dig @8.8.4.4 google.com | grep 'Query time'
    ;; Query time: 19 msec
    OpenDNS:
    Code:
    $ dig @208.67.222.222 google.com | grep 'Query time'
    ;; Query time: 19 msec
    $ dig @208.67.220.220 google.com | grep 'Query time'
    ;; Query time: 11 msec
    My default dns (from isp):
    Code:
    $ dig  google.com | grep 'Query time'
    ;; Query time: 11 msec
    Still, it's good to have these options, especially with reports of how some isps behave. These servers are also handy for people working under mildly restrictive regimes or corporations, although you need more sophisticated bypass techniques to get past something as severe as The Great Firewall of China

  11. #11
    aleph's Avatar
    aleph is offline Banned (for/from) behaving just like everybody else!
    Join Date
    Jul 2007
    Location
    Nanjing, China
    Posts
    1,332
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I cache all dns queries locally (by dnsmasq) so latency is not quite a problem.
    Code:
    from rlyeh import cthulhu
    cthulhu.fhtagn()

  12. #12
    Join Date
    Sep 2004
    Posts
    2,006
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    not so keen on this, gotta be google snooping/world-domination plans.

    if they wanted to help they should have just loaned some bandwidth/servers to opendns.org or implemented dnssec.

  13. #13
    Join Date
    Mar 2004
    Location
    In your closet
    Posts
    15,753
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Code:
    [glenn@leonardo ~>$ dig 68.87.71.230 | grep 'Query time'
    ;; Query time: 30 msec
    Maybe I'd benefit by changing to OpenDNS, no?

    If I make this change how will it impact everyday Internet usage here at home, web surfing, e-mail, etc?
    Last edited by glennzo; 4th December 2009 at 12:11 PM.
    Glenn
    The Bassinator
    © ®

  14. #14
    Join Date
    May 2007
    Location
    U.S.
    Posts
    4,851
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by sej7278
    not so keen on this, gotta be google snooping/world-domination plans.
    How'd I know that was coming? Lockbait in 3... 2... 1...

    Quote Originally Posted by glennzo
    Code:
    [glenn@leonardo ~>$ dig 68.87.71.230 | grep 'Query time'
    ;; Query time: 30 msec
    Maybe I'd benefit by changing to OpenDNS, no?

    If I make this change how will it impact everyday Internet usage here at home, web surfing, e-mail, etc?
    You might see a night-and-day difference in terms of DNS lookup times, or it could help DNS lookups slightly, or you might not notice a difference at all.

    If you have any rugrats running around this may be of interest, though I don't know if this requires the paid service.
    http://www.opendns.com/solutions/household/parental/

    Of course if said rugrats are capable of changing DNS servers, you're SOL.

    Also, OpenDNS's founder with a few words on Google's DNS:
    http://blog.opendns.com/2009/12/03/opendns-google-dns/
    - Tom
    "What is freedom? To have the will to be responsible for one's self." - Stirner

  15. #15
    Join Date
    Mar 2004
    Location
    In your closet
    Posts
    15,753
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Heh! Last "rugrat" is 15. Kicked the other 2 out years ago

    Guess you're telling me that what I need to do it give it a go. Maybe it will help, maybe not. Currently under Comcast's thumb.
    Glenn
    The Bassinator
    © ®

Page 1 of 2 1 2 LastLast

Similar Threads

  1. Google introduce Google Wave
    By Demz in forum Wibble
    Replies: 4
    Last Post: 31st May 2009, 09:40 AM
  2. Replies: 34
    Last Post: 29th September 2008, 07:55 AM
  3. Google Earth Beta (Version 4) released for Linux
    By smfinley in forum Using Fedora
    Replies: 108
    Last Post: 17th September 2007, 04:29 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •