# Pi-hole slow DNS queries when browsing

**URL:** <https://discourse.pi-hole.net/t/pi-hole-slow-dns-queries-when-browsing/48151>\
**Category:** Help\
**Created:** [July 9, 2021, 2:21pm UTC](https://discourse.pi-hole.net/t/pi-hole-slow-dns-queries-when-browsing/48151 "2021-07-09T14:21:24Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![khoneini](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/k/3be4f8/32.png) [@khoneini](https://discourse.pi-hole.net/u/khoneini)\
**Post date:** [July 9, 2021, 6:54pm UTC](https://discourse.pi-hole.net/t/pi-hole-slow-dns-queries-when-browsing/48151/3 "2021-07-09T18:54:35Z")

</div>

Interesting...

Continued searching on the web and here on discourse and found the following:

- [Default blocking behavior makes Chrome slow · Issue #4107 · pi-hole/pi-hole · GitHub](https://github.com/pi-hole/pi-hole/issues/4107)
- [Consider making NODATA the default blocking strategy](https://discourse.pi-hole.net/t/consider-making-nodata-the-default-blocking-strategy/46080)

I applied the "fix" by setting BLOCKINGMODE=NODATA in /etc/pihole/pihole-FTL.conf (more details about BLOCKINGMODE here: [Blocking mode - Pi-hole documentation](https://docs.pi-hole.net/ftldns/blockingmode/)).

From the discourse and github I understand this seems to be a MacOS bug however I experienced the slowdowns on non MacOS devices as well. After I set the BLOCKINGMODE=NODATA I don't experience the slowdowns anymore. I will continue monitoring my network but this seems to be the fix!

---

_[View the full topic](https://discourse.pi-hole.net/t/pi-hole-slow-dns-queries-when-browsing/48151)._