The issue I am facing: most Clients are not resolving to the Pihole containers it appears only certain devices on specific vlan.
Details about my system:Two Docker containers running the latest pihole across two separate hosts resolving to active directory for DNS
What I have changed since installing Pi-hole: Little changed apart from adding some groups hoping to add the clients to them once they show in the Admin menu
From one of those clients (and from the command prompt or terminal in that client and not via ssh to the Pi), what is the output of
nslookup pi.hole
Hi,
On some devices It resolves fine. other devices it seems to be able to run nslookup on it. It tries to use the Pihole but always ends up saying Not found
That's not what I asked. What I need is the complete output of the command for one of the clients that does not appear to be using Pi-hole. It should look something like this:
nslookup pi.hole
Server: 192.168.0.160
Address: 192.168.0.160#53
Name: pi.hole
Address: 192.168.0.160
Also, please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
https://tricorder.pi-hole.net/qlJcCDg8/
P:\>nslookup pi.hole
Server: pi.hole
Address: 192.168.6.3
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Name: pi.hole
Address: 0.0.0.0
The debug log you uploaded shows that Pi-hole at this IP address:
eth0 (192.168.3.4)
Yes its the Docker version on a Docker network with direct routing to the other subnets
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.