Weekly Edition
Return to the Announcements page
| |||||||||||||
Introducing Google Public DNS: A new DNS resolver from Google
Google has announced
Google Public DNS, an experimental public DNS resolver.
"We believe that a faster DNS infrastructure could significantly improve the browsing experience for all web users. To enhance DNS speed but to also improve security and validity of results, Google Public DNS is trying a few different approaches that we are sharing with the broader web community through our documentation".
(Thanks to Jay R. Ashworth).
(Log in to post comments)
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 20:01 UTC (Thu) by kragil (subscriber, #34373) [Link]
Great, once the German government enables their DNS filters I give more of my privacy to Google for a reliable DNS server.
It really is a zero sum game.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 11:46 UTC (Fri) by akumria (subscriber, #7773) [Link]
What is stopping you from running your own recursive DNS server?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 20:03 UTC (Thu) by jebba (✭ supporter ✭, #4439) [Link]
tl;dr
The Google Public DNS IP addresses are as follows:
* 8.8.8.8
What fantastic IPs.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 21:52 UTC (Thu) by Banis (guest, #59011) [Link]
That was my first thought to. I wonder how much they had to pay to acquire such excellent IP's for this?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 23:18 UTC (Thu) by jebba (✭ supporter ✭, #4439) [Link]
Ya, they only got a /24 of each of them--it's not like they got some huge block. The address space was reassigned just in the last couple months from Level 3, who have 8.0.0.0/8 (!).
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 6:28 UTC (Fri) by olof (subscriber, #11729) [Link]
A bunch of the /8 networks are in possession of old-timers. Not exactly
news.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 10:16 UTC (Fri) by efexis (guest, #26355) [Link]
Does every statement of fact have to be?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 19:15 UTC (Fri) by paulj (subscriber, #341) [Link]
Probably nothing. 8.8.8.8 was already a well-known open, recursive DNS service, run by AS1 (BBN / Genuity, taken over by L3) - one of at least 2, I think. I'm not quite sure, but I think L3 eventually closed it down (anyone know?).
I bet thought that IP still got tonnes of requests, even if it was shut down. No doubt Google has been consulting people in the DNS community about their plans and no doubt it was suggested that re-using that well-known IP would be a good idea.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 10, 2009 12:26 UTC (Thu) by fragmede (subscriber, #50925) [Link]
4.3.2.1 is owned by Google (and does DNS).
~$ whois 4.3.2.1
I wonder how much they had to pay for /that/.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 13, 2009 2:25 UTC (Sun) by Baylink (subscriber, #755) [Link]
And L3/GTE/BBN/Genuity has recursive servers on 4.2.2.1-6 as anycast, in their various colos; for me, they're half a ms off the end of my fiber link.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 20:09 UTC (Thu) by arekm (subscriber, #4846) [Link]
No IPv6 addresses.
No IPv6 AAAA records published when asking for google services.
Fail in that area.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 22:23 UTC (Thu) by jasonpearce (guest, #5249) [Link]
Actually that makes a lot of sense and is inline with Google's general
approach to the IPv6 transition. There are unfortunately all too many end users that have an IPv6 address provided from transition technologies and their connectivity to the IPv6 Internet is not working well. Google would not be doing its customers or investors any good if it published AAAA records for its services generally.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 23:32 UTC (Thu) by bboissin (subscriber, #29506) [Link]
And they don't have cool IPv6 adresses like the one they got for IPv4.
Otherwise I totally agree, but it would be nice if they enabled AAAA
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 19:41 UTC (Fri) by jengelh (subscriber, #33263) [Link]
They could have easily chosen 2001:8:8:8:8 or something (2a01,whatever)...
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 5, 2009 0:15 UTC (Sat) by bboissin (subscriber, #29506) [Link]
By the way I wonder, are they any rules for the address chosen for anycast
in ipv6 (prefix or anything else)?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 7, 2009 16:01 UTC (Mon) by hmh (subscriber, #3838) [Link]
None. You can't even know if something is anycast or unicast...
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 9:35 UTC (Fri) by paravoid (subscriber, #32869) [Link]
That's an authoritative DNS "problem", not a recursor one.
And Google does have a "trusted IPv6" program that you can join and receive AAAA records for all Google services.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 9:41 UTC (Fri) by arekm (subscriber, #4846) [Link]
They don't trust themself and didn't add these resolvers to "trusted ipv6" program.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 12:46 UTC (Fri) by paravoid (subscriber, #32869) [Link]
It's not about the recursors, it's about the end users and the quality of their IPv6 network (tunnelled vs. native etc.).
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 20:11 UTC (Thu) by mmcgrath (subscriber, #44906) [Link]
I wonder how long it'll be before Google is the brand name of the Internet?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 7, 2009 14:10 UTC (Mon) by ikm (subscriber, #493) [Link]
I had just exactly the same thought.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 20:12 UTC (Thu) by dmk (subscriber, #50141) [Link]
wow, i don't believe it. but it really _is_ faster...
who would have thought, that 3 vs 1 dns querie makes such a difference?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 20:34 UTC (Thu) by jwb (guest, #15467) [Link]
From where I am testing, the ancient BBN resolver 4.2.2.4 is between 2 and 10
times faster than Google's new DNS.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 20:14 UTC (Thu) by Baylink (subscriber, #755) [Link] Lauren Weinstein of PRIVACY Digest has, of course, already raised the obligatory "they're looking over my shoulder" concerns, though mostly to dismiss them -- he's pretty happy with the 48 hour data retention policy they've promulgated, though he expects many of hisLance Ulanoff, for his part, asks on Twitter if "Google has co-opted the internet", and of course, they haven't. And comments in the inevitable Mashable posting talk about how OpenDNS does search-redirecting, without giving David credit for the fact that he *does* provide a way to turn that off. I'm a big Clausewitz fan, too...
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 21:01 UTC (Thu) by klevin (subscriber, #36526) [Link] And comments in the inevitable Mashable posting talk about how OpenDNS does search-redirecting, without giving David credit for the fact that he *does* provide a way to turn that off.True, but that option is only available to paying customers.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 21:04 UTC (Thu) by Baylink (subscriber, #755) [Link]
Yes, and how *dare* he give extra features to paying customers, when he gets all those servers and bandwidth for free!
Wait; what?
Someone *charges* him for that?
I'm shocked. Shocked, I tell you.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 21:24 UTC (Thu) by klevin (subscriber, #36526) [Link] Yes, and how *dare* he give extra features to paying customers, when he gets all those servers and bandwidth for free!Well, not really what I was saying. Just pointing out that, for free, Google DNS will just say, "hey, no record was found for that name." OpenDNS does all sorts of interesting stuff. However, one of the primary reasons for me not wanting to use my ISP's DNS is that they (Comcast) hijack lookup failures. So, I can either use Google's free DNS service, which doesn't hijack the lookup failure, or I can pay OpenDNS for the privilege of getting an accurate DNS response. Which am I gonna do?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 11:45 UTC (Fri) by akumria (subscriber, #7773) [Link]
Run your own recursive DNS server?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 12:18 UTC (Fri) by massysett (guest, #52736) [Link]
You can turn off what Comcast calls "domain helper". Login to the bill paying website (which apparently is comcast.com, not comcast.net) and click on "users and settings". There is a "domain helper" setting under "my devices".
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 18:59 UTC (Fri) by jwb (guest, #15467) [Link]
This doesn't really work and it's based on the MAC of the thing behind the
cable modem. I've "opted out" of that service dozens of times and it keeps turning itself back on.
I finally ended up just installing a local bind9.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 14, 2009 3:02 UTC (Mon) by tkil (subscriber, #1787) [Link] However, one of the primary reasons for me not wanting to use my ISP's DNS is that they (Comcast) hijack lookup failures. To their credit (probably after they got yelled at), Comcast does publish a list of clean / opt-out DNS resolver IPs. I don't know how well they work -- they look a little under-provisioned, honestly, with single IPs for multiple cities. And my previous residential gateway was dying about the time I was playing around with this. I now use the default DNS from my gateway for most of the computers, with pdns- recursor running on a spare box for when I feel the need for a bit more control.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 21:51 UTC (Thu) by Banis (guest, #59011) [Link]
This is not an extra feature. It's a violation of the DNS standard and destroys the security added by DNSSEC.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 20:27 UTC (Thu) by bangert (subscriber, #28342) [Link]
can i pay google for them to have my domain in their cache even though it
is not popular?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 22:47 UTC (Thu) by ahoogerhuis (subscriber, #4041) [Link]
Just query your domain name from their DNS'es and that should keep it in their cache? Add to crontab to match your TTL, and off you go.
If you feel like paying I have an account. :]
-A
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 0:01 UTC (Fri) by bangert (subscriber, #28342) [Link]
i doubt that that would work. if i understood correctly they cache based
on popularity, not on TTL[*], so my lone cron job will not be bringing my record into the cache - only a million hits or possibly a proper wallet will.
unless, of course, you assume google has infinite memory... oh wait!
[*] or rather popularity trumps TTL. if that were not the case, then their
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 2:18 UTC (Fri) by elanthis (guest, #6227) [Link]
The docs says they adhere to TTL lifetime. If they have more domain data being queried than what fits in cache, it makes sense for them to prioritize popular queries. Why should some dipshit with a little cash be able to slow down popular sites just so his domain that nobody is querying be kept in cache where it isn't needed?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 10:47 UTC (Fri) by efexis (guest, #26355) [Link] Perhaps moody, having people contribute to the cost of running the thing would allow it to be faster... anymore than a couple of pennies (or cents or whatever) will easily pay for the amount of memory required to hold the few handful of bytes a dns record takes up. Anything else you want to call somebody something for because you haven't thought it through? If so, this site might be of interest to you.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 11:38 UTC (Fri) by bangert (subscriber, #28342) [Link]
i didn't claim that they dont adhere to the TTL. The TTL determines when
they definitively through out a record.
But they will also actively refresh those records which are often used
therefore, my record, pulled into the cache via a hourly cron job, could
ie. they are ejecting records not on least recently used but they are
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 21:42 UTC (Fri) by dmk (subscriber, #50141) [Link]
they re-query the domain before end of TTL. thats one of the reasons of it being smth "new".
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 13, 2009 2:31 UTC (Sun) by Baylink (subscriber, #755) [Link]
The thing I *like* about OpenDNS is that if you have to change a record unexpectedly (IE: without having the opportunity to monkey with the TTL in advance), *you can force Open to re-read and re-cache it*; just as any random guy.
Does gDNS have that feature?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 11, 2009 23:24 UTC (Fri) by giraffedata (subscriber, #1954) [Link] Why should some dipshit with a little cash be able to slow down popular sites just so his domain that nobody is querying be kept in cache where it isn't needed? Because he's not having his name cached for his amusement. The money he's using to buy that service comes from his customers, who are willing to pay extra to be able to resolve his name quickly even though it isn't terribly popular. In other words, the public values quick lookups of some names more than others and it doesn't necessarily correlate with how frequently people look them up. LRU is a cheap way to estimate something that could be calculated more precisely with money-based trade.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 19:10 UTC (Fri) by jzbiciak (✭ supporter ✭, #5246) [Link]
Would that actually work? Ignoring TTL vs. LRU concerns, I would imagine their DNS IP addresses actually go to multiple servers for load balancing. Just because your IP is cached in one doesn't mean it'd be cached in all.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 3, 2009 23:45 UTC (Thu) by gdt (subscriber, #6284) [Link] If if gets popular than DNS-based DDoS may be an issue. It really depends if Google checks its peer's source addresses based on the peer's IRR contents. Likely to break the hack used by Akamai and similar for finding the location of a web page requestor. So international users will see their Akamai traffic come from the USA rather than from onshore. That would bring significant costs to those ISPs, and I'd totally understand if they forced their customers onto their own DNS forwarders to avoid provisioning more undersea capacity. The claims of speed are very sensitive to network-geographic location and to the size of the cache of the existing forwarder. For example, the Google forwarder is 180ms from my location, and so the much nearer Large Australian ISP's resolver beats it every time. What is good about the Google initiative is that it brings focus to the problem that poor DNS lookup times are now starting to dominate the user's web performance experience. If the Google service spurs ISPs into better DNS infrastructure (such as anycast DNS forwarders located within 15ms of every customer) then it will have done the world of good.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 0:03 UTC (Fri) by wmf (guest, #33791) [Link]
Are you assuming Google DNS is not anycast and located all over the world?
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 0:27 UTC (Fri) by cowsandmilk (guest, #55475) [Link]
I think based on the timing, it's pretty obvious that they don't have boxes in Australia. I'm sure with
popularity, they will soon. And I'm surprised they don't already, since they have offices in Sydney...
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 10:15 UTC (Fri) by forthy (guest, #1525) [Link] Well, I get ping times of about 13-14ms from Strato and TU Vienna, so it must be an anycast address.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 13, 2009 2:35 UTC (Sun) by Baylink (subscriber, #755) [Link]
Well, I just pinged it and was getting times between 450 and 1300 ms.
Course, I'm on EVDO... :-)
But, all seriousness aside, I was getting low 100's, basically link speed, from 4.2.2.1. So go figure.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 2:34 UTC (Fri) by glup (guest, #62317) [Link]
Luckily I have my own dnsmasq cache responding in millisecond time frame instead of 150+ms that is provided by ISP. Too bad I have noticed problem for negative response caching. Sometimes DNS system fails to resolve correct IP for one request and then my cache is poisoned for a few hours with bogus negative response.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 9:05 UTC (Fri) by roblucid (subscriber, #48964) [Link]
dnsmasq lets you configure the negative TTL set, if the negative response doesn't have TTL set by SOA record ( --neg-ttl=<time> ), and you can disable negative cache-ing entirely in dnsmasq.conf if it's causing you trouble.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 8:41 UTC (Fri) by zhirsch (guest, #46949) [Link]
SPDY, Go, now DNS. Google's getting a reputation for taking every day
infrastructure and "doing something" to make it faster.
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 4, 2009 10:55 UTC (Fri) by efexis (guest, #26355) [Link]
This is what you get when you give your employees their own time to work on their own projects with! An idea factory... not all good, not all successful, not all original, but add a little evolution through consumer selection and you've got yourself some winners :-)
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 5, 2009 12:49 UTC (Sat) by loevborg (guest, #51779) [Link]
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 5, 2009 14:13 UTC (Sat) by lab (subscriber, #51153) [Link]
"Has anyone heard of namebench? Looks interesting: http://namebench.googlecode.com"
Yes, I just tried it. Works great. I did 3 runs with it, to check out the performance of Google DNS, versus OpenDNS and my ISP's DNS, here from Copenhagen, Denmark, and you can see the result here: http://rubyglow.net/namebench-copenhagen.html
Introducing Google Public DNS: A new DNS resolver from Google Posted Dec 13, 2009 14:35 UTC (Sun) by pcampe (guest, #28223) [Link] Yes, I've tried it to check how fast Google Public DNS is, and summarizing: - better network path than Open DNS - faster than local DNS when your router has poor UDP NATting logic (because your local DNS has to do some recursive queries, each one being carried over UDP) - quite a big cache Details and graphs here: Google's Namebench and Your Name Server
|
|||||||||||||