开云体育

My setup is a bit different, i.e. not so utterly standard. I'm running
both pi-hole and a squid proxy on the same Pi, the former for obvious
reasons, the latter because it allows for URL rewriting, amongst other
things.

I was no longer able to connect to FB after running this:

pi@pi2b08:~ $ pihole -b --wild facebook.com
[i] Adding (^|\.)facebook\.com$ to regex list...
[i] facebook.com does not exist in whitelist, no need to remove!

[i] Pi-hole blocking is enabled
[i] Using cached Event Horizon list...
[i] 140909 unique domains trapped in the Event Horizon
[i] Number of blacklisted domains: 1
[i] Number of regex filters: 6

[] Restarting DNS service
[] DNS service is running
[] Pi-hole blocking is Enabled
pi@pi2b08:~ $ sudo service squid restart
pi@pi2b08:~ $

The squid restart became necessary because IP addresses tend to get
cached; they don't change often, so it is not necessary to request an
address again as long as one holds on to the results of previous queries.
This may happen in multiple places, in the browser, on your client device
(the one talking to pi-hole), or, in my case, the squid proxy.

To verify access denial on Pi-Hole's server, run this:

pi@pi2b08:~ $ export | grep -i proxy
pi@pi2b08:~ $ nslookup www.facebook.com
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: www.facebook.com
Address: 0.0.0.0

pi@pi2b08:~ $ wget
--2021-03-05 09:32:57--
Resolving www.facebook.com (www.facebook.com)... 0.0.0.0, ::
Connecting to www.facebook.com (www.facebook.com)|0.0.0.0|:443... failed:
Connection refused.
Connecting to www.facebook.com (www.facebook.com)|::|:443... failed:
Connection refused.
pi@pi2b08:~ $

The first command checks if your account is set up to use a proxy via
environment variable, such as http_proxy or HTTP_PROXY.

Hope this helps.

-Cornelius