Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
I have two docker instances of pihole running on my network. both are wired with ips of 172.16.0.10 and 172.16.0.15. the network is configured as 172.16.0.0/23. i should be able to connect to either instances for adblocking and dns lookups.
Actual Behaviour:
the behavior that i am seeing is that wireless devices dont seem to be connecting to pihole instance on 172.16.0.10 but connect with no issues to the instance on 172.16.0.15. from a wireless host i get this:
% nslookup pi.hole 172.16.0.10
Server: 172.16.0.10
Address: 172.16.0.10#53
** server can't find pi.hole: NXDOMAIN
% nslookup pi.hole
Server: 172.16.0.15
Address: 172.16.0.15#53
Name: pi.hole
Address: 172.16.0.15
if i run these commands from a wired host on the network both lookups return correct results.
if i do a standard nslookup for any domain against 172.16.0.10 the results are correct but i see no activity in the log via the web interface.
i am at a loss as this has been working for a while and i have not changed anything. my docker script is the same for both instances minus the ServerIP= section where i specify the ip.
i also noticed that the routing tables of the instances show
Network routing table
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2
thanks for any assistance that can be provided.
Debug Token:
https://tricorder.pi-hole.net/RVJgF7v1/ - 172.16.0.10
https://tricorder.pi-hole.net/6GSp48Se/ - 172.16.0.15