Google has introduced its own new free public DNS server service to all the users on internet. The system is named as Google Public DNS. The basic reason for the development of Google Public DNS server is to design a server that can provide comfort to all users for web-surfing practices more rapidly, safer and trustworthy.
- Speed: Server-side cache is sometimes neglected which is one of the primary reasons to slow down the speed of DNS reaction. This problem can be removed by introducing clever caching practice that helps add to the speed-up DNS reactions. Same clever caching practice has been introduced in Google Public DNS. It outfits pre-fetching process i.e. before the TTL on a user request expires; the system refreshes the record consistently for a large number of trendy domains. This allows Google Public DNS to serve many DNS requests in the round trip time it takes a packet to travel to the servers and back.
- [ad#ad-taalz-inpost-right]Security: Google Public DNS server provides the maximum security to all the users by implementing a new security protocol named as Domain Name System Security Extensions Protocol (DNSSEC). Using this protocol makes the service providers need to take additional measures to keep their caches protected. Overall this makes a user request more difficult for hackers and attackers to spoof valid responses by randomizing the case of query names. Also Google Public DNS includes additional data in its DNS messages.
- Validity: Google Public DNS acts in accordance with with the DNS standards and gives the user an accurate and to the point results a user expects without blocking any piece of information or filtering the searched information, and provides no redirection that may slow down a user’s browsing experience.
- Performance. Google Public DNS outfits “smart” caching to increase the speed of responses. It separately resolves the 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.