Pihole not resolving dns. conf file is configured to use 127. . Apr 1, 2025 · However, some users may encounter issues with DNS resolution after the upgrade, particularly when the /etc/resolv. Mar 17, 2021 · Is your router configured to use Pi-hole as its upstream DNS server (as opposed to distributing Pi-hole as local DNS server via DHCP)? If it is, CF won't give you per-client attribution for DNS requests anyway, since Pi-hole would see all DNS requests as originating from your router. 255. Feb 21, 2025 · After updating to V6 pihole stopped answering DNS requests on host interface e. 168. The problem lies in your router, by all indications. my Pi-Hole. Yes, you read that right - I have a few Domain Controllers at home. This guide provides solutions to common issues encountered when using Pi-hole v6, including DNS resolution problems, blocking issues, network conflicts, and performance optimizations. Feb 18, 2019 · Everything we have tested so far, plus your debug log, indicates that DNS requests made to the Pi-Hole are resolving. I haven't tried changing the container's DNS from 127. 31. g. First thing I tried was clearing iptables, so there are no rules whatsoever, then it worked on host IP. 12, but answers them on docker interface IP e. : 192. 11 yet, but I thought that having the explicit DNS server set in the compose file would override that? What I noticed first and foremost is that DNS resolved from my Domain Controllers vs. This article will explain the problem and provide a step-by-step solution to restore DNS functionality. 1. 0. 102. : 172. 1#53 as the nameserver. lcbm ucpcme myojj vqjykyz cuhktn xooho lmjw exfzvx vbr frkuvx

Pihole not resolving dns. I haven't tried changing the container's DNS from 127.