Please follow the below template, it will help us to help you!
Not a Pi-hole issue but a plea for help.
As a newbie (sorry), I've made some undocumented changes and run into a BIG issue. Pi-hole is not responding in a timely manner. I don't know how to troubleshoot the issue. I have Nagios looking after the IoT devices in the farm and not a single NRPE check (mostly via FQDN) can receive a reply before the task times out. It is one big RED sheet on the Nagios summary page. I need help to get Pi-hole back to configuration 48 hours ago without resorting to uninstall/reinstall, please.
The Pi-hole query log has two corresponding entries for any device in the farm:
- A record Status is OK (cached) and Reply is IP (0.1ms)
- AAAA record Status is OK (forwarded) and Reply is NA
Of course, AAAA entry is not relevant for this request for assistance.
Ping takes a few seconds to get started and then works fine (from Ubuntu desktop client) until interrupted.
Nslookup responds as follows:
$ nslookup raspbari1.parkcircus.org Server: 127.0.0.1 Address: 127.0.0.1#53 Name: raspbari1.parkcircus.org Address: 172.16.1.147 ;; connection timed out; no servers could be reached
Pi-hole is the DCHP and primary DNS server in the farm. The router is not supposed to forward local network (non-FQDN as well as local domain) names to the standard external servers (Google, OpenDNS, Cloudfare, etc) that are used for general Internet connectivity.
I would like Pi-hole to respond quickly to intranet DNS queries (as before for the last two years! ). The Pi-hole upgrade is not an issue. I have changed some setting that is making the query responses extremely slow.
I would like response times (presumably with Pi-hole DNS role) to improve so that basic applications (e.g. Nagios) do not experience socket timeout errors. The devices in the intranet farm are configured to use Pi-hole as the primary DNS server. Also, nslookup should complete without any timeout error message.
Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
ARMv7 Raspberry Pi (buster)
Pi-hole version is v5.1.1 (Latest: v5.1.1)
AdminLTE version is v5.1 (Latest: v5.1)
FTL version is v5.1 (Latest: v5.1)
I have been using Pi-hole essentially as a black box with two static IP addresses (Pi-hole itself and the router). All other devices have leased addresses from Pi-hole.
The browser use on the primary desktop client (Firefox) for external access has no noticeable latency. But when I try to access any local intranet site every request crawls very, very slowly. Most applications, OSS and home grown apps are experiencing socket timeouts.