# Pi-hole not working

**URL:** <https://discourse.pi-hole.net/t/pi-hole-not-working/52522>\
**Category:** Help\
**Created:** [January 12, 2022, 2:47am UTC](https://discourse.pi-hole.net/t/pi-hole-not-working/52522 "2022-01-12T02:47:58Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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:** [January 13, 2022, 10:49pm UTC](https://discourse.pi-hole.net/t/pi-hole-not-working/52522/8 "2022-01-13T22:49:31Z")

</div>

The DNS server at `80.241.218.68` that we requested to resolve `flurry.com` should have blocked resolution, as that is a filtering DNS resolver known to be blocking that domain.

Your answer suggests that the DNS request never made it to the public DNS server at `80.241.218.68`, and thus implies that either your router or your ISP redirect your network's DNS traffic to a server of their choice (e.g. Netgear's C7800 has been reported exhibiting that kind of misbehaviour [before](https://discourse.pi-hole.net/t/netgear-c7800-firmware-v3-01-36-and-pihole-not-working-properly/28482)).

---

_[View the full topic](https://discourse.pi-hole.net/t/pi-hole-not-working/52522)._