# Unbound, stubby or dnscrypt-proxy

**URL:** <https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378>\
**Category:** General\
**Created:** [May 8, 2018, 8:16am UTC](https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378 "2018-05-08T08:16:39Z")\
**Posts on this page:** 1\
**Showing post:** 24

<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:** [May 18, 2018, 2:49pm UTC](https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378/24 "2018-05-18T14:49:50Z")

</div>

The solution pihole + unbound is easy to implement, you already have it working'. @DL6ER has documented it well in his [wiki](https://docs.pi-hole.net/guides/unbound/).  
If you use unbound with pihole, you should disable DNSSEC in pihole (settings) and have DNSSEC records evaluated by unbound.

Why is this currently the preferred solution? see [here](https://discourse.pi-hole.net/t/dnssec-test-fails/9586/2).

---

_[View the full topic](https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378)._