# Google DNSSEC vs Pi-Hole's?

**URL:** https://discourse.pi-hole.net/t/google-dnssec-vs-pi-holes/1926
**Category:** Help
**Created:** [February 26, 2017, 8:09pm UTC](https://discourse.pi-hole.net/t/google-dnssec-vs-pi-holes/1926 "2017-02-26T20:09:26Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jpgpi250](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jpgpi250/32/286_2.png) [@jpgpi250](https://discourse.pi-hole.net/u/jpgpi250)
#### Post date: [February 27, 2017, 7:40am UTC](https://discourse.pi-hole.net/t/google-dnssec-vs-pi-holes/1926/2 "2017-02-27T07:40:22Z")

</div>

There are many articles out there, regarding DNSSEC.  
A [quote](http://www.internetsociety.org/deploy360/resources/plan-dnssec-validation/) from one of these articles

> Ideally, the DNSSEC validation will occur as close as possible to the end user (either a person or a device) so that the attack surface where an attacker could inject bogus DNS packets is minimized.

If you are using raspbian (version february 2017) and want to implement DNSSEC, read [this topic](https://discourse.pi-hole.net/t/the-truth-about-dnscrypt-proxy-and-dnssec/1694) to get a working solution.

---

_[View the full topic](https://discourse.pi-hole.net/t/google-dnssec-vs-pi-holes/1926)._