# Blocking DNS-over-HTTPS (DoH)

**URL:** <https://discourse.pi-hole.net/t/blocking-dns-over-https-doh/21359>\
**Category:** Closed or Out Of Scope\
**Created:** [July 3, 2019, 4:35am UTC](https://discourse.pi-hole.net/t/blocking-dns-over-https-doh/21359 "2019-07-03T04:35:38Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![Coro](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/coro/32/15424_2.png) [@Coro](https://discourse.pi-hole.net/u/Coro)\
**Post date:** [September 17, 2020, 3:05pm UTC](https://discourse.pi-hole.net/t/blocking-dns-over-https-doh/21359/28 "2020-09-17T15:05:34Z")

</div>

> [@ChurchOfNoise](#):
>
> Taking it currently isn't, is there then a way to realise this functionality already e.g., using a proxy?

Yes, there is. I pinged DL6ER above. He gave the instructions to a user once, I'm fairly sure about it. I just cannot find it right now. He will know what to do.

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [September 17, 2020, 3:29pm UTC](https://discourse.pi-hole.net/t/blocking-dns-over-https-doh/21359/29 "2020-09-17T15:29:56Z")

</div>

You may want to take a look at Pi-hole's documentation for [Configuring DNS-Over-HTTPS](https://docs.pi-hole.net/guides/dns-over-https/).

---

<div class="post-metadata">

**Author:** ![ChurchOfNoise](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/churchofnoise/32/17886_2.png) [@ChurchOfNoise](https://discourse.pi-hole.net/u/ChurchOfNoise)\
**Post date:** [September 17, 2020, 4:29pm UTC](https://discourse.pi-hole.net/t/blocking-dns-over-https-doh/21359/30 "2020-09-17T16:29:04Z")

</div>

That's for DoH between the Pi-Hole and the DNS provider though - so upstream, right?  
(on a sidenote, I used Cloudflared at first when I started using Pi-Hole, moved to Unbound later)  
What I had in mind is to keep using Pi-Hole + DNS, and have the devices see the Pi-Hole as DoH source - so downstream.

Makes sense I hope...

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [September 17, 2020, 6:33pm UTC](https://discourse.pi-hole.net/t/blocking-dns-over-https-doh/21359/31 "2020-09-17T18:33:03Z")

</div>

> [@Coro](#):
>
> @DL6ER had a description somewhere how to add DoH to Pi-hole with a few easy commands. The guide on the docs currently talks about **Pi-hole --\> Cloudflare** , what is requested here is to support **Client --\> Pi-hole**.

Unfortunately, you git this wrong. I wrote a guide how to use Pi-hole with _any_ **upstream DNS server** using `https-dns-proxy` in the past. This was not about a downstream connectivity.

In contrast to

> [@Bucking\_Horn](#):
>
> You may want to take a look at Pi-hole's documentation for [Configuring DNS-Over-HTTPS](https://docs.pi-hole.net/guides/dns-over-https/).

using `https-dns-proxy` is not a `cloudflare`-dependent solution but, instead, vendor-independent which is better IMO. When I find the time, I will summarize my steps a long time ago. I only described it for another user and don't run this myself, so I'd have to dig out the details, first (I'm using a local `unbound` solution).

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [September 17, 2020, 9:20pm UTC](https://discourse.pi-hole.net/t/blocking-dns-over-https-doh/21359/32 "2020-09-17T21:20:08Z")

</div>

A post was split to a new topic: [Is this a solution for running a DoH server in front of Pi-hole?](https://discourse.pi-hole.net/t/is-this-a-solution-for-running-a-doh-server-in-front-of-pi-hole/38446)

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [September 17, 2020, 9:24pm UTC](https://discourse.pi-hole.net/t/blocking-dns-over-https-doh/21359/33 "2020-09-17T21:24:59Z")

</div>

> [@ChurchOfNoise](#):
>
> That's for DoH between the Pi-Hole and the DNS provider though - so upstream, right?

Sorry, I read your post as a request for an upstream proxy.

But regardless of upstream or not, let's keep this focused:  
Running a DoH server will not allow you to block DNS-over-HTTPS, which was the original request.

I'll split your question for running DoH in front of Pi-hole into a separate topic for discussion. 😉

[Previous page](https://discourse.pi-hole.net/t/blocking-dns-over-https-doh/21359.md?page=1)