The issue I am facing:
DNS Resolution is quite slow when using the LanCache as upstream DNS
Details about my system:
I currently have two piholes, which run fine without the Lancache as upstream. I would like to manually forward only these addresses to my LanCache server so other queries go to CloudFlare upstream instead. Example: cache-domains/steam.txt at 1faf51e6a0b4aeb98cdad98445a1b60b088cc249 · uklans/cache-domains · GitHub
I am not famiiar with lancache at all, but a while ago, another user had difficulties using a dockered lancache as Pi-hole's upstream DNS. This was caused by lancache handling DNS UDP traffic only, instead of UDP and TCP.
Maybe that is affecting you as well, see Intermittent 'config error is REFUSED'.
Hey, Appreciate the reply. I fully read that article and verified TCP 53 is in my docker config yml. My primary symptom at the moment is super high query time 1200+ MS for each query.
My setup is slightly different in that I have my Lancache and Pihole servers separated.
If I added the URLs in the host file on pihole to point at lancache would that work? I may be completely wrong, but am not sure how else to mitigate the query slowness.
Another idea, is there anyway I can add URL's to the conditional forwarding in pihole?
I actually was curious if there was any updates for Lancache, after update the docker containers query times dropped quite dramatically, I wonder if there was a memory leak or something causing the process to be super slow. I am still interested in seeing if there is an option to only forward specific URLs to the lancache server to help improve query time even more.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.