I am not getting any return traffic from my pi-hole

Help
1

Hi,

I have setup a pi-hole as normal, followed a normal guid aswell.

I then installed unbound on my pi-hole.

The problem I am facing know is that when I change my pc DNS to the pi's ip address, the internet does not work for me. I cannot reach any website.

Please note that on my home network I do network segmentation.

I have put all the relevant rules on my home firewall so that all my devices can DEFINALTY reach my pi-hole.

BUT!, for some reason when my pc makes a request on port 53 to my pi, the pi does not respond.

Please note that I can ping the pi and a get a response.

image

Please see picture attached, my pc is sending packets on port 53 but not receiving anything back from the pi.

2

If you are not able to access the internet from Pi-hole host, you will need to temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.

sudo nano /etc/resolv.conf

Edit the nameserver line to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Then, 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

3

Hi please see logs:

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

4

the pi itself has internet outbreak, but as soon as I set my home pc's DNS settings to the PI's ip address my pc does not have internet.

5

I think your issue is your Pi-hole is on a different network (192.168.90.2/24) than your PC (I'm guessing it is 192.168.20.101) and you configure Pi-hole to listen only local requests (DNSMASQ_LISTENING=local).

image
image573×232 5.24 KB

6

Oky I see what you mean,

It is supposed to be that way.

As explained earlier I do network segmentation on my home network.

My PI is on a different subnet as my other devices the pi ip is 192.168.90.2

7

I have a setup similar in that my Pihole is on one network (192.168.3.0/24) and other VLANs are on 192.168.1.0/24, 10.10.5.0/24, etc. I had the same problem you describe initially, but change the Interface settings to "Respond only on interface eth0" fixed it, since ultimately all LAN DNS traffic is going through my RPi's ethernet port.
Note that your "...interface..." may have a different name from mine.

8

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