I'm new here as you can see. I generated a debug log entries. I'm not so sure what I need to do next with this, some errors I'm getting. My token is https://tricorder.pi-hole.net/TaRvy2bu/ also this was included as well---A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log I'm complete novice at this and trying to understand it all slowing..08/10/2024
Thanks for your patients
Welcome, please provide a lot more details - what errors are you seeing, where are you seeing them, when did this start happening, what are you expecting to happen, and anything else that could be useful. Thankyou.
All I know is the debug log was generated and automatically uploaded. I'm seeing the in the pi-hole Diagnosis of two messages-- |2024-08-08 13:43:55|DNSMASQ_WARN|Warning in dnsmasq core:
Maximum number of concurrent DNS queries reached (max: 150)
Check out our documentation for further information.||
||2024-08-10 20:21:53|RATE_LIMIT|Client 192.168.50.248 has been rate-limited (current config allows up to 1000 queries in 60 seconds)||
Not sure if I should delete these two or what do i do?
Thanks,
Your debug token is: https://tricorder.pi-hole.net/TMHdnRuX/
/var/log/pihole/pihole_debug.log
Pi-hole is telling you that the computer or device which has IP address 192.168.50.248 is sending a large number of DNS requests in a short space of time. When this happens, Pi-hole will "rate-limit" the IP, which means it will ignore it for a short time and see if it stops being so noisy. If it continues, Pi-hole will keep rate-limiting it for short periods of time.
To fix this you will need to identify the computer or device which has that IP address and then do some searching online to find why it might be making so many requests. You may need to contact the vendor or find a support forum and post in there to see if it can be stopped. Have a look in Pi-hole's Query Log and see if you can identify the domains it is trying to resolve. This will help you in your searching.
As for the other error, it is probably another symptom of the same situation - that device is filling all of Pi-hole's available lanes, so to speak. I would clear both errors and then see how it looks once you've fixed the first problem. Your Pi-hole looks like it is performing well.
One other thing from your log. Your router is the DHCP server and it is telling clients to use Pi-hole and itself (the router) for DNS. This means that clients will sometimes bypass Pi-hole. To fix this, log in to your router and find the DHCP LAN section and make sure that only the Pi-hole IP is being given out. Within a day devices will pick up the new settings and only use the Pi-hole, if the router is doing what you tell it to.
Thanks so much; I will follow all advice outline if I can really just understanding all this don't want to incorrectly enter wrong information. As far as pi-hole address in the DHCP LAN that would be the ip in the browser correct , example 192.168.50.83 I guess assign it manually.
Thanks,
That's right, in your router's LAN DHCP section it should only have the Pi-hole's IP in there, which is 192.168.50.83, and that will help to ensure clients are only using Pi-hole for DNS.
1 Like
Thanks so much for the invaluable information as I really needed. Learning a little at a time.
Thanks again,
I forgot to mention that pi-hole ip address shown in the the address bar that is the ip I believe that is correct.
You're welcome, do hang around and have a search for different things in the forum. You'll find lots of discussions and useful info if you ever have another question.
Yes, Pi-hole is the DNS server but it also has a web-based admin interface, so you would go to the same IP in your browser and log in, and now you can see what Pi-hole is doing and make changes, such as whitelisting or blacklisting a domain.
1 Like
Thanks...
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.