PiHole shows no activity

Help Community Help
,
1

Hello,

I am experiencing a situation that changing DNS server on my router to my synology NAS (I am running pihole in the docker) causing the router forcefully change the local pool from 192.168.2.1 to 192.168.0.1. The synology has 192.168.2.200.

I can change the DNS servers in the "internet connection" which is setting up (dynamically) how the router looks in the UPC network (UPC connect box is in modem mode):

image
image1610×1834 348 KB

However, there is also an option to change the DNS server for the DHCP server of the router:

image
image1652×1860 398 KB

I think the second option is correct because my computers visibly show that they are looking firstly to the NAS as a DNS server. However, pihole does not show any activity.

2

If I go to the network tab in pihole admin, it shows that my computer is not using pihole. What does it mean?

image
image1861×1582 333 KB

3

Yes, this looks good. Mind, you need to dis/reconnect clients from the network to pickup new DHCP information.

Please upload a debug log and post just the token 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

4

Thanks for quick reply.
I moved forward. Pihole started showing queries but does not resolve a single dns querry, no webpages such as news show up.
I am running it in Synology NAS docker, so I am not sure where is the pi terminal in this case.

Debug token:
https://tricorder.pi-hole.net/HwIFxUif/

Debug file:
Removed by moderator to protect privacy

5

What does it show as "reply" in the query log for your received queries?

6

Do you mean this table?

image
image1471×605 64 KB

7

Which is acutally all queries I have. I put pihole IP address as primary DNS and my router as secondary DNS, this setup let me work now but if I delete the secondary DNS, I loose internet connection as no DNS is resolved in pihole.

8

Please upload a debug log and post just the token 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

9

https://tricorder.pi-hole.net/xUo9mJIo/

10 
*** [ DIAGNOSING ]: Domainlist (0/1 = exact white-/blacklist, 2/3 = regex white-/blacklist)
   id    type  enabled  group_ids     domain                                                                                                date_added           date_modified        comment                                           
   ----  ----  -------  ------------  ----------------------------------------------------------------------------------------------------  -------------------  -------------------  --------------------------------------------------                                 
   2        3        1  0             1.2.168.192.in-addr.arpa                                                                              2021-08-11 08:47:51  2021-08-11 11:03:55  Added from Query Log                              
   3        3        1  0             200.2.168.192.in-addr.arpa                                                                            2021-08-11 08:48:19  2021-08-11 11:03:51  Added from Query Log                              
   5        3        1  0             (\.|^)in-addr\.arpa$                                                                                  2021-08-11 11:03:40  2021-08-11 11:03:40

There is no reason to block *arpa requests. Those are valid PTR requests https://www.wikiwand.com/de/PTR_Resource_Record

12

I added them from the link of ads. Ok deleted.
However, this is not the reason why pihole does not solve dns and therefore all computers use the secondary DNS on my router.

14

Pi-hole's container doesn't seem to have access to an eth0 interface:

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.

You may have to provide the correct INTERFACE as an environment variable for your Pi-hole container if your Docker host does use a different interface.

15

Looks like a good vector! However, the only option (and the recommended one on some website how to install pihole in docker on synology nas) I can set during setting up of the docker container is:

image
image1126×952 34.2 KB

I know that the interface is ovs_eth0 from checking over ssh. So can I set it up as a variable in the environment to override the settings during the installation? If so, please let me know how, thanks

16

I have to pass on this one - I don't have a Synology device, so I don't know Synology's Docker UI.

The link I've provided above contains the information for plain Docker, where you'd just add the correct value to the INTERFACE environment variable (e.g. in a docker compose file).

Glancing at your screenshot, I'd guess Synology's UI might expose relevant settings under its Environment tab. Consulting Synology's documentation and support channels for Docker configuration options may yield quicker and better advice than I am able to provide you with.

17

Ok, no problem. I added INTERFACE as a variable and added ovs_eth0 as I checked over ssh. It is certainly the correct interface. Debug says the following:

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the ovs_eth0 interface:
192.168.2.200/24 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)

and still does not resolve DNS...

18

setupVars.conf contains following:
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=8.8.4.4
WEBPASSWORD=
BLOCKING_ENABLED=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
IPV4_ADDRESS=192.168.2.200
PIHOLE_INTERFACE=ovs_eth0
DNSMASQ_LISTENING=local
QUERY_LOGGING=true

20

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