Expected Behaviour:
Google should be accessible.
Actual Behaviour:
Google is being blocked.
Debug Token:
93ks5xs1h4
Google should be accessible.
Google is being blocked.
93ks5xs1h4
Can you give us a little more information on this issue? What url(s) are you trying to visit and what response are you getting. Also does this happen on the master release or just on the development testing code branch?
Share the output of these commands:
pihole -q www.google.com
dig www.google.com
pi@raspberrypi:~ $ pihole -q www.google.com
grep: *.domains: No such file or directory
[i] No results found for www.google.com found within block lists
pi@raspberrypi:~ $ dig www.google.com
; <<>> DiG 9.9.5-9+deb8u13-Raspbian <<>> www.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44911
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.google.com. IN A
;; ANSWER SECTION:
www.google.com. 2 IN A 10.0.1.85
;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Sep 23 23:47:13 UTC 2017
;; MSG SIZE rcvd: 59
Run pihole -g
and then the first command again.
pi@raspberrypi:~ $ pihole -q www.google.com
[i] Over 100 results found for www.google.com
This can be overridden using the -all option
I removed the malwaredomains.lehigh.edu list which fixed it.
[i] Over 100 results found for www.google.com
This number (which was recently changed to 100) tells me that you're running a very recent version of the development
branch. That explains why you encountered the following issue, which was fixed a couple of hours ago:
grep: *.domains: No such file or directory
Make sure you run pihole -up
so that whitelisting or blacklisting doesn't delete your list.#.*.domains
files