I live in a shared appartment and like to use pi-hole for the whole network. For my mates I need to unblock ad-heavy German news-site "bild.de". With any adblocking active, you get referred to a page "Why can’t I see bild.de?"
I tried whitelisting these subdomains from the default lists:
Is it possible that the link changed? I whitelisted the url, flushed dns from computer and device running PI-hole & i removed all my cookies... However Bild.de is still detecting pi-hole. Any suggestions?
Could you confirm that the proposed solution still works for you?
I’m sorry my pi is serving a different project at the moment, so I can’t test the settings right now on my side; I guess searching the query log for addresses is your best bet still–the domain in question didn’t look at all connected to "bild.de" back then, so you probably have to go through them all sadly.
Don't know if this is still an open question but I had the same "problem"...depending on the fact if bild.de is a news side worse visiting
I got access by whitelisting the following URLs:
Took me some time to fix this problem. Had some hardware issues...
But now I'm effectively blocking bild.de ads and still being able to browse the website.
normally there should be no problem using bild.de when running pi-hole.
Funny enough when calling bild.de you will be redirected to the "Why can't I see bilde.de" page.
There's a very simple way around that without whitelisting any pages...
First of all: I do not know why this solution works. I am myself working in the IT business (Senior test engineer) but maybe one of the pi-hole developers can answer this problem...
But now for the solution:
open bild.de: You will be presented with the bild.de blocking page...
now disable pi-hole for let's say 30 seconds
now open bild.de again within the time-period of pi-hole being disabled. this will work, of course
after the expiration of the given time period open bild.de again and you will see that...
...bild.de will never be blocked again!
This worked for me using
a) Firefox (60.0.1 / 64bit / Win 10 Pro 1803 build 17134.81)
b) Firefox (version ? / 32bit / Android 6)
c) Chrome (66.0.3359.181 / 64bit / Win 10 Pro 1803 build 17134.81)
d) Chrome (66.0.3359.158 / 32bit / Android 6)
Regards
deomaki
This is most likely because the browser cached the DNS result of the domain, and the DNS result you get from the Pi-hole is configured to be cached for only a short amount of time (to ease the enabling/disabling experience).
I think like Mcat12 said that this is happening because of caches. Could you remove cookies and caches followed by reloading the page? Is your workaround still working?
From my experience you currently need to white list: