The original post: /r/homelab by /u/masiv_o on 2024-06-22 22:42:13.
I currently run a single server using Nginx Proxy Manager, DuckDNS, PiHole (new), and Unbound (new).
The issue first appeared a few days ago when trying to access any of my public-facing domains. Requests would either take a considerable amount of time to go through or not go through at all. As I started investigating the root cause, I verified my configuration at every level mentioned above but found nothing. I then proceeded with nslookup and dig queries, where I noticed a pattern: there would be no response from the server for several seconds, often displaying messages like “;; communications error to 192.168.1.1#53: timed out.” Once the connection was made, latency would be normal for a while.
With the help of some forums and GPT, I managed to capture DNS request packets on the server side. I tried installing both PiHole and Unbound to see if there was any improvement, but to no avail. My current setup has Unbound as PiHole’s DNS, and PiHole is then pointed to by networkd, completing the cycle. One thing I noticed was the time between responses, being around 5.9 seconds (possibly a timeout, but I’m not sure if it’s due to DuckDNS, my configuration, or another party).
Despite my efforts, I haven’t been able to determine the root cause of the issue and haven’t found any specific information on the topic yet. I will provide further information if it helps with diagnosing the issue. Thank you for reading until the end.
