Hi,
RATE_LIMIT setting i not working.
Please be more specific about the issue you encounter.
Please upload a debug log and post just the token generated by
pihole -d
allowing to upload when prompted, or do it through the Web interface:
Tools > Generate Debug Log
Post the output of
cat /etc/pihole/pihole-FTL.conf
PRIVACYLEVEL=0
RATE_LIMIT=0/0
On the pihole logs show:
config error is refused
reply error is SERVFAIL
Resulting to not able to resolve domain.
Can you quote some of these lines? SERVFAIL is a different error code and shouldn't have anything to do with rate-limiting. It typically means your upstream DNS server is either no (or not properly) responding. From your debug log I see that you have quite a long list of upstream DNS server configured. As far as we know know, I'd say there is some chance that your Pi-hole selected, by chance, a malfunctioning one.
I see there are two DNS servers in the same /16 network as your Pi-hole is. Chances are high that they will always be the fastest and, hence, will always be selected as best upstreams. Check the logs of those to see if they were queried at all and, if so, what they responded with.
How about the config error is refused?
Also this error happened only after the latest upgrade resulting to not able to browse.
I tried to reduce the number of users using pihole dns then the is gone and they are able to surf the internet. That's why I add the RATE_LIMIT=0/0 as instructed on the update logs but the logs is still showing and the users are not able to resolv.
Following are sample logs if more users used the pihole as dns:
21:56:55: query[A] play.googleapis.com from 202.57.32.32
21:56:55: cached play.googleapis.com is (null)
21:56:55: config error is REFUSED
It appears you are running an open Pi-hole? This IP is not a local LAN IP.
Im not running open pihole, Im just using a public ip on my network.
Let's take a look at the traffic your Pi-hole is receiving and see if rate limits would be met:
echo ">stats >quit" | nc localhost 4711
echo ">top-clients withzero (100) >quit" | nc localhost 4711
echo ">overTime >quit" | nc localhost 4711
Then you're doing it wrong.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] ffej.purpledaily.com is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve ffej.purpledaily.com via Pi-hole (PUBLIC IP IS BAD)
[✓] doubleclick.com is 172.217.24.78 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the enp2s0 interface:
192.168.251.222/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
That public IP isn't configured for the interface on the PI-hole device.
PIHOLE_INTERFACE=enp2s0
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.