# DoH/DoT bypass Pi-hole

**URL:** <https://discourse.pi-hole.net/t/doh-dot-bypass-pi-hole/80956>\
**Category:** General\
**Created:** [July 2, 2025, 4:37pm UTC](https://discourse.pi-hole.net/t/doh-dot-bypass-pi-hole/80956 "2025-07-02T16:37:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Ladrien](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/ladrien/32/39018_2.png) [@Ladrien](https://discourse.pi-hole.net/u/Ladrien)\
**Post date:** [July 2, 2025, 7:57pm UTC](https://discourse.pi-hole.net/t/doh-dot-bypass-pi-hole/80956/2 "2025-07-02T19:57:36Z")

</div>

There are a few ways to bypass pi-hole. Refer to this post to block the majority of them: [Do individual devices require configuration with Pihole+Unbound?](https://discourse.pi-hole.net/t/do-individual-devices-require-configuration-with-pihole-unbound/77092)

There has also been a new pi-hole setting: `dns.specialDomains.designatedResolver` to prevent clients from upgrading to DoH via the upstream provider. Make sure this is set to true.

Edit: I just want to make clear that these bypasses are not a fault of pi-hole

---

_[View the full topic](https://discourse.pi-hole.net/t/doh-dot-bypass-pi-hole/80956)._