Saturday, December 12, 2009

News article by NDTV-HINDU on Tamizh Bloggers



News article by NDTV-HINDU on Tamizh Bloggers - Video!




Interview with:





























Friday, December 4, 2009

Switch to Google Public DNS server and speed up your browser speed.



Most of us has not probably come into contact with DNS, the Domain Name System, yet although they make use of it everyday on the Internet. DNS is basically a system to convert domain names into IP addresses. 




The Internet Service Provider (ISP) is usually the one that is providing the DNS servers to the customer. This happens more often than not automatically. There are however reasons to switch to other DNS servers with performance, security and results are being three of the major reasons.


Google Public DNS implements a number of security, performance, and compliance improvements. We provide a brief overview of those enhancements below. If you're a developer or deployer of DNS software, we hope you'll also read the technical information pages on this site for more information on these features. Ultimately, our hope is to share our insights and inspire the community to adopt some of these features in all DNS resolvers. The changes are grouped into 3 categories:


  • Performance. Many DNS service providers are not sufficiently provisioned to be able to support high-volume input/output and caching, and adequately balance load among their servers. In addition to load-balancing user traffic to ensure shared caching, Google Public DNS implements "smart" caching to increase the speed of responses. Google Public DNS independently resolves domain names and keeps the resolutions in the cache until their time-to-live (TTL) expires, at which point they are automatically refreshed. The cycle of caching and refreshing is performed offline, asynchronously with user requests, so that responses are almost always available directly from cache. For more information, see the page on performance benefits.

  • Security. DNS is vulnerable to various kinds of spoofing attacks that can "poison" a nameserver's cache and route its users to malicious sites. The prevalence of DNS exploits means that providers have to frequently apply server updates and patches. In addition, open DNS resolvers are vulnerable to being used to launch denial-of-service (DoS) attacks on other systems. To defend against such attacks, Google has implemented several recommended solutions to help guarantee the authenticity of the responses it receives from other nameservers, and to ensure our servers are not used for launching DoS attacks. These include adding entropy to requests, rate-limiting client traffic, and more. For more information, see the page on security benefits.

  • Correct results. Google Public DNS does its best to return the right answer to every query every time, in accordance with the DNS standards. Sometimes, in the case of a query for a mistyped or non-existent domain name, the right answer means no answer, or an error message stating the domain name could not be resolved. Google Public DNS never blocks, filters, or redirects users, unlike some open resolvers and ISPs







How to set DNS:


Control panel / Network connections/ Select active connection/ Properties /Internet Protocol/ Properties/ Select Use the following DNS server address/8.8.8.8 and 8.8.4.4 /OK and exit.



(Before you change your DNS settings to use Google Public DNS, be sure to write down the current server addresses or settings on a piece of paper. It is very important that you keep these numbers for backup purposes, in case you need to revert to them at any time. )







To test that the Google DNS resolver is working:



  1. From your browser, type in a hostname, such as http://www.google.com. If it resolves correctly, bookmark the page, and try accessing the page from the bookmark. If both of these tests work, everything is working correctly. If not, go to step 2.

  2. From your browser, type in a fixed IP address. You can use http://18.62.1.6/ (which points to the website http://eecs.mit.edu/) as the URL*. If this works correctly, bookmark the page, and try accessing the page from the bookmark. If these tests work (but step 1 fails), then there is a problem with your DNS configuration; check the steps above to make sure you have configured everything correctly. If these tests do not work, go to step 3.

  3. Roll back the DNS changes you made and run the tests again. If the tests still do not work, then there is a problem with your network settings; contact your ISP or network administrator for assistance.



Privacy


Users who use the Google Public DNS servers will automatically submit extensive data to Google that includes all the websites and other services on the Internet that they visit.


According to the privacy information posted on the project web page Google Public DNS records temporary and permanent data but does not “correlate or combine” these information “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”.



Update:

Google Public DNS: Largest Public DNS service and receives 70 Billion requests a day