Today, as part of our ongoing effort to make the web faster, we're launching our own public DNS resolver called Google Public DNS, and we invite you to try it out.If you're web-savvy and comfortable with changing your network settings, check out the Google Code Blog for detailed instructions and more information on how to set up Google Public DNS on your computer or router.I think that I will give it a go....The goal of Google Public DNS is to benefit users worldwide while also helping the tens of thousands of DNS resolvers improve their services, ultimately making the web faster for everyone.
Link: Google Public DNS
Source: Official Google Blog
Seems to be loading web pages quicker for me than with my ISP's dns.
FYI google dns =
8.8.8.8
8.8.4.4
nice easy ip to remember!
How long before they try to be OpenDNS?
I have just put it in place at home and it does seem faster.
+1 rep to the OP for that!
Put it on my router as primary DNS (left OpenDNS as secondary) and wow what a difference! I'll have to give a try at work in the morning and see if it is usable through the myriad of firewalls the LA/RBC have placed in our way.
Wow nice and fast, will try these at work tomorrow.
Anyone saying that this "feels faster" is just feeling the placebo effect. I'm at a total loss as to how this would ever be faster from a practical point of view.
Instead of querying a server that's within your ISP's local network, that will be within 1 hop and likely has a ton more bandwidth assigned to it than you'll ever have, your going half way around the web on your home connection. Unless your ISP's DNS server is a 486, then it's massive waste of resources and will actually slow you down.
Once a hosts address is resolved, it will have absolutely sod all bearing on how fast a page loads. Zilch.
Not only that, but the majority of internet users probably only visit a handful of websites, as such it's likely that they will already have a resolved address stored in their local DNS cache(either on the users PC or router) and even if they don't, it's likely that their ISP's DNS server does, which is again much closer to you network wise than Google's servers.
Anyway I bet virtually all of you who tried this, accessed a site that you'd already accessed that day, so not only do you/your ISP have the DNS entries cached already, you probably already have a fair amount of the webpages main content(images blah blah) in your local cache. Thus making it faster in other ways :P
Last edited by DrCheese; 4th December 2009 at 02:47 AM.
Aaaah Dr, you're a great big spoilsport :-)
However, interestingly I've just had a quick ping and found:
My ISP (Virgin):
Reply from 194.168.4.100: bytes=32 time=105ms TTL=239
Reply from 194.168.4.100: bytes=32 time=104ms TTL=239
Reply from 194.168.4.100: bytes=32 time=103ms TTL=239
Reply from 194.168.4.100: bytes=32 time=102ms TTL=239
Google:
Reply from 8.8.8.8: bytes=32 time=100ms TTL=242
Reply from 8.8.8.8: bytes=32 time=99ms TTL=242
Reply from 8.8.8.8: bytes=32 time=98ms TTL=242
Reply from 8.8.8.8: bytes=32 time=97ms TTL=242
Even though Google has data centres all over the place and therefore the result is likely to be from somewhere close by, I am surprised that the response time is quicker.
It looks like Google's argument is that they have a larger cache and use prefetching, and while this won't make a difference for looking up mainstream sites which are widely cached, it would do for les commonly browsed ones. More info: Performance Benefits
I've just amended mine at home!
and just done it here at work! (School)
It definately seems faster, but now I'm struggling to open my school's website when I'm on the school network...? Anyone else got this problem?
Did you change your own workstation's DNS settings, and does your internal DNS server resolve your website hostname to some internal address? If yes, then you will need to remove the Google DNS settings from your computer, or add an entry for it to your hosts file.Originally Posted by bandgeekmafia78
This maybe a stupid question, but by doing this can Google now monitor what we are looking at on the web?
They will know that my IP address has requested Website A and so can assume I have an interest and then target adverts?
Similar I guess to a Tesco ClubCard.
Also, can someone explain how their IP address works? 8.8.8.8? How is that allowed (lack of knowledge there)
GJE
They have a pretty clear privacy statement. It definitely shouldn't result in more targetted ads...
8.8.8.8 is allowed because it's an IP address? Not sure what's wrong with that... It's a valid IP they own and they've obviously tried to find a nice easy to remember one. I used to use 4.2.2.4 in emergencies a long time ago - now 8.8.8.8 can top the list.We do keep some location information (at the city/metro level) so that we can conduct debugging, analyze abuse phenomena and improve the Google Public DNS prefetching feature. We don't correlate or combine your information from these logs with any other log data that Google might have about your use of other services, such as data from Web Search and data from advertising on the Google content network. After keeping this data for two weeks, we randomly sample a small subset for permanent storage.
Only when things are served from different domains - which admittedly is the case with lots of portal-style websites. Typically they will have different hosts for their own assets like CSS, images and javascript files (to do with browsers & multiple HTTP connections per host); and then many more hosts involved for the varying advert servers.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote