Pi-hole doesn't block any domains

Help Community Help
1

System info:

Centos 8.2
lighttpd/1.4.56-devel-lighttpd-1.4.56-rc7-30-g730c932e
Pi-Hole installed from automatic script

Expected Behaviour:

Blocking a certain domain/domains in a adlist

Actual Behaviour:

Not blocking anything nor any domain.
DNS settings are correct.

Debug Token:

omytyx3tla

2

Pihole is/was working

   [2020-11-25 01:02:25.284 3512756M] Imported 4885 queries from the long-term database
   [2020-11-25 01:02:25.285 3512756M]  -> Total DNS queries: 4885
   [2020-11-25 01:02:25.285 3512756M]  -> Cached DNS queries: 2078
   [2020-11-25 01:02:25.285 3512756M]  -> Forwarded DNS queries: 2780
   [2020-11-25 01:02:25.285 3512756M]  -> Blocked DNS queries: 4
   [2020-11-25 01:02:25.285 3512756M]  -> Unknown DNS queries: 23
   [2020-11-25 01:02:25.285 3512756M]  -> Unique domains: 578
   [2020-11-25 01:02:25.285 3512756M]  -> Unique clients: 5
   [2020-11-25 01:02:25.285 3512756M]  -> Known forward destinations: 2

From a client (which you think does not get blocked) please run

nslookup pi.hole

nslookup flurry.com

Side note: your're running nginx which is not officially supported. I'm moving your topic to community help.

[80] is in use by nginx (https://docs.pi-hole.net/main/prerequisites/#ports)

Side note 2:
As you're running pihole from within your lan, there is no need to configure public IPs as clients.

3

i ran nslookup flurry.com in my computer that has the dns configured and it still gave me the normal IP. running pi.hole is not available since the machine is a VPS and is not at my local LAN.

also, nginx does nothing on my pihole server since it's running at port 80 and lighttpd at port 8088.

the public IPs are basically mine and my other routers and all that because its a VPS not in LAN.

i don't know what is happening here...

4

Could you please provide the full output for the nslookups as run from a client?

7

this is the nslookup command for "flurry.com" in a Windows 10 CMD:

Server:  UnKnown
Address:  <redacted (VPS real IP)>

Non-authoritative answer:
Name:    flurry.com
Addresses:  212.82.100.150
          98.136.103.23
          74.6.136.150

this is the nslookup command for "flurry.com" in a Windows 10 CMD WSL Ubuntu in Windows 10:

Server:         <redacted (VPS real IP)>
Address:        <redacted (VPS real IP)>#53

Non-authoritative answer:
Name:   flurry.com
Address: 74.6.136.150
Name:   flurry.com
Address: 212.82.100.150
Name:   flurry.com
Address: 98.136.103.23
8

Don't open port 53 to the world. This creates an open resolver and we do not provide support for users that chose to run with that kind of configuration.

9

alright, its actually blocked to only some IPs to access it in the microsoft azure firewall.

10

i was checking here and i see that centos and localhost are actually getting blocked from accessing some domains. this is what i expected to happen normally in my windows pc.

it shows in the web panel that it blocked 7 requests, but in my pc it still doesn't work as expected.
image

11

so, i don't really know what happened, but after the 3rd reinstall i did, everything started working just fine....
i think that i just changed from cloudflare dns to google dns and now it works correctly

12

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