# Domain not blocked when expected to be blocked

**URL:** <https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896>\
**Category:** Help\
**Created:** [December 5, 2018, 1:11pm UTC](https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896 "2018-12-05T13:11:59Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![pelangi](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/b19c9b/32.png) [@pelangi](https://discourse.pi-hole.net/u/pelangi)\
**Post date:** [December 5, 2018, 1:11pm UTC](https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896/1 "2018-12-05T13:11:59Z")

</div>

## Expected Behaviour:

I added `https://raw.githubusercontent.com/chadmayfield/pihole-blocklists/master/lists/pi_blocklist_porn_top1m.list` to the Settings \> Block Lists and expect that sites like pornhub.com will be blocked

## Actual Behaviour:

pornhub.com is still accessible

If I add pornhub.com to the Blocklist (wildcard) then I can confirm that pornhub.com is blocked. But I expect that it will be blocked using the gravity list.

## Debug Token:

_22slxqmlt9_

[https://raw.githubusercontent.com/chadmayfield/pihole-blocklists/master/lists/pi\_blocklist\_porn\_top1m.list](https://raw.githubusercontent.com/chadmayfield/pihole-blocklists/master/lists/pi_blocklist_porn_top1m.list)

---

<div class="post-metadata">

**Author:** ![pelangi](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/b19c9b/32.png) [@pelangi](https://discourse.pi-hole.net/u/pelangi)\
**Post date:** [December 5, 2018, 1:29pm UTC](https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896/2 "2018-12-05T13:29:34Z")

</div>

It seems to be blocking now. Is there gap between the list updated and it actually starts to block? Thanks.

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [December 5, 2018, 3:43pm UTC](https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896/3 "2018-12-05T15:43:00Z")

</div>

The block list you referenced blocks "pornhub.com", but not "www.pornhub.com". These are two different domains and it is likely that the domain you were able to access was "www.pornhub.com." Here is a quick way to check your pihole.log and see if this is the case - this command will find every instance of "pornhub" in your log.

`sudo grep pornhub /var/log/pihole.log`

If "pornhub.com" was shown as blocked, and "www.pornhub.com" was not, this was the problem.

---

<div class="post-metadata">

**Author:** ![pelangi](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/b19c9b/32.png) [@pelangi](https://discourse.pi-hole.net/u/pelangi)\
**Post date:** [December 6, 2018, 1:41pm UTC](https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896/4 "2018-12-06T13:41:22Z")

</div>

In that case, what do I do so that for all domain listed in [https://raw.githubusercontent.com/chadmayfield/pihole-blocklists/master/lists/pi\_blocklist\_porn\_top1m.list](https://raw.githubusercontent.com/chadmayfield/pihole-blocklists/master/lists/pi_blocklist_porn_top1m.list) the www equivalent of the domain names are block as well?

It is strange that when I randomly test the sites listed there, not all of them blocked while pornhub is remain blocked.

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [December 6, 2018, 2:15pm UTC](https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896/5 "2018-12-06T14:15:02Z")

</div>

Pornhub is likely blocked because you have blacklisted it as a wildcard.

If the public block list you are using does not adequately block the "www" equivalents, then feedback to the list maintainer would be in order.

---

<div class="post-metadata">

**Author:** ![pelangi](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/b19c9b/32.png) [@pelangi](https://discourse.pi-hole.net/u/pelangi)\
**Post date:** [December 11, 2018, 9:52pm UTC](https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896/6 "2018-12-11T21:52:47Z")

</div>

Actually I don't think the issue is about with/out WWW. Trying out sites listed on the above list, some of them that are blocked on Chrome I still can access through Firefox. How is that even possible?

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [December 12, 2018, 3:19am UTC](https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896/7 "2018-12-12T03:19:11Z")

</div>

Firefox has an option to run it's own filtering on it's own DNS. When you do this, your DNS traffic bypasses Pi-Hole. Check your Firefox options and disable this feature.

---

<div class="post-metadata">

**Author:** ![pelangi](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/b19c9b/32.png) [@pelangi](https://discourse.pi-hole.net/u/pelangi)\
**Post date:** [December 14, 2018, 8:29pm UTC](https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896/8 "2018-12-14T20:29:11Z")

</div>

Hi @jfb would you please tell me which part of configuration is that? I search for DNS in Firefox settings and found only Proxy DNS when using SOCKS v5 and Enable DNS over HTTPS which both are unticked.

 ![dns](https://discourse.pi-hole.net/uploads/default/original/2X/1/1df0bf0b19db0c8dd25a3fa21def24a5a926a55b.png)

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [January 4, 2019, 8:31pm UTC](https://discourse.pi-hole.net/t/domain-not-blocked-when-expected-to-be-blocked/14896/9 "2019-01-04T20:31:25Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.