Google recently launched it’s Public DNS service with a claim that they are looking to make the browsing experience faster. A faster internet is something that is very crucial to Google considering it’s domination of the internet. So with Google Public DNS they are looking to give us more options.
Google Public DNSMany amongst you might already know that DNS (Domain Name System) is used to fetch a website to your browser when you type in the URL. This DNS address is usually provided by your ISP (Internet Service Provider).An Open or Public DNS is basically an alternative that can be used instead of the DNS address allotted by your ISP.* Changing to Google Public DNS would be a good idea if your ISP has DNS issues and a really good indication of that is if you are getting a lot of “Page not found” errors even with a decent internet speed.* Google Public DNS will store some private information of the user in a temporary log. This information with include the full IP address of the computer you are using. These temporary logs will be deleted every 24-48 hours.* There is quite a lot of information that will be stored in permanent logs which is mostly performance oriented. Some information of your location will be stored at the city/town level. This is being done for debugging and also improve the prefetching feature of Google Public DNS.* On the privacy front, Google will not link or co-relate any other logs of your usage with the Public DNS logs. In simpler words they will not collect details of your internet usage and then relate it to lets say your Google account.Monetizing Redirection?* There will be some redirection concerns when using Google Public DNS. Redirection takes place when a page cannot be fetched incase the web address is entered incorrectly.* Google has been silent on this at the moment but really nothing can stop Google to show advertisements or redirect to Google search when a page cannot be fetched while using its DNS.What good can come out of Google Public DNS?An ISP which does not have a great record with it’s DNS servers might not get a lot of attention except by it’s estranged customers. Google being the internet giant it is, will be scrutinized very minutely and will receive bad press if it does not get Public DNS right.This is a good thing as Google Public DNS still has to offer new services which can help filter and tune up your internet experience.Let me know your experiences and thoughts on Public DNS through your comments.You want to know more then visit this Link:http://code.google.com/speed/public-dns/docs/using.html
You need to be a member of MyEnglishClub to add comments!
Hi,Use this http://www.ip-details.com/ site for known your IP address with necessary details and also you known your system;s internet speed at free of cost ,visit here for more details.
IP-Details.com : Find your IP address Information
IP-Details.com, Search and find ip address's,domain name host's whois information including city, country, global latitude & longitude coordinates.
Well I'm not too knowledgeable about these things. I just base on simple logic that if a ISP suck so greatly that can't provide even a well working DNS servers, then it's very dubious that it can provide a good link to google's dns server.
Anyways before switching to another dns server it might be good to bing and traceroute dns servers first.
My bing to google's primary dns 8.8.8.8
sh-4.0$ 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=242 time=39.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=242 time=39.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=242 time=39.0 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=242 time=39.5 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=242 time=39.4 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=242 time=39.4 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=242 time=39.7 ms
^C
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 39.034/39.524/39.846/0.341 ms
To the dns that my ISP provides:
--- xxx.xxx.xxx.30 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7010ms
rtt min/avg/max/mdev = 1.262/1.364/1.483/0.074 ms
The average time difference is ~29 (It takes 29 times longer to reach to google's dns from my computer) It's normal that it takes so long because ISP dns server is nearby.
tarceroute to google's dns took 12 hops and to My ISP's dns provided by dhcp took 4 hops.
Now the only thing that's left, is how well synced the ISP dns server's data is and how fast it's able to respond to dns query. But I know no way how I could get know that.
Actually, if you use a router, then there's usually a small dns cache server build in that keeps the dns data some time.. That means only first time query to outside dns server is made. Next time it's not needed. Same is for your computer. It stores the dns data a while. :)
So my conclusion is that it doesn't speed anything noticeably up. It instead slows Internet down, :D but it's useful when you get page not found errors.
Or when google's name server is enough near to you(check ping and traceroute)
Or when your ISP suck so greatly that can't provide even a simplest well working dns cache servers. :)
actually i have a friend who told me about this and he send me a mail so i posted here.
but before posting, i searched in google for Google Public DNS then i got it: http://code.google.com/speed/public-dns/docs/using.html
and today i again searched in google for whts opinion of user, because i have no idea about this. is it really working or not? so i had left a comment in your profile. i thought that may be you that so i wanted to discuss with you.
I doubt that this could really speed anything up. It might in some cases, but.. Most what it does is that google will be able to collect even more data about you. it will know exactly which websites you visit. And target the adds for you according to that data.
Well actually I have had some issues with browsing in web. I have to use refresh button very often, because server won't respond. It often won't load in first time.
It started when my isp changed the Internet connection from pppoe to dhcp, but I don't believe that this is dns issue. I have thought that it's something else, like some broken proxy server that is forcefully added to my line or smth. Or it's made so by ISP on purpose to force me to buy more expensive packet.. that have up to 12Mbs Internet speed and digital tv. And other nonsense that I don't need.
Replies
Thank you for giving here a url of Open DNS
again u give me surprise, what a analysis and your calculation. you are really genius hardi.
thank you hardi for sharing your opinion & conclusion.
Anyways before switching to another dns server it might be good to bing and traceroute dns servers first.
My bing to google's primary dns 8.8.8.8
sh-4.0$ 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=242 time=39.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=242 time=39.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=242 time=39.0 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=242 time=39.5 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=242 time=39.4 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=242 time=39.4 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=242 time=39.7 ms
^C
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 39.034/39.524/39.846/0.341 ms
To the dns that my ISP provides:
--- xxx.xxx.xxx.30 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7010ms
rtt min/avg/max/mdev = 1.262/1.364/1.483/0.074 ms
The average time difference is ~29 (It takes 29 times longer to reach to google's dns from my computer) It's normal that it takes so long because ISP dns server is nearby.
tarceroute to google's dns took 12 hops and to My ISP's dns provided by dhcp took 4 hops.
Now the only thing that's left, is how well synced the ISP dns server's data is and how fast it's able to respond to dns query. But I know no way how I could get know that.
Actually, if you use a router, then there's usually a small dns cache server build in that keeps the dns data some time.. That means only first time query to outside dns server is made. Next time it's not needed. Same is for your computer. It stores the dns data a while. :)
So my conclusion is that it doesn't speed anything noticeably up. It instead slows Internet down, :D but it's useful when you get page not found errors.
Or when google's name server is enough near to you(check ping and traceroute)
Or when your ISP suck so greatly that can't provide even a simplest well working dns cache servers. :)
http://www.opendns.com/
actually i have a friend who told me about this and he send me a mail so i posted here.
but before posting, i searched in google for Google Public DNS then i got it: http://code.google.com/speed/public-dns/docs/using.html
and today i again searched in google for whts opinion of user, because i have no idea about this. is it really working or not? so i had left a comment in your profile. i thought that may be you that so i wanted to discuss with you.
if you want to see about user opinion of Google Public DNS: http://code.google.com/speed/public-dns/docs/using.html
Thank you Mr. Hardi
Well actually I have had some issues with browsing in web. I have to use refresh button very often, because server won't respond. It often won't load in first time.
It started when my isp changed the Internet connection from pppoe to dhcp, but I don't believe that this is dns issue. I have thought that it's something else, like some broken proxy server that is forcefully added to my line or smth. Or it's made so by ISP on purpose to force me to buy more expensive packet.. that have up to 12Mbs Internet speed and digital tv. And other nonsense that I don't need.