编辑“︁Google Public DNS”︁（章节）

===DNSSEC===
2013年5月6日，Google Public DNS默认启用[[DNSSEC]]验证，意味着即使客户端未启用，所有的域名解析请求都将接受验证<!-- explicitly opt out -->。<ref>{{cite web |url=http://googleonlinesecurity.blogspot.com/2013/03/google-public-dns-now-supports-dnssec.html |title=Google Public DNS Now Supports DNSSEC Validation |publisher=Google Code Blog |date=2013-06-01 |accessdate=2014-01-21 |archive-date=2016-02-10 |archive-url=https://web.archive.org/web/20160210112938/https://googleonlinesecurity.blogspot.com/2013/03/google-public-dns-now-supports-dnssec.html |dead-url=no }}</ref>

Google Public DNS起初不直接支持DNSSEC。即使RRSIG不可被查询，AD flag（Authenticated Data，意味着服务器可以验证所有数据的签名）在最初版本中从未设置过。2013年1月28日这种情况得到改进，当时Google的DNS服务器静默启动DNSSEC验证信息的供应，<ref>{{cite web |url=http://seclists.org/nanog/2013/Jan/690 |title=Google's Public DNS does DNSSEC validation |publisher=nanog mailing list archives |date=2013-01-29 |accessdate=2014-01-21 |archive-date=2018-11-11 |archive-url=https://web.archive.org/web/20181111173654/https://seclists.org/nanog/2013/Jan/690 |dead-url=no }}</ref>但是只有客户端启动DNSSEC OK (DO) flag时生效。<ref name="CircleID">{{cite web |url=http://www.circleid.com/posts/20130717_dns_dnssec_and_googles_public_dns_service/ |first=Geoff |last=Huston |title=DNS, DNSSEC and Google's Public DNS Service |publisher=CircleID |date=2013-07-17 |accessdate=2014-01-21 |archive-date=2018-07-01 |archive-url=https://web.archive.org/web/20180701050320/http://www.circleid.com/posts/20130717_dns_dnssec_and_googles_public_dns_service |dead-url=no }}</ref>这一服务需要的client-side flag在2013年5月6日被替换成默认启用的完整的DNSSEC验证。