Adguard home constantly queries . reddit / selfhosted ---------------------------------------------------------------------- Sonaryr · 2023-11-24 08:48 Hi all I have been hosting adguard home on a local raspberry pi for a few years now. A few moths ago I changed everything around as I wanted to host more on that pi and moved to a docker setup. Everything works, but I see that I have about 70k dns queries in 24 hours. and about 90 percent of that is just a query for "." from an IP which I guess is my raspberry pi's interal docker IP? Anything I can do about that, or is that normal? ​ ​ https://preview.redd.it/1cmu3cs8e92c1.png?width=1274&format=png&auto=w ebp&s=42a647b32d87337ab9280def1445d151e5422a12 ---------------------------------------------------------------------- highspeed_usaf · 2023-11-24 12:13 No, does not look normal. That query doesn’t make any sense. What does Adguard say the response is (click the entry)? You can check that IP by running docker network inspect and see if that address falls within the subnet. Are you running any other services along side AGH? E.g., homebridge? ---------------------------------------------------------------------- Sonaryr · 2023-11-24 12:20 Response details: I have a wireguard running there and a portainer agent. network inspect tells me the IP is the gateway for the docker\_default network ---------------------------------------------------------------------- 4LAc · 2023-11-24 13:03 I've never had much joy with AdGuard via docker. There was usually some error or glitch I couldn't get fixed. I've always ended up installing it directly. It still works happily with wireguard and all the others that I do have installed via docker. ---------------------------------------------------------------------- highspeed_usaf · 2023-11-24 13:07 Hmm. The "." being queried from the gateway is interesting. Like there are internal DNS queries from the docker network not getting to the right place. Do you have network host mode enabled? Btw if you are using portainer, I will unfortunately be of little help troubleshooting your network stuff :( I use docker natively, not through any managers. By happenstance, I took a look at my own queries and noticed I was getting many requests to "host.docker.internal" from my physical docker host's IP address, which suggested some internal docker networking DNS stuff isn't working like it should. As different as that is to your problem, I'd almost suggest they appear somewhat similar. I implemented this fix: [https://discourse.pi-hole.net/t/solve-dns- resolution-in-other-containers-when-using-docker- pihole/31413](https://discourse.pi-hole.net/t/solve-dns-resolution-in- other-containers-when-using-docker-pihole/31413) And will monitor it. ---------------------------------------------------------------------- Deadlydragon218 · 2023-11-24 16:24 . Is the root of all DNS. These are known as the root DNS servers and they point to top level domains such as .com .net etc. including the newer TLDs. ---------------------------------------------------------------------- adamshand · 2023-11-25 08:38 I'd guess that you have another DNS server on your network which is trying to get the list of root name servers (what the . means) via AdGuard. I'd guess that there are so many queries because something is going wrong with it's attempt to get the root name servers from AdGuard so it's doing it over and over (because it can't function without them). ---------------------------------------------------------------------- Sonaryr · 2023-11-27 08:56 Ok, so I managed to figure it out, as soon as I took down wireguard the constant query stopped. So now I move wireguard to one of other pi's and everything is working as it should. Thanks for all the help!