News for hackers. Stuff that matters.
Re:Pi-Hole: Why You Need a Network-Wide Ad-Blocker by natch on Tuesday August 07, 2018 @12:28PM (#17708076)
When something isn't working, how do you determine with a tiny bit of effort which one or more domains out of the 650,000+ domains to whitelist?
Re:Pi-Hole: Why You Need a Network-Wide Ad-Blocker by michaelbuckbee on Tuesday August 07, 2018 @12:46PM (#17708252)
Here is what I do:

1. Switch off DNS from PiHole to ISP DNS (or Google/CF, whatever non blocking DNS)

2. Reload page in Chrome with uBlock Origin and selectively allow domains to load until the page loads.

3. Whitelist domain in PiHole

This works b/c both uBlock Origin and PiHole out of the box use basically the same blocklists (or you can force them to).

Re:Pi-Hole: Why You Need a Network-Wide Ad-Blocker by ProAm on Tuesday August 07, 2018 @01:47PM (#17708815)
How often do you find yourself doing this? Probably hard to determine, how frequent when you first set it up, vs after a month of use? Thanks
Re:Pi-Hole: Why You Need a Network-Wide Ad-Blocker by natch on Tuesday August 07, 2018 @02:29PM (#17709235)
Thanks. Can you expand on what you mean in step 2?

What is involved in selectively allowing domains to load?

Could you do it if the domain is a completely unrelated string to whatever site you are visiting? (Say for site example.com, it requires something from whwehkhsfasfs.com in order to load)... how does step 2 work exactly in this case? Are you being prompted for a small subset of domains that the page is trying to load, for example?

Re:Pi-Hole: Why You Need a Network-Wide Ad-Blocker by michaelbuckbee on Tuesday August 07, 2018 @04:42PM (#17710585)
So, PiHole has a web interface to blacklist/whitelist items, but it's hard to use for debugging as what it "sees" are just a bunch of DNS requests come through (they aren't grouped by page/user - at least in the version I had going).

But in Chrome with uBlock Origin - it very clearly tells you what's happening and you can selective unblock domains until the page starts working and then turn around and add that domain to the whitelist.

I'm making this sound harder than it actually is, it's honestly just a couple mouse clicks and page refreshes in Chrome with uBlock origin going.

Re:Pi-Hole: Why You Need a Network-Wide Ad-Blocker by erikbye on Wednesday August 08, 2018 @03:02PM (#17718473)
I've always found it trivial to know what to whitelist.

Pi-hole admin -> Query log -> Show all -> Search filter <domain>

Whitelist whatever necessary.

Re:Pi-Hole: Why You Need a Network-Wide Ad-Blocker by t3ra on Wednesday August 08, 2018 @01:34AM (#17713432)
I use the web interface and filter it with the IP address of the device. It will usually show up in the top of the list and try whitelisting.

Example my Samsung TV took some effort : multiple domains were blocked and had to restart my TV everytime, thankfully PiHole has a neat responsive web interface. After allowing 2 domains it started to work or else it wouldnt go online.

Re:Pi-Hole: Why You Need a Network-Wide Ad-Blocker by luxpir on Tuesday August 07, 2018 @03:12PM (#17709638)
Easiest way: check the log to see what was blocked. It's as simple as that.

Happens so infrequently though - the lists are made up of domains you don't typically want to whitelist. Only 133,608 on my lists though, and that's pretty up to date.

Re:Pi-Hole: Why You Need a Network-Wide Ad-Blocker by TremendousJudge on Tuesday August 07, 2018 @12:39PM (#17708184)
I want to know this as well