The Domain Name System (DNS) was not designed with security in mind and is open to a number of attacks that can route requests for a web site to a spurious site masquerading as the genuine article.
DNSECC (Domain Name System Security Extensions) was designed to prevent these attacks but relies on both the site supporting DNSSEC and the name servers used to access that site being able to perform DNS validation.
Google's support for DNSSEC was announced in a posting on Google's security blog http://googleonlinesecurity.blogspot.nl/2013/03/google-public-dns-now-supports-dnssec.html this week by Yunhong Gu, team lead, Google Public DNS. "With this new security feature, we can better protect people from DNS-based attacks and make DNS more secure overall by identifying and rejecting invalid responses from DNSSEC-protected domains," Gu said.
However he added that implementation of DNSSEC is still low. "Only 7% of queries from the client side are DNSSEC-enabled and about 1% of DNS responses from the name server side are signed. Overall, DNSSEC is still at an early stage and we hope that our support will help expedite its deployment.
"Effective deployment of DNSSEC requires action from both DNS resolvers and authoritative name servers. Resolvers, especially those of ISPs and other public resolvers, need to start validating DNS responses. Meanwhile, domain owners have to sign their domains. Today, about 1/3 of top-level domains have been signed, but most second-level domains remain unsigned. We encourage all involved parties to push DNSSEC deployment and further protect Internet users from DNS-based network intrusions."
The ISOC web site provides details on how users can configure their systems to use Google's DNS servers. It also notes that another step is required. Applications, mainly browsers, requesting an IP address must request DNSSEC validation.
At present off-the-shelf browsers do not do so, but ISOC also provides details of plug ins for Chrome and Firefox that provide this function.