popbob
December 19, 2024, 9:37am
1
Expected Behaviour:
Accessing websites through end devices connected to Pi-hole.
Actual Behaviour:
Queries appear on Pi-hole web GUI and show domains that a device tried to access however trying to actually connect to them will show a connection error on the device.
Debug Token:
https://tricorder.pi-hole.net/h0vkJPwb/
You are running your Pi-hole as a Docker container.
Please share your docker-compose or docker run script used for starting Pi-hole.
And run from a client, please share the output of:
nslookup pi.hole
nslookup flurry.com
popbob
December 19, 2024, 11:31am
4
C:\Users\Name>nslookup pi.hole
Server: UnKnown
Address: 192.168.100.34
Name: pi.hole
Address: 0.0.0.0
C:\Users\Name>nslookup flurry.com
Server: UnKnown
Address: 192.168.100.34
Name: flurry.com
Addresses: ::
0.0.0.0
I'm can't seem to find the file you mentioned and running "docker compose up" cant find it either. How can I find it ?
I cannot know that.
How do you start your Pi-hole container?
Your nslookup results show that your Pi-hole is being used for those requests and blocking is working.
You can use nslookup to verify how your dockered Pi-hole at 192.168.100.34
would answer a given request, e.g.
nslookup discourse.pi-hole.net 192.168.100.34
For a domain that you can't connect to, what does a respective nslookup return?