Gateway did not respond

Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

Gateway did not respond. Or posible cause is because i have Pihole working from raspberry pi with WIFI?

Actual Behaviour:

Pi Hole seems not to block ads although it’s active

Debug Token:

pto72hhvgf

2

Pi-hole is blocking ads correctly and can connect to the internet according to the debug log, so you can ignore that message.

Since Pi-hole is blocking ad domains, your devices must not be set up correctly if you are still seeing ads. Make sure your devices are only using Pi-hole for DNS.

3

I do not know what to touch anymore. It does not work



4

Did you set Pi-hole as your only DNS server in your router?

5

Yes. My raspberry with pihole is connected by wifi to a static address (192.168 ....) In the router, LAN section, like this


6

You are using more than just Pi-hole for DNS, so you will get DNS results from more than just Pi-hole, and some ads won't be blocked. Only use Pi-hole for DNS so that all ads are blocked.

7



Place only one, and I still see advertising

8

Check what DNS servers your clients are actually using.

9

Reinstall the entire system. I think the problem was because Pihole ran from Wi-Fi. Now install the RPI with Ethernet. Still configuring everything from scratch. We'll see if it works.

10

127.0.0.1 is the actually dns i am using

11

It does not work. I do not know what I'm doing wrong, but I lost all my Sunday trying to make this work ....

12

Is that the DNS server that the client is using, or just Pi-hole?

13

Ip Pihole on RAspberry pi: 192.168.1.36
DNS client is 127.0.0.1

14

How I see the DNS client?

15

What clients do you have? Windows, linux, etc? Google "Find DNS on BLANK" where "BLANK" is the operating system the client is running.

16

LInux: $ cat /etc/resolv.conf

Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)

DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

nameserver 127.0.0.1
search 192.168.1.36

17

I don't think the problem is wifi. That's just the method of transmitting data - if you can connect to the PiHole that is not the issue. I run several PiZeroW on WiFi only with zero problems.

18

You need to check each DNS client and ensure it is using the IP address of the PiHole (192.xxx). Old DNS addresses can linger in caches. Clear the DNS cache on each device and if needed renew it's DHCP lease. This will get all the devices using the PiHole as DNS server.

1 Like
19

That linux client has an internal DNS server. Check its configuration to make sure it is only using Pi-hole as its upstream DNS.

20

And can you tell me how do I do that in Debian?
I followed the instructions of Mcat12, I installed "nscd" and ran "$ sudo /etc/init.d/nscd restart
"
to clear the DNS cache on the client machine. I still do not know if I have to do it on the raspberry pi where PIHOLE runs. And I'm reinstalling PIHOLE because I had uninstalled it.